The local policy might be overriding the settings but the PDC FSMO should have the following:ġ. computer-configuration > administrative-template > system > windows-time-service.If you see "(Policy)", then the setting is set by policy and overrides your manual settings. reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\\TimeProviders.reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters.reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config.reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\.w32tm /query /configuration | findstr /i policy.I had a really strange issue where the clock would not use the external servers. External-check: $w32tm /monitor /computers:.Internal: $w32tm /config /syncfromflags:manual /manualpeerlist:192.168.1.1 /reliable:yes /update.External: $w32tm /config /syncfromflags:manual /manualpeerlist:"0. 1. 2. 3." /reliable:yes /update.
-set the server to a working NTP server.-if you get an error, check to see if an internal NTP server is working.-check to see if an external NTP server is working.You can check to see if a NTP Server is working. -click SETTINGS (on the right-hand side).If it is a VIRTUAL-OS, disable TIME-SYNCHRONIZATION from the HYPER-V settings: $w32tm /config /syncfromflags:domhier /update.If for some reason, a domain-client doesn't, then force it: The domain-clients should automatically get their time from the server. $w32tm /config /syncfromflags:manual /manualpeerlist:"0. 1. 2. 3." /reliable:yes /update.The domain-server should be set to sync with an external source. You can have more but it would be redundant. There should only be one NTP SERVER on the network.
0 kommentar(er)
