Updating primary domain controller
If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved.
This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
View the event details for more information on the file name and path that caused the failure.If all has gone well, each of your shared SYSVOL folders on your DCs should contain the same amount of policies and your client should successfully pull down all policies.Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.Visit Stack Exchange The issue is that when we connect remotely to the secondary domain controller, it still accepts the old password, and not the new one.
It also has an outdated version of AD users and and old version of the DNS server, it is like it has stopped updating itself from the primary domain controller.
Visit Stack Exchange In my domain there are two domain controllers, there is a gap of 3 minutes between their times and than I can find this difference between many clients (it depends on their DC). MYDOMAIN.locale *** PDC ***[10.0.0.3]: ICMP: 0ms delay NTP: 0.0000000s offset from SRVDC1.