Sysvol Replication error

[msi_school]

Hi

 

In February I turned off Two DCs meaning to decommission them and with one thing and another I forgot and they tombstoned, I have manually removed these and cleaned up the metadata but I am still having problems with the Sysvol not syncing the error I am getting is:

 

The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 260 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.

 

The guidance to resolve this is to remove the server from the replication group using the DFS Management snap in and then add it back to force a resync however I have never done this before and am hoping for some guidance.

 

I can't see a method of removing the server from the group the only option is to remove the group from display and there is a message telling me that some options are not available because this is a Sysvol replication group. Am I going about this correctly or is there a better way to resolve this?

 

Thanks

 

Mike

[HPlum78]

Did you get this resolved? The sysvol is not usually displayed in the dfs management console for its own protection... Edited October 31, 2020 by HPlum78

[msi_school]

I have not resolved this, obviously it has been broken for almost a year and has not caused any noticeable errors so I am going slow as I don't want to break the sysvol any more than it is.

 

The guidance for using the DFS management snap in ius from the original error message in Dcdiag

 

Group Policy problems.

An error event occurred. EventID: 0xC0000FAC

 

Time Generated: 10/28/2020 13:05:40

 

Event String:

 

The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 260 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.

 

To resume replication of this 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.

 

 

The DFS Management snap in shows the Sysvol but other than running reports does not give you any options. Does anyone have any ideas I have seen some discussion of running non authoritative sync but I think most of this advice is aimed at DFS issues and not Sysvol issues.