Removing SBS 2003 Server from Network

We were doing a system upgrade to our network and upgrading from Windows Small Business Server 2003 to Windows Server 2012 R2.

About 2 years ago we moved Exchange role from SBS 2003 to Windows Server 2003 Std + Ms Exchange 2003 Standard.

And last week we moved AD role from SBS 2003 to Windows 2012 R2. Unfortunately during the weekend old SBS server has failed with it's main disk (which was not redundant). So we are struggling to load it back. Although we load it, it keep shutting down after an hour and saying the current environment violating EULA agreement (Not sure why is this as there are 14 days period to remove the SBS from network)

Question 01:
New Exchange "Server Manager" (2003 Std) still shows old (SBS) server in the list of Exchange servers. Would it causing any trouble to email users if we remove the old Exchange server by using "Remove Server" option?
We have moved all user mailboxes to new server
All Connectors have been moved to new server
Only communication we can see there are some system mailbox messages queued in new server and waiting to deliver to old server

Question 02:
Although we have moved all FSMO roles to new domain controller, we haven't demoted SBS from AD roles. Can we safely remove SBS from Domain Controller list without recovering the SBS? If so can you please provide necessary steps.
netdom command shows all FSMO roles belongs to new Domain Controller
We Managed to Remove Global Catalog privilege from old SBS

We would really appreciate if you can help with above two questions.

Thanks in Advance

Sameera
LVL 2
sameeragayanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Pete LongTechnical ConsultantCommented:
It's rebooting because SBS expects to be holding all the FSMO Roles

Q1. Not as long as the new Exchange server is not looking a the SBS box as a 'DC or as the recipient update service server, look at my migration document here for explanation.

Q2. IF there is no data on the SBS box don't even try and restore it! if you delete it from the domain controllers OU in active directory, tick 'this server is permanently offline and will not be recovered' (or something like that I cant remember the actual text of the question). Then make sure it's removed from active directory sites and services.
Finally I would do a metadata clean-up to make sure its safely gone.(Google it, it's not hard).

Pete
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sameeragayanAuthor Commented:
Thanks Pete.

Apart from them we noticed that new AD does not create email accounts when adding new users. This option not available at all. We have to access AD from mail server and add new users in order to get the email accounts. Is this something relate to this SBS issue?

We will try it this Friday and post the result.
0
Pete LongTechnical ConsultantCommented:
You need  to install the Exchange 2003 Management tools on the other DC before you will get that option m8
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.