Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So a 2003 DC crashed in a branch office. All it did was local authentication, dns, and dhcp. I have the server fixed now but I would think there is a few things I should do before I use dcpromo and put the server back on the network. What would be the right way to do this?

share|improve this question
I will be using the same name and same IP address unless other wise advised – evolvd May 20 '11 at 1:26
up vote 1 down vote accepted

It's not clear whether you've re-installed the OS on this system; that's a big factor. The other question is whether you're keeping the same name on the server as it had before.

I'm going assume that you've re-installed the OS, and that the same name will be used. Correct me if that's not the case, and I'll edit the answer.

A lot of the cruft that you'd normally have to clean up will be picked back up by using the same name. That said, you'll want to clean up the metadata before doing the re-promote:

ntdsutil metadata cleanup remove selected server "servername"

What this accomplishes is to clear FRS links, seize FSMO roles (confusion over those when the DC comes back could be ugly, though dcpromo ought to handle that condition), and nuke the object out of AD Sites and Services and replication links (I don't buy that this part is necessary unless you've built manual replication connections, as they're normally automatically created).

That should cover it, take care of that then feel free to re-join the domain and re-promote.

share|improve this answer
Sounds good! Great answer! – evolvd May 20 '11 at 1:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.