2003 AD Child to Parent DC Replication is Tombstoned
Posted on 2009-05-06
We have a domain, child.parent.edmondok.com for example (parent.edmondok.com would be the example parent domain), whose 2 domain controllers (CDDC001 and CDBKU01) are not replicating to the 2 parent domain controllers (PD01 and PD02). Something happened back in Febuary 2008, and now CDDC001 and CDBKU01 are tombstoned (tombstone lifetime set to 60 days). Shows what happens when you bury your head in projects and don't check maintenance. It apparently isn't causing any issues, as the two domains don't have much interaction. We are upgrading to 2008, and I would like to get this taken care of before doing so.
I have read on other threads that there are two things we can do to resolve this. The most often recommended is to forcibly demote the DCs using dcpromo /forceremoval and then cleanup the metadata.
As both the child.parent.edmondok.com domain controllers are tombstoned, I'm not sure I should demote them both.
The other option is to run repadmin /removelingeringobjects on all the DCs (with the correct parameters including servername and serverGUID) and then force replication by modifying the "Allow Replication With Divergent and Corrupt Partner" reg key in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters" to 1. After replication I would set it back.
I believe the second option would be best in my case due to both child DCs having been tombstoned and just want to get verification that it is the best option.
Thanks for all comments and answers.