Group Policy changes not replicating between domain controllers

2017-12-11T16:24:16+00:00 May 13th, 2015|Azure, Cloud|

One of our customers reported that changes to group policies were not being replicated correctly. After testing the theory ourselves we could see the policy files versions were not succinct.

So I hopped onto the event logs and started trawling through. After forcing replication there didn’t seem to be any errors or in fact any events logged so I looked further back and found the below event from early in the morning:

 

The full error actually gives us the remediation steps!

The File Replication Service has detected that the replica set “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)” is in JRNL_WRAP_ERROR.

Replica set name is : “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”

Replica root path is : “c:windowssysvoldomain”

Replica root volume is : “.C:”

A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

[1] Volume “.C:” has been formatted.

[2] The NTFS USN journal on volume “.C:” has been deleted.

[3] The NTFS USN journal on volume “.C:” has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.

[4] File Replication Service was not running on this computer for a long time.

[5] File Replication Service could not keep up with the rate of Disk IO activity on “.C:”.

Setting the “Enable Journal Wrap Automatic Restore” registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.

[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run “net stop ntfrs” followed by “net start ntfrs” to restart the File Replication Service.

[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.

Click down the key path:

“SystemCurrentControlSetServicesNtFrsParameters”

Double click on the value name “Enable Journal Wrap Automatic Restore” and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

So I followed the instructions and added the registry key and gave it a value of 1. Sure enough we got the follow event was logged the next time replication was attempted (around 5 mins):

It auto copies the old sysvol contents just in case for you into the same locations “NtFrs_PreExisting” folder.

5 minutes later it started adding it back in and I saw the sysvol start to populate:

And finally:

And sure enough I retested and replication seemed fine!

Hope it helps!