If you find that the clock on your domain-joined Windows 7 computer has the incorrect time, you can troubleshoot the problem and resynchronize with your NTP server as follows. Begin by opening an admin-level command prompt and typing w32tm /query /status to display which server your computer is getting its time from:
C:\Users\Administrator.FABRIKAM>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 2 (secondary reference – syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0624001s
Root Dispersion: 0.0100000s
ReferenceId: 0x564D5450 (source IP: 86.77.84.80)
Last Successful Sync Time: 6/10/2010 9:36:20 AM
Source: VM IC Time Synchronization Provider
Poll Interval: 10 (1024s)
Here the Windows 7 computer is a virtual machine running on a Hyper-V host, and for some reason the time on the host is set incorrectly.
Now type w32tm /resync /rediscover to force a new time synchronization with the configured time server for the domain:
C:\Users\Administrator.FABRIKAM>w32tm /resync /rediscover
Sending resync command to local computer
The command completed successfully.
Run the w32tm /query /status command again to see where the time is now coming from:
C:\Users\Administrator.FABRIKAM>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 3 (secondary reference – syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0312500s
Root Dispersion: 7.8170376s
ReferenceId: 0xAC100B0A (source IP: 172.24.11.10)
Last Successful Sync Time: 6/10/2010 10:07:09 AM
Source: NYC-DC-01.fabrikam.com
Poll Interval: 10 (1024s)
Your computer's time is now coming from the domain controller in the Fabrikam domain as expected.
If you have feedback concerning this tip, please email me. And be sure to check out my website!
