While the w32tm /resync
in theory does the job, it only does so under certain conditions. When "down to the millisecond" matters, however, I found that Windows wouldn't actually make the adjustment; as if "oh, I'm off by 2.5 seconds, close enough bro, nothing to see or do here".
In order to truly force the resync (Windows 7):
- Control Panel -> Date and Time
- "Change date and time..." (requires Admin privileges)
- Add or Subtract a few minutes (I used -5 minutes)
- Run "cmd.exe" as administrator
w32tm /resync
- Visually check that the seconds in the "Date and Time" control panel are ticking at the same time as your authoritative clock(s). (I used
watch -n 0.1 date
on a Linux machine on the network that I had SSH'd over into)
--- Rapid Method ---
- Run "cmd.exe" as administrator
net start w32time
(Time Service must be running)
time 8
(where 8 may be replaced by any 'hour' value, presumably 0-23)
w32tm /resync
- Jump to 3, as needed.