If your domain controller down and stop working , you can recover your domain controller if you have any running additional domain controller of same domain. For that I assume here that you have a running DNS or in same additional domain controller contain a DNS server also and global catalog service also available same location. For recovery we use ‘NTDSUTIL’ command line tool.
Now follow the steps below:
- From additional domain controller go to RUN console, write ‘cmd’ and click OK. (If you are doing in Windows Server 2003 then install support tools.msi from Windows Server 2003 CD and go Start button >> All programs >> Support tools >> Command terminal).
- Type ntdsutil in the Open Command Terminal box, and then click ENTER.
- Type roles, and then press ENTER.
- Type connections, and then press ENTER.
- Type connect to server <servername>, and then press ENTER, where <servername> is the name of the domain controller that you want to assign the FSMO role.
- At the server connections prompt, type q, and then press ENTER.
- Type seize role, where role is the role that you want to seize. For a list of roles that you can seize, type ? at the fsmo maintenance prompt, and then press ENTER. For example, to seize the RID master role, type seize rid master. The one exception is for the PDC emulator role, whose syntax is seize pdc, not seize pdc emulator.
Seize domain naming master
Seize infrastructure master
Seize RID master
Seize schema master
- Then from the fsmo maintenance prompt, type q, and then press ENTER to gain access to the ntdsutil prompt. Type q, and then press ENTER to quit the Ntdsutil utility.
- After seize the fsmo role we need to check whether it placed properly on ADC or not. For that we need to run NetDom Query FSMO command on command terminal. Then we need to clear all METADATA from Active Directory Domain Services.
I’ll give other post regarding METADATA cleanup.