Looking for a guide to demote a failed 2003 dc and comprehensive guide to promote a new 2008r2 DC

Posted on 2014-12-02
Last Modified: 2014-12-09
Hello Experts,

We have two domain controllers and both are running Windows Server 2003 Enterprise. One of them failed 3 months ago and it will not replicate anymore as it reached the tombstone period. We know that demoting a failed server only takes us about 5-10 mins as this is only apply to the perfect world. Currently the failed server is completely inaccessible and we are looking for a comprehensive guide to demote our failed server and promote one of our new server running windows 2008 R2.  We've read some articles on Microsoft website suggested to perform a dcpromo /forceremoval  on the failed dc and perform a meta cleanup on the primary domain controller. Or if there are some other methods that we can perform please let us know. Our goal is get this fix as soon as we can. Thank you for your time!
Question by:lappladmin
  • 2
  • 2
  • 2
LVL 10

Accepted Solution

Walter Padrón earned 250 total points
ID: 40477107
Demote the DC and then do a metadata cleanup,  see
Then install 2008R2 DC, see

Best regards
LVL 34

Assisted Solution

by:Seth Simmons
Seth Simmons earned 250 total points
ID: 40477233
you are correct; do a force removal and metadata cleanup (link above is ok to use)
if this server had FSMO roles, seize them on another domain controller first

Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller

Author Comment

ID: 40478881
Seth - Do we really need to perform a force removal if the DC completely down? I mean hardware failed...
Swamped with email signature updates?

Have you been given a load of changes to make to your users’ email signatures? Having to manually implement multiple signatures for every department? Let Exclaimer save you from being swamped with email signature updates!

LVL 10

Expert Comment

by:Walter Padrón
ID: 40478899
No, if the hardware is failed and you never brings back online the server the only thing you need to do is metadata cleanup and seize the roles if the server holds one.
LVL 34

Expert Comment

by:Seth Simmons
ID: 40479882
sorry...your explanation seemed a bit confusing
if the hardware is dead then yes, do a metadata cleanup
i imagine there is a plethora of replication warnings and errors on the active domain controller

Author Comment

ID: 40489682
Awesome guide. We were able to cleanup and promote the new 2008 server to a domain controller successfully!

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Resolve DNS query failed errors for Exchange
Synchronize a new Active Directory domain with an existing Office 365 tenant
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now