Removing SBS 2003 Server from Network

Posted on 2014-09-02
Last Modified: 2014-09-07
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

Question by:sameeragayan
    LVL 57

    Accepted Solution

    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).

    LVL 2

    Author Comment

    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.
    LVL 57

    Expert Comment

    by:Pete Long
    You need  to install the Exchange 2003 Management tools on the other DC before you will get that option m8

    Featured Post

    Threat Intelligence Starter Resources

    Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

    Join & Write a Comment

    Easy CSR creation in Exchange 2007,2010 and 2013
    The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    how to add IIS SMTP to handle application/Scanner relays into office 365.

    746 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    15 Experts available now in Live!

    Get 1:1 Help Now