![]() ![]() ![]() demote forcefully, clean AD database, promote again and let it replicate.Ī. HKLM\System\CurrentControl Set\Servic es\NTDS\Pa rameters\A llow Replication With Divergent and Corrupt Partner and replicateī. I have came across several articles where there were two suggestions either toĪ. Tombstone was still 60 days instead of 180 days because we migrated from 2003 to 2008 as far i understood from tech notes that value wouldn't change if original value was 60 days. Originally domain was at Windows Server 2003 where tombstone interval was originally default and at 60 days (as far as the documents i found had true source), then we migrated all domain controllers to Windows 2008 R2 Standard, once they were all at 2008 we raised the Domain Functional Level to 2008 R2. The Forest has around 20 DCs, one DC for each physical location, main site has two DCs.Įach physical AD Site replicates to either of main site DCs using only 1 link to either of them.Įntire env is virtual so creating new servers wont be a problem. Thru combination of dcdiag, repadmin, ADSiEdit I found that one of my clients servers past its tombstone time and became disconnected. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |