I noticed tonight that my domain controller’s clock had creeped ahead by about 15 minutes. Inconsistent time, especially time that differs between servers, clients, and a domain controller can throw applications like Exchange, who depend upon Active Directory for information, for a loop.
In Windows 2008 R2 (and Windows 7), the /setsntp and /querysntp switches of NET TIME are deprecated. W32TM.exe provides similar functionality that NET TIME provided when it came to configuring domain controllers as a primary time source.
W32TM is not terribly intuitive, but I did get enough information to get my Windows 2008 R2 domain controller updated and again updating the time of the resources in my domain.
If you are wondering how to set this up – here are a few steps to help you out.
1. Use W32TM to configure the peer list and then update the configuration. In this case, I am using a “set” of public servers to get my time information. From a command prompt, type (on a single line):
w32tm /config /manualpeerlist:”server 0.north-america.pool.ntp.org”,0×8 /syncfromflags:MANUAL /reliable:yes /update
2. I’m not entirely sure that this is required, but we’ll restart the Windows Time Service for good measure. From a command prompt, type:
net stop w32time
then restart the service:
net start w32time
3. Then we’ll initiate the time resynchronization and rediscovery of the peer list time sources that we specified in Step #1. From a command prompt, type:
w32tm /resync /rediscover
There. You should be all set. If you want to update the time on a client (or a server) ahead of the regular interval at which is checks with a domain controller for the correct time, you can go to a command prompt and type:
net time /domain<domain name> /set /yes
This will force an update of the time on the current system from your local domain.