We help IT Professionals succeed at work.

Turned off Domain Controller

I have a Windows 2008 R2 server that was used as an ADMT server for migrating 2 separate domains into a new single domain.  The current domain is a Windows 2012 domain.  A while ago, a network refresh occurred and someone shut this server down and never powered it back up.  This has been about 3 months.  I would like to decommission it, but I'm afraid to power it back on to demote it and remove it from the domain.  My fear would be reverse replication where it pushes old Active Directory data to our good domain controllers.  Would that happen?  Could that happen?  Should I just treat it as an orphaned domain controller and try to manually get rid of it?  Or is it safe to power it on and demote it?  Thanks!

Watch Question

Solutions Architect
It won't be treated as orphaned (tombstoned), by default for 2008 I think was 180 days.  The update sequence numbers on all objects would have moved beyond what the 2008 server currently has on it.  So I don't think there would be any ill effects.  So I would feel ok turning it on to DCPromo it down.

That being said, if you are paranoid, you can do a metadata cleanup to get rid of it:

... and you don't have to be concerned with back replication
Top Expert 2013
If it has been off longer than the tombstone lifetime (180 or 60 days by default) then it won't replicate when it comes back online.

If it doesn't promote cleanly then you can do a force removal and metadata cleanup.   If you want you can also delete that computer object (metadata cleanup will happen)

Check your tombstone lifetime


Will SzymkowskiSenior Solution Architect
Most Valuable Expert 2015
Top Expert 2015
Just for added measure, if the DC's will bootup then always do a clean demotion. Also make sure that this DC does not hold any of the FSMO roles either. If it does it would be especially necessary to transfer the roles clean and then demote it.

A side from that everything else should be fine.