Windows useful commands to troubleshoot time issues

December 23, 2018 by Munkhtuvshin Baatar
No comments
  • w32tm /query /status (see source and ReferenceId, in AD output should NOT be “Source: Local CMOS Clock” or “VM IC Time Synchronization Provider”, nor “Free-running System Clock” – maybe need to run below two commands)
  • net time /set
  • net stop/start w32time
  • to compare time on DCs for small companies with only several AD DCs – for example from powershell: “net time \\dc00″,”net time \\dc01″,”net time \\dc02″,”net time \\dc03″,”net time \\dc04” | ForEach-Object {cmd.exe /c $_}
  • for PDC emulator role:       
  • w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:manual /reliable:yes /update
  • to reset computer time settings in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters:
  • net stop w32time
  • w32tm /unregister  
  • w32tm /register
  • net start w32time
  • w32tm /resync

If you need to compare local and remote time:

w32tm /stripchart /computer:dc00
Tracking dc00 [192.168.1.10:123].
The current time is 1/15/2019 8:26:22 PM.
20:26:22, d:+00.0017563s o:+00.0274519s [ * ]
20:26:24, d:+00.0014726s o:+00.0354117s [ * ]
20:26:26, d:+00.0029066s o:+00.0262283s [ * ]
20:26:28, d:+00.0017425s o:+00.0309692s [ * ]
20:26:30, d:+00.0015372s o:+00.0361298s [ * ]
20:26:32, d:+00.0013512s o:+00.0273809s [ * ]
20:26:34, d:+00.0012632s o:+00.0364975s [ * ]
20:26:36, d:+00.0017833s o:+00.0286893s [ * ]
20:26:38, d:+00.0019420s o:+00.0312782s [ * ]
20:26:40, d:+00.0012876s o:+00.0389575s [ * ]
20:26:42, d:+00.0012943s o:+00.0322041s [ * ]
20:26:44, d:+00.0020414s o:+00.0316223s [ * ]