0

I have the following setup:

  • Two Domain Controllers in different sites (both Windows Server 2016) -The sites are permanently connected via a VPN (so the servers can directly reach each other)
  • The Domain Controllers are in different subnets
  • The Domain Controllers are both Global Catalogs

The problem I have is with the syncing/replication of SYSVOL content. It was syncing fine, but after the reboot of one of the servers it doesn't seem to sync/replicate anymore, while GPOs still sync/replicate without any problem.

Are there any ways to debug the replication of the SYSVOL content, or tools you would recommend to monitor the SYSVOL replication?

Thanks

Fionn
  • 475
  • 5
  • 15
  • Have you verified that both servers are pointing to the same DNS? – uSlackr Aug 02 '18 at 15:59
  • 1
    `It was syncing fine, but after the reboot of one of the servers it doesn't seem to sync/replicate anymore, while GPOs still sync/replicate without any problem.` If GPO's are replicating, you need to tell us what is *not* replicating. There really should not be much in SYSVOL, except for some basic scripts. – Greg Askew Aug 02 '18 at 16:05
  • Well I was trying to replicate a startup script. – Fionn Aug 02 '18 at 19:07
  • `The problem I have is with the syncing/replication of SYSVOL content. It was syncing fine, but after the reboot of one of the servers it doesn't seem to sync/replicate anymore, while GPOs still sync/replicate without any problem.` - How are you determining this? What are you using to diagnose the problem? What is it that you're looking at? – joeqwerty Aug 02 '18 at 20:09
  • @Fionn - Is [this question on SO](https://stackoverflow.com/questions/51659328/gpos-no-longer-sync-permissions-after-applying-kb4338814-to-server-2016) related? – Am_I_Helpful Aug 04 '18 at 18:55
  • Have you run dcdiag on each DC and verified the tests pass on both of them? – user5870571 Dec 01 '20 at 02:51

1 Answers1

0

Have you checked the Event log under Application and Services Log in event viewer it could be related to file replication service and the DC could be in one of the following states:

Assertions in the FRS service Corruption of the local jet database Journal wrap errors FRS replication failures

This article might be able to help. https://support.microsoft.com/en-us/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi

Lake29
  • 41
  • 3