Another short blog posting (brevity is obviously my thing for 2014).
I occasionally come across environments in which Strict Replication Consistency is not enabled. This is invariably because these environment have forests that were created with Windows 2000 server, but which have subsequently been upgraded. If you need to know more about Strict Replication Consitency and why it is important for your AD environment, I don’t plan to bore you with the details here as this topic is well covered elsewhere. The best article I have found on the topic is this one.
The article makes the essential point that if the environment does not have SRC enabled then you need to do two things:
- Ensure the required registry key is configured on each DC. The quickest method to achieve this is using Repadmin as follows: repadmin /regkey * +strict
- Ensure any new DCs promoted within the forest automatically have SRC enabled by creating an operational GUID (actually a Container object in the Configuration Partition). There are several ways to create the object, but as you know, I’m a fan of Powershell, so here’s the code to do it:
# Strict Consistency - add operational GUID
$cnc = (get-adrootdse).configurationnamingcontext
$path = "CN=Operations,CN=ForestUpdates," + $cnc
$obj = "94fdebc6-8eeb-4640-80de-ec52b9ca17fa"
New-ADObject -Name $obj -Type container -Path $path -OtherAttributes @{showInAdvancedViewOnly="TRUE"}
Enjoy!