Time synchronization (NTP, SNTP) setup

article #37, updated 780 days ago

In Windows Server 2012 R1/2, 2008 R1/2, 7, Vista, and 2003 SP2 and later, whenever time is out of sync, it’s good to run the following two commands in an administrative command prompt (an ordinary command prompt for 2003SP2+):

w32tm /config /manualpeerlist:pool.ntp.org,0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org /syncfromflags:MANUAL /reliable:YES /update
w32tm /resync /rediscover

/rediscover is something new to this writer, it solves problems when /resync alone does not produce correct results.

In Server 2003 SP1 and before, and XP, we use this, because /reliable doesn’t exist:

w32tm /config /manualpeerlist:pool.ntp.org,0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org /syncfromflags:MANUAL /update
w32tm /resync

Sometimes w32tm doesn’t exist as a service, and has to be registered:

w32tm /register

Under Windows 2000, we need to go a bit more archaic:

net time /setsntp:pool.ntp.org
net time /querysntp

If you are using Windows DHCP services, the above is best for the server, but for all of the workstations under its control, place the server’s IP in the Time Server option. This is probably best for a domain. When you have standalone or mobile-capable machines, best to just use the w32tm configuration above.