|
HOW TO: Remove a Windows 2000 Domain Controller from the domain |
|
|
To remove a domain controller from the domain you demote it using the dcpromo.exe command. To use this tool type dcpromo at either the command prompt or at the run command.
However, there are some considerations that you need to think about. This article briefly discusses those.
Firstly, does this DC hold any of the five FSMO (Flexible Single Master Operations) roles, i.e. the PDC emulator, the Schema master, etc. If it does, it is recommended that they are moved (not seized, there's a distinct difference) to another DC prior to the demotion. In actuality, the demotion process will relocate these roles for you; however it simple chooses an (almost) random DC. This is why most prefer to perform the move themselves.
For information on how to move the FSMO roles, and for links to additional sources of information please refer to the following link:
Secondly, are there any other Global Catalog servers in the domain? If not, you will need to make one of the other DCs a GC too. Realistically, you should have at least two GCs, however that is beyond the scope of this article.
For a step-by-step article on how to configure (or un-configure) a Global Catalog server please refer to the following link:
And then there's DNS! Do you have any other DNS servers? If not you're going to need to move DNS as well. Again, realistically, there should be at least two DNS servers. Furthermore, the clients should be configured to point to both. Many people make the classic mistake of demoting (or even simply powering down and rebuilding) the DC and forgetting about where all the clients are pointing for DNS. Regardless how many DNS servers there are, if the clients (that's DNS clients, not actual workstations) are only pointing at one DNS server (they're usually DCs) and you get rid of that DC you're in a little predicament.
Document information
Author: Paul Williams
Written: 24-06-2004
Version: 2.0
Last updated: 07-08-2007
Last updated by: Paul Williams
|
How-To 
