F
forgiven
1 Server 2016 as DC0 and 1 2102R2 server as DC1 both are hyper-v VM's. It appears we have a timebomb that has expired and now replication doesn't work. Here is one of the errors:
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 204 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.
Additional Information:
Error: 9061 (The replicated folder has been offline for too long.)
Replicated Folder Name: SYSVOL Share
When i load up the DFS snapin, i do not have an option to remove just the server. I checked DC0 and its SYSVOL is NOT shared in computer management->shares. DC1 DOES have SYSVOL shared in computer management->shares.
So, if i want to force a non-authoritative sync, i should do this from the DC that does NOT have its sysvol shared, right?
Continue reading...
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 204 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.
Additional Information:
Error: 9061 (The replicated folder has been offline for too long.)
Replicated Folder Name: SYSVOL Share
When i load up the DFS snapin, i do not have an option to remove just the server. I checked DC0 and its SYSVOL is NOT shared in computer management->shares. DC1 DOES have SYSVOL shared in computer management->shares.
So, if i want to force a non-authoritative sync, i should do this from the DC that does NOT have its sysvol shared, right?
Continue reading...