How to Remove a Failed Domain Controller

AID: 677
  • Status: Published

12250 points

  • Bymkbean
  • TypeTutorial
  • Posted on2009-05-22 at 09:21:07
Awards
  • Community Pick
  • Experts Exchange Approved

One of the tasks that every Active Directory administrator has to learn is how to remove a failed or offline Domain Controller (DC) from the environment.  The easiest method is to use DCPROMO, however if the DC is already offline or had a catastrophic failure this is not going to be an option.  You also don't want to leave it to the Garbage Collection process as you will have nagging issues within Active Directory (AD).  What you need to do is remove the DC's metadata info from AD.  This involves using a command called NTDSUTIL.  NTDSUTIL is a command line tool that allows you to perform some of the more advanced Active Directory maintenance tasks.

Below are the steps needed to remove a failed or offline Domain Controller from your environment.  I have included additional steps that are needed to remove the leftover data in Active Directory Sites and Services as well as DNS.  Those two areas are often overlooked.

Step by Step Procedure


1. Open the Command Prompt

2. Type:
ntdsutil
                                    
1:

Select allOpen in new window

(all the commands will be entered via this command prompt)

3. Type:  
metadata cleanup
                                    
1:

Select allOpen in new window



TIP: NTDSUTIL does not require the full command to be entered; you only have to enter enough of the command that is unique.  For Example, instead of typing metadata cleanup you could just type met cle or better yet m c.


4. Type:  
connections
                                    
1:

Select allOpen in new window



5. Type:
connect to server <ServerName>
                                    
1:

Select allOpen in new window

replace <ServerName> with the name of a functional DC in your environment, even if you are logged in locally.  

6. Type:
quit 
                                    
1:

Select allOpen in new window



7. Type:  
select operation target 
                                    
1:

Select allOpen in new window



8. Type:
lists sites 
                                    
1:

Select allOpen in new window



9. Type:
select site <#> 
                                    
1:

Select allOpen in new window

where <#> is the site where the failed or offline DC resided

10. Type:
list servers in site 
                                    
1:

Select allOpen in new window



11. Type:
select server <#>  
                                    
1:

Select allOpen in new window

where <#> is the DC that is failed or offline

12. Type:
list domains 
                                    
1:

Select allOpen in new window



13. Type:
select domain <#> 
                                    
1:

Select allOpen in new window

where <#> is the domain where the failed or offline DC resided (at this point you should verify that the site, server and domain are all selected)

14. Type:
quit 
                                    
1:

Select allOpen in new window

(this should set you back to the metadata cleanup menu)

15. Type:
remove selected server 
                                    
1:

Select allOpen in new window

(a warning message will pop up, verify that this is the correct DC, in fact get a peer to verify it for you too)

16. Click Yes

17. Open Active Directory Sites and Services

18. Expand out the site that the failed or offline DC resided in

19. Verify the DC cannot be expanded out (no connection objects and such)

20. Right Click the DC and select Delete  

21. Close Active Directory Sites and Services

22. Open DNS Manager

23. Expand the zones where this DC was also a DNS server and perform the following steps

24. Right click the zone and select Properties  

25. Click the Name Servers tab  

26. Remove the failed or offline DC from the Name Servers tab  

27. Click OK to also remove the HOST (A) or Pointer (PTR) record if asked

28. Verify the zone no longer has a DNS record for the failed or offline DC

29. Make sure that none of your existing DCs, Clients, and/or DHCP Scopes is using the failed or offline DCs IP for DNS.  

Asked On
2009-05-22 at 09:21:07ID677
Tags

Active Directory

,

DCPROMO

,

NTDSUTIL

,

Domain Controller

Topic

Active Directory

Views
12273

Comments

Expert Comment

by: Mr-Madcowz on 2010-04-15 at 08:49:14ID: 13260

Hi,

Shouldn't Step 7:

Type select operations target

read:

Type select operation target

Add your Comment

Please Sign up or Log in to comment on this article.

Join Experts Exchange Today

Gain Access to all our Tech Resources

Get personalized answers

Ask unlimited questions

Access Proven Solutions

Search 3.2 million solutions

Read In-Depth How-To Guides

1000+ articles, demos, & tips

Watch Step by Step Tutorials

Learn direct from top tech pros

And Much More!

Your complete tech resource

See Plans and Pricing

30-day free trial. Register in 60 seconds.

Loading Advertisement...

Top Active Directory Experts

  1. mkline71

    412,697

    Wizard

    3,000 points yesterday

    Profile
    Rank: Genius
  2. dariusg

    163,412

    Guru

    0 points yesterday

    Profile
    Rank: Genius
  3. dvt_localboy

    136,278

    Master

    0 points yesterday

    Profile
    Rank: Sage
  4. demazter

    116,263

    Master

    0 points yesterday

    Profile
    Rank: Genius
  5. iSiek

    113,702

    Master

    0 points yesterday

    Profile
    Rank: Genius
  6. motnahp00

    92,762

    Master

    0 points yesterday

    Profile
    Rank: Sage
  7. acbrown2010

    81,763

    Master

    10 points yesterday

    Profile
    Rank: Genius
  8. Jmoody10

    71,214

    Master

    1,210 points yesterday

    Profile
    Rank: Wizard
  9. yo_bee

    68,718

    Master

    0 points yesterday

    Profile
    Rank: Guru
  10. kevinhsieh

    60,310

    Master

    0 points yesterday

    Profile
    Rank: Genius
  11. KenMcF

    56,098

    Master

    0 points yesterday

    Profile
    Rank: Genius
  12. snusgubben

    55,438

    Master

    0 points yesterday

    Profile
    Rank: Sage
  13. pwindell

    54,060

    Master

    2,800 points yesterday

    Profile
    Rank: Genius
  14. KCTS

    52,196

    Master

    0 points yesterday

    Profile
    Rank: Genius
  15. leew

    51,399

    Master

    0 points yesterday

    Profile
    Rank: Savant
  16. PrashantGirennavar

    46,884

    3,000 points yesterday

    Profile
  17. Neilsr

    46,472

    0 points yesterday

    Profile
    Rank: Genius
  18. xxdcmast

    42,972

    1,100 points yesterday

    Profile
    Rank: Genius
  19. Anuroopsundd

    38,834

    0 points yesterday

    Profile
    Rank: Sage
  20. dstewartjr

    37,595

    0 points yesterday

    Profile
    Rank: Genius
  21. RobSampson

    36,382

    0 points yesterday

    Profile
    Rank: Genius
  22. ve3ofa

    34,856

    1,800 points yesterday

    Profile
    Rank: Genius
  23. amitkulshrestha

    34,647

    0 points yesterday

    Profile
    Rank: Genius
  24. alanhardisty

    32,393

    0 points yesterday

    Profile
    Rank: Genius
  25. McKnife

    32,203

    2,000 points yesterday

    Profile
    Rank: Genius

Hall Of Fame