Delete Failed DCs from Active Directory

Caution: Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality.
To clean up metadata

1. At the command line, type Ntdsutil and press ENTER.

PowerShell

1 2	C:\WINDOWS>ntdsutil ntdsutil:

2. At the Ntdsutil: prompt, type metadata cleanup and press Enter.

PowerShell

1 2	ntdsutil: metadata cleanup metadata cleanup:

3. At the metadata cleanup: prompt, type connections and press Enter.

PowerShell

1 2	metadata cleanup: connections server connections:

4. At the server connections: prompt, type connect to server <servername>, where <servername> is the domain controller (any functional domain controller in the same domain) from which you plan to clean up the metadata of the failed domain controller. Press Enter.

PowerShell

1 2 3 4

server connections: connect to server server100 Binding to server100 ... Connected to server100 using credentials of locally logged on user. server connections:

Note: Windows Server 2003 Service Pack 1 eliminates the need for the above step.

5. Type quit and press Enter to return you to the metadata cleanup: prompt.

PowerShell

1 2	server connections: q metadata cleanup:

6. Type select operation target and press Enter.

PowerShell

1 2	metadata cleanup: Select operation target select operation target:

7. Type list domains and press Enter. This lists all domains in the forest with a number associated with each.

PowerShell

1 2 3 4

select operation target: list domains Found 1 domain(s) 0 - DC=dpetri,DC=net select operation target:

8. Type select domain <number>, where <number> is the number corresponding to the domain in which the failed server was located. Press Enter.

PowerShell

1 2 3 4 5 6

select operation target: Select domain 0 No current site Domain - DC=dpetri,DC=net No current server No current Naming Context select operation target:

9. Type list sites and press Enter.

PowerShell

1 2 3 4

select operation target: List sites Found 1 site(s) 0 - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net select operation target:

10. Type select site <number>, where <number> refers to the number of the site in which the domain controller was a member. Press Enter.

PowerShell

1 2 3 4 5 6

select operation target: Select site 0 Site - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net Domain - DC=dpetri,DC=net No current server No current Naming Context select operation target:

11. Type list servers in site and press Enter. This will list all servers in that site with a corresponding number.

PowerShell

1 2 3 4 5

select operation target: List servers in site Found 2 server(s) 0 - CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net 1 - CN=SERVER100,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net select operation target:

12. Type select server <number> and press Enter, where <number> refers to the domain controller to be removed.

PowerShell

1 2 3 4 5 6 7 8 9

select operation target: Select server 0 Site - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net Domain - DC=dpetri,DC=net Server - CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net DSA object - CN=NTDS Settings,CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net DNS host name - server200.dpetri.net Computer object - CN=SERVER200,OU=Domain Controllers,DC=dpetri,DC=net No current Naming Context select operation target:

13. Type quit and press Enter. The Metadata cleanup menu is displayed.

PowerShell

1 2	select operation target: q metadata cleanup:

14. Type remove selected server and press Enter.

You will receive a warning message. Read it, and if you agree, press Yes.

Sponsored

PowerShell

1 2 3

metadata cleanup: Remove selected server "CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net" removed from server "server100" metadata cleanup:

At this point, Active Directory confirms that the domain controller was removed successfully. If you receive an error that the object could not be found, Active Directory might have already removed from the domain controller.

15. Type quit, and press Enter until you return to the command prompt.

To remove the failed server object from the sites

16. In Active Directory Sites and Services, expand the appropriate site.
17. Delete the server object associated with the failed domain controller.

To remove the failed server object from the domain controllers container

18. In Active Directory Users and Computers, expand the domain controllers container.
19. Delete the computer object associated with the failed domain controller.

20. Windows Server 2003 AD might display a new type of question window, asking you if you want to delete the server object without performing a DCPROMO operation (which, of course, you cannot perform, otherwise you wouldn’t be reading this article, would you…) Select “This DC is permanently offline…” and click on the Delete button.

21. AD will display another confirmation window. If you’re sure that you want to delete the failed object, click Yes.

To remove the failed server object from DNS

22. In the DNS snap-in, expand the zone that is related to the domain from where the server has been removed.
23. Remove the CNAME record in the _msdcs.root domain of forest zone in DNS. You should also delete the HOSTNAME and other DNS records.

24. If you have reverse lookup zones, also remove the server from these zones.

Other considerations
Also, consider the following:

• If the removed domain controller was a global catalog server, evaluate whether application servers that pointed to the offline global catalog server must be pointed to a live global catalog server.
• If the removed DC was a global catalog server, evaluate whether an additional global catalog must be promoted to the address site, the domain, or the forest global catalog load.
• If the removed DC was a Flexible Single Master Operation (FSMO) role holder, relocate those roles to a live DC.
• If the removed DC was a DNS server, update the DNS client configuration on all member workstations, member servers, and other DCs that might have used this DNS server for name resolution. If it is required, modify the DHCP scope to reflect the removal of the DNS server.
• If the removed DC was a DNS server, update the Forwarder settings and the Delegation settings on any other DNS servers that might have pointed to the removed DC for name r