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

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!
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.

Walter PadrónCommented:
Demote the DC and then do a metadata cleanup,  see http://www.petri.co.il/delete_failed_dcs_from_ad.htm
Then install 2008R2 DC, see http://www.experts-exchange.com/Software/Server_Software/Active_Directory/Q_27719118.html

Best regards

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
Seth SimmonsSr. Systems AdministratorCommented:
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
lappladminAuthor Commented:
Seth - Do we really need to perform a force removal if the DC completely down? I mean hardware failed...
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Walter PadrónCommented:
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.
Seth SimmonsSr. Systems AdministratorCommented:
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
lappladminAuthor Commented:
Awesome guide. We were able to cleanup and promote the new 2008 server to a domain controller successfully!
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
Windows Server 2003

From novice to tech pro — start learning today.