dcpromo /forceremoval on working DC to get rid of failed DC?

I have a remote DC that stopped replicating, "access denied" message. I 'm having it shipped back for a rebuild. MS support said to run the dcpromo /forceremoval from a working domain controller. Is this correct? I thought you would run it from the non-working DC. I'm just worried of forcefully demoting a good DC. Thanks!
Who is Participating?
Mike KlineConnect With a Mentor Commented:
That is not correct, DO NOT  run /forceremoval on a working DC.

What you do from a working domain controller is metadata cleeanup  http://www.petri.co.il/delete_failed_dcs_from_ad.htm  

Are you sure that is not what they said/meant?

So if you can log into the box you can do the following

On "bad" box run dcpromo /forceremoval http://blogs.technet.com/b/asiasupp/archive/2006/09/06/454327.aspx

metadata cleanup (per previous link)
if the box held any FSMO roles you can seize those roles (guessing it didn't hold FSMO roles)

Then if you want you can add it back to the domain and repromote.

If you can't log into the box and it is totally dead still go through the metadata cleanup.


waleedaConnect With a Mentor Commented:
you are right

you should run on the bad one not on the good one, take care
RickSheikhConnect With a Mentor Commented:
I agree they must have meant the metadata cleanup from a working DC. If you are gonna rebuild it (as in rebuild of the OS) and not just force demote (via /forceremoval) and repromote, then the /forceremoval should not even be needed. Metadata cleanup however is a must.
dcs-userAuthor Commented:
Thanks everyone. I wanted a sanity check before proceeding.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.