Since not specific which DC has problem and new change in SYSVOL folder can be propagate each other now, solved by this link lastly.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/ntfrs-added-to-folder-name
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
A client site has two server 2012 DC which has sysvol replication problem using FRS.
dcdiag - all passed
net share netlogon and sysvol - normal
can ping each other using FQDN - normal
When test to place a file "abc.txt" on DC1\netlogon, "abc.txt" wasn't copied to DC2\netlogon.
Then tried the following steps.
dcdiag - both DC server will have the following results
Starting test: FrsEvent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
Ever restart server but still not help.
Then repeat above steps and find that there are a lot of folders in sysvol.
The replication is solved suddenly now. Can we delete "Polices_NTFRS...." files directly in picture safely? Please help.
Since not specific which DC has problem and new change in SYSVOL folder can be propagate each other now, solved by this link lastly.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/ntfrs-added-to-folder-name
Safer method may be to move roles off, demote server, do cleanup, reboot, promo the problematic one again.
--please don't forget to Accept as answer if the reply is helpful--