Second domain controller crashed today and will not boot back up. How can I clean up active directory 2008r2??

It has been one of those days. Today I noticed a newly created mailbox had vanished and after some research I noticed that only or DC2 had the new active directory account in its ADUC. I tried to force replication but got errors, so I went ahead and rebooted DC2 and it never came back up.  Now I am stuck with a bogus DC listed in my sites and services. I know this is not healthy and want to properly remove DC2, but it looks like it is shot and will never boot again. How can I clean up AD without actually having the server to demote? BTW this is not related to my other DC question I have out there. Like I said, it has been one of those days!!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You need to seize the FSMO roles from the dead server.
Seize FSMO roles
To seize the FSMO roles by using the Ntdsutil utility, follow these steps:

    Log on to a Windows 2000 Server-based or Windows Server 2003-based member computer or domain controller that is located in the forest where FSMO roles are being seized. We recommend that you log on to the domain controller that you are assigning FSMO roles to. The logged-on user should be a member of the Enterprise Administrators group to transfer schema or domain naming master roles, or a member of the Domain Administrators group of the domain where the PDC emulator, RID master and the Infrastructure master roles are being transferred.
    Click Start, click Run, type ntdsutil in the Open box, and then click OK.
    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 to.
    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, or see the list of roles at the start of this article. 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.
    At 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.

For more details see:

Once complete you can remove the  dead DC
To remove dead or orphaned D.C. you can go to Active Directory Users and Computers, then go to Domain Controllers OU, then you will see the list of Domain Controllers you can directly delete it with the following options which tells you what is the right action you will do, and don't forget to go to Active Directory Sites and Services to fully delete also the DC which is no longer use and no longer active to eliminate the error messages like NTDS.

     If you have also a Windows Based DNS Server delete also these entries at Forward Lookup Zones:

     1.)  (same as parent folders)   (Host A)   <IP Address of the dead Domain Controller>
     2.)  <DC Server Name>   (Host A)   <IP Address of the dead Domain Controller>

     At Reverse Lookup Zones:

     1.)  <IP Address of the dead Domain Controller>   Pointer (PTR)   <>
Mike KlineCommented:
The second part of Craig's answer is known as a "metadata cleanup"  more iformation on that here

How many DCs do you currently have up and running?


Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Thor2923Author Commented:
I only have one more DC on this subnet, but 4 more DCs are located in 2 other offices and one newly introduced "sickly" DC in another new office. The last DC is another story and I have another thread going to try and clean that up, although my "sickly" DC probably has to be demoted and reinstated, I have no replication working on it. But to answer your question, I now have 5 functioning DCs on my network and only one in my home office
Mike KlineCommented:
ok good so you have more than 2 so that is why I asked.  


SandeshdubeySenior Server EngineerCommented:
As other suggested to need to perfrom metadata cleanup to remove the instances of faulty DC.If the faulty server is fsmo role holder server you also need to sieze fsmo role.

Complete Step by Step Guideline to Remove an Orphaned Domain controller (including seizing FSMOs, running a metadata cleanup, and more)

I will also recommend to verify the health of other DCs by dcdiag /q and repadmin /replsum and post the og if error is reoprted.You also need to ensure that clients now point to online DC for there preferred dns setting as faulty DC instances will be removed this may be in TCP/IP or dhcp setting.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.