Windows 2008 R2 - NTP server settings

restart the time service and see if it updates the source

net stop w32time && net start w32time

same thing.

Try the run the code below in elevated command prompt.

w32tm /config /syncfromflags:manual /manualpeerlist:"0.ca.pool.ntp.org 1.ca.pool.ntp.org 2.ca.pool.ntp.org 3.ca.pool.ntp.org"

Select allOpen in new window

http://www.pool.ntp.org/zone/ca

http://www.pool.ntp.org/en/use.html

Hmmm ... W32time, the timekeeping service in Windows. I experienced enough trouble with that piece of crap when in NTP mode to avoid using it whenever I can.

For a mature timekeeping service with well documented behaviour, I'd recommend this:

Use a Windows port of the classic *ix NTP service on your DC VMs, and sync 'em with NTP time sources from pool.ntp.org. Ensure to disable the time sync features of VMware (to timekeeping services on one clock will cause time chaos). The NTP service software is free. Easy to install and configure, works like a charm and is stable as a rock. And it is nicer when it comes to one of the rare cases of troubleshooting.

See my article on NTP basics for the "How To".

The NTP service has a low ressource footprint, therefore the NTP functionality could be hooked onto existing machines or VM's like webservers, ftp servers, mailservers or database hosts - even in a DMZ - without visible performance impact.

If securtity is an issue, you might as well use local radio controlled clock appliances (see the article for that, too) in your LAN who serve times very reliable and precise.

By the way, I'd recommend to configure your NTP client to more than one server ... in the case you want to use the ca segment of pool.ntp.org, you should use

server 0.ca.pool.ntp.org iburst
server 1.ca.pool.ntp.org iburst
server 2.ca.pool.ntp.org iburst
server 3.ca.pool.ntp.org iburst

Select allOpen in new window

in your ntp.conf file for enhanced redundancy and stability.

Great answer! Worked like a charm!