Windows Server / Active Directory & Group Policy
Check SYSVOL replication backlog between known partners
A controller can have an older policy copy when DFS Replication does not keep up. Inspect backlog in the correct direction between known partners.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-DfsrBacklog -GroupName 'Domain System Volume' -FolderName 'SYSVOL Share' -SourceComputerName DC01 -DestinationComputerName DC02 -VerboseRead the result
With DFSR tools and approved access, the command reports backlog information for the chosen replication relationship. Direction matters and a snapshot can change rapidly.
Resolve and verify
Compare repeated backlog and DFSR events on both partners. Resolve connectivity, service or replication-state issues through the documented SYSVOL recovery process.
Before changing production
Do not perform an authoritative SYSVOL restore simply because a backlog is nonzero.