Also, from the above article, try to run dcpromo with the forceremoval switch, if you're dead set on running this server in your forest without rebuilding it.

from the run line, try dcpromo /forceremoval

 

It would seem formatting is the easiest solution...why not do that?

 

Yeah, but it's my AV server as well...

I have Dell coming out for the hardware issues tomorrow, then I'll try the forceremoval switch and metadata cleanup...

These were the answers I was looking for.

for you and Vader!!!

 

Well, I forced the demotion (while the POS was actually running)... After I get the offending hardware replaced, I'll have to play with the metadata cleanup.

One question I have is, "If I can't connect to the server that needs to be removed from AD (as a DC) from a good DC, how do I remove it using ntdsutil with the metadata cleanup switch?"

 

Here is an article explaining how to do it. You run ntdsutil on an active DC in the forest. You don't need to be able to talk to the old DC that you are removing from the schema.

If it was still on-line, the premise would be that there is nothing wrong and no need to "clean up" the metadata in the AD schema.

Remember, you're telling your AD that "this DC no longer exists, so I want to remove all references to it in AD".

http://www.petri.co.il/fix_unsuccessful_demotion.htm

 

So, Bruzr, what happened? How does the story finally end?

 

Just got it rejoined to the domain yesterday late afternoon... It's just a member now with no fights...