Windows Time Settings
Set the PDC Time
-
First, locate your PDC Server. Open the command prompt and type:
netdom /query fsmo
-
Log in to your PDC Server and open the command prompt.
- Check if the PDC is a HyperV VM
- If it is, log into the host
- Right-click on the VM and open the properties
- On the left, go down to the services and turn off the time sync service
- Return to the PDC and continue
-
Stop the W32Time service:
net stop w32time
-
Configure the external time sources
w32tm /config /syncfromflags:manual /manualpeerlist:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org” /update
-
Make your PDC a reliable time source for the clients.
w32tm /config /reliable:yes
-
Start the w32time service:
net start w32time
-
The Windows time service should begin synchronizing the time. You can check the external NTP servers in the time configuration by typing:
w32tm /query /configuration
Fix the time source on a domain member
-
Check the current settings
w32tm /query /status
Most likely, it will return something similar to the following, pay attention to the source.
Leap Indicator: 3(not synchronized) Stratum: 0 (unspecified) Precision: -23 (119.209ns per tick) Root Delay: 0.0000000s Root Dispersion: 0.0000000s ReferenceId: 0x00000000 (unspecified) Last Successful Sync Time: unspecified Source: Local CMOS Clock Poll Interval: 10 (1024s)
-
Restart the time service
net stop w32time net start w32time
-
Update the settings
w32tm /config /update
-
Sync settings from the domain
w32tm /resync /rediscover
-
Confirm it is querying the domain now
w32tm /query /status
It should return something similar to the following, note the updated source.
Leap Indicator: 0(no warning) Stratum: 4 (secondary reference - syncd by (S)NTP) Precision: -23 (119.209ns per tick) Root Delay: 0.0475434s Root Dispersion: 14.8991085s ReferenceId: 0xC0A803E3 (source IP: 192.168.3.227) Last Successful Sync Time: 7/15/2019 1:21:37 PM Source: DC1.domain.local Poll Interval: 10 (1024s)