Removing a SBS 2000 server from the network (safely) RRS feed

  • Question

  • Hi there,

    I have a network with a Microsoft SBS 2000 server, Windows 2003 Server and 2008 R2 servers. Removing SBS 2000 has to happen so we can move the functional level of the domain higher to migrate from Exchange 2003 to 2010.

    I am having real issues getting SBS 2000 off the network, without screwing up AD. While I had the server running, I tried to transfer the roles. This resulted in AD being corrupt some how...

    My final step was to power down the SBS server and manually (forcefully) take the roles on the new 2008 R2 server. Would this work or is there an easier way?


    Monday, January 31, 2011 1:41 AM

All replies

  • How many Domain Controllers do you currently have in the AD? My suggestion would be to demote all DCs except for a single Server 2003 DC. Then seize the 5 FSMO roles, and check that the server 2003 is also a GC.

    Then shut down the SBS2000, and physically remove it from the network. If everything is running after a few days, then you know your network is OK.

    Then, you can remove the SBS2000 server from the network using NTDS util, and clean up the entries from AD Users and Computers, and AD Sites and Services, and use ADSI to clean out any remaining entries. Once this is cleared up, you should be able to DCPROMO other DC and then raise the functional level.

    Regards, Boon Tee - PowerBiz Solutions, Australia - http://blog.powerbiz.net.au
    Monday, January 31, 2011 1:55 AM
  • That was my excat plan, with one exception.

    I was going to seize the roles on the 2008 r2 server, as the 2003 server will be removed from the network as well. Currently I've powered down the server and we've only have a few DNS/DHCP issues so far which have been fixed. If everything went fine this week, I was going to size the roles and remove the SBS server using ntds.

    There are 3 DCs. SBS 2000, Win2k3, Win2k8R2

    Does this sound like a plan?

    Monday, January 31, 2011 2:04 AM
  • It sounds OK. I would still be inclined to remove the other DC as well, so that you don;t have to deal with replication errors as well, when you drop the SBS2000.

    Also, you need to make sure that the DNS is properly replicated before shutting down the SBS2000, and ensure that all DHCP clients are properly redirected.

    Regards, Boon Tee - PowerBiz Solutions, Australia - http://blog.powerbiz.net.au
    Monday, January 31, 2011 2:42 AM
  • Would you be able to expand on what you mean by DNS being properly replicated? I assume the win2k3 dc is demoted and the network is left for a day or so, replication will take effect?
    Monday, January 31, 2011 3:58 AM
  • The Domain Controller that is remaining needs to be the DNS server as well. Otherwise all the clients will be looking for the DNS on the SBS2000 which you are shutting down.
    Regards, Boon Tee - PowerBiz Solutions, Australia - http://blog.powerbiz.net.au
    Monday, January 31, 2011 4:20 AM
  • I would also like to point out that the server you want me to demote is running Exchange 2003. I've read some horror stories about doing this. Wouldn't it be easier to drop off the sbs 2000 machine by turning it off, seize the roles in the 2008R2 domain controller then deal with any AD replication issues with the 2003 box? All I have to do is migrate 2003 exchange to 2010 after this, then I can kill off that server as well.

    Reading up, it looks like the best way is to put another 2003 server in. That's an option, however time is not on my side. Just wondering how safe it is dropping the sbs 2000 server, claiming the roles so I can install Exchange 2010 (forest level needs to be 2003) then migrate so I can dump the 2003 server.

    Saturday, February 5, 2011 7:56 AM
  • Yes, it is always good to have the whole picture, or you may get an answer that is not suitable. In that case, you should definitely leave the 2003 server as is.

    So what is running on the 2008 R2 server?

    Regards, Boon Tee - PowerBiz Solutions, Australia - http://blog.powerbiz.net.au
    Saturday, February 5, 2011 12:13 PM
  • The 2008R2 server is just a fileshare server and domain controller at the moment. There is another 2008R2 server running SQL in the network for apps, but I can't really see an issue there. The plan once the sbs 2000 is removed is to install Exchange 2010 on the 2008R2 server that is a domain controller (I know this isn't good, but limited by budget), and go from there.
    Saturday, February 5, 2011 11:57 PM
  • Hi,



    Please kindly check out the following article that describes how to decommission a DC:





    This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.





    Saturday, February 19, 2011 4:58 AM
  • If you are going to install Exchange 2010 on 2008R2 server, why not just install SBS2011?
    Regards, Boon Tee - PowerBiz Solutions, Australia - http://blog.powerbiz.net.au
    Saturday, February 19, 2011 5:21 AM
  • SBS2011 was not available and had not been tested. R2 server was already there... if that makes sense.
    Monday, March 21, 2011 6:10 AM