Enables and disables the values for two registry keys located under HKLM\system\ccs\services tds\parameters "allowDivergent" ...

     Enables and disables the values for two registry keys located under 
     HKLM\system\ccs\services
tds\parameters


     "allowDivergent" || "strict"


     allowDivergent for "Allow Replication With Divergent and Corrupt Partner"
   
     When a Windows Server 2003 domain controller has not inbound replicated a 
     directory partition from any source in the preceding tombstone lifetime 
     number of days, it logs NTDS Replication event 2042, then quarantines 
     inbound replication from that source DC. 

     Event 2042 indicates that replication can be unblocked by modifying 
     "Allow Replication With Divergent and Corrupt Partner" in the registry 
     to a value of 1. 

     This replication quarantine should only be relaxed after checking for 
     lingering objects, and removing them if present. 

     "repadmin  /regkey - allowDivergent" provides a reliable method 
     to relax "Allow Replication With Divergent and Corrupt Partner" on one or 
     more domain controllers in a forest.

     [SYNTAX]

     repadmin /regkey  <{+|-}key> [value [/reg_sz]]

     [EXAMPLE]

     set "Allow Replication With Divergent..." on a single DC

     repadmin /regkey dc01.contoso.com +allowDivergent 
     
     set "Allow Replication With Divergent..." on a all DC's

     repadmin /regkey GC: +allowDivergent               

     set "Allow Replication With Divergent..." on a all GC's

     repadmin /regkey * +allowDivergent                 



     strict for "Strict Replication Consistency"

     Determines how a destination domain controller behaves when a source domain
     controller sends an update (as opposed to an object create) for an object 
     that does not exist in the destination DC's copy of Active Directory. This
     behaviour is indicative of a lingering object being sent from the source DC
     to the destination dc. 

     When strict replication consistency is enabled, the destination DC halts 
     inbound replication from the source with and logs NTDS Replication events 
     1388, and Event 1084 with the extended error "there is no such object on
     the server" identify and attempt by the source DC to send a lingering 
     object to the destination.

     When loose replication consistency is enabled, the destination DC 
     reanimates the object sent by the DC and inbound replication is allowed to 
     continue. 

     The default value for replication consistency is determined by the how 
     your Active Directory forest was created. Strict replication consistency 
     quarantine lingering objects for easier removal but requires monitoring 
     diligence. 

     "repadmin  /regkey +|- strict" provides a reliable way 
     to configure values for the "Strict Replication Consistency" 
     on one or more domain controllers in a forest. 
     

     [SYNTAX]

     repadmin /regkey  <{+|-}key> [value [/reg_sz]]

     [EXAMPLE]

     enable strict replication consistency on all DC's in forest

     repadmin /regkey * +strict     

     enable strict replication consistency on all GC's in forest

     repadmin /regkey gc: +strict    

     disable strict replication consistency on all DC's in forest

     repadmin /regkey * -strict