InSearchOf
asked on
AD replication errors.
One of my DCs running 2008 R2 is logging a lot of event id 1096 errors in my system log.
The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object LDAP://CN=Machine,cn={DEF2 9BE2-8436- 465E-A5F8- ABAEBED31C 1D},cn=pol icies,cn=s ystem,DC=D omain,DC=O RG. Group Policy settings will not be resolved until this event is resolved. View the event details for more information on the file name and path that caused the failure.
I also see event 13568 errors in the File Replication Service under Applications and Service Logs
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
I also notice the SYSVOL folder is not the same size as my other DCs. Its replication partner has the correct size of entries as compared to other DCs.
The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object LDAP://CN=Machine,cn={DEF2
I also see event 13568 errors in the File Replication Service under Applications and Service Logs
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
I also notice the SYSVOL folder is not the same size as my other DCs. Its replication partner has the correct size of entries as compared to other DCs.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Arnold nailed it. Once you get the issue resolved, you should seriously consider migrating SYSVOL from FRS to DFSR, as it's much more stable:
https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405
Make sure you get the issue fixed first, though, or the migration will fail.
https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405
Make sure you get the issue fixed first, though, or the migration will fail.
ASKER
Thanks for the help. Problem solved. I followed the instructions on the Event ID.
ASKER