DFS replication issues

Vard0 

To resume replication of the folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.

I would suggest trying the below.

• Stop the DFS Replication Service: net stop DFSR
• In the ADSIEDIT.MSC tool, modify the following DN and two attributes on the domain controller you want to make authoritative (preferably the PDC Emulator, which is usually the most up to date for SYSVOL contents):
  • CN=SYSVOL Subscription,CN=Domain System Volume,CN=DFSR-LocalSettings,CN=<the server name>,OU=Domain Controllers,DC=<domain>
    • msDFSR-Enabled=FALSE
    • msDFSR-options=1

Here is where you will find that key:

• Start the DFS Replication service: net start DFSR
• You will see Event ID 4114 in the DFSR event log indicating SYSVOL is no longer being replicated
• On the same DN above, set it back to TRUE: msDFSR-Enabled=TRUE
• Force Active Directory replication throughout the domain and validate its success on all DCs: repadmin /syncall /AdP
• Run the following command from an elevated command prompt on the same server that you set as authoritative: DFSRDIAG POLLAD
• You will see Event ID 4602 in the DFSR event log indicating SYSVOL has been initialized. That domain controller has now done a “D4” of SYSVOL.