Have you noticed that Windows Server clock is not synchronized with external source?
I had a case when customer called me that their clock is 5 minutes late.
Server 2003 was not configured to sync with external NTP source. Difference with internal clock and external clock was 5 minutes. Not cool. Possibly that System time was not updating with domain.
At first I thought that customer’s clock was not accurate, but when I checked time on my watch, I knew there was some thing wrong. Usually the clock on the client is synchronized with domain.
Here is the procedure that I have used to solve the problem and Synchronize NTP server to external source
Active directory domain is providing time to it’s clients. That’s why it’s really important to have AD domain synchronized with a reliable source. There is a reliable NTP project called NTP Pool. Project has over 3900 NTP servers spread around the world in Africa, Asia, Europe, North America, Oceania and South America. You can easily find the closest mirror to you, in most cases in the same country.
I have tested this solution on a Windows server 2003 SP2, 2008, 2008R2 and confirm that it works. To implement it, you only need around 5 minutes.
First you need to discover which server is domain authoritative.
This is important because the other DC sync from that one.
To find authoritative server type:
netdom query fsmo
you will get the name of the server which is authoritative. Connect to that server
To find out time difference between external source and your domain type:
w32tm /stripchart /computer:us.pool.ntp.org /samples:5 /dataonly
you will get difference in time between your DC and external NTP server. Output will look something like this:
Tracking us.pool.ntp.org [126.96.36.199].
Collecting 5 samples.
The current time is 15.1.2013 14:15:41 (local time).
w32tm /config /manualpeerlist:us.pool.ntp.org,0×8, /syncfromflags:manual /update
This command will configure your DC to use external NTP server for source.
w32tm /resync /nowait
this will resync immediately with external NTP server.
Once this is done you can resync computer with your DC
w32tm /resync /nowait /computer:computername
To confirm that time is synchronized type: w32tm /stripchart /computer:us.pool.ntp.org /samples:5 /dataonly
you will receive output similar to this one:
Tracking us.pool.ntp.org [188.8.131.52].
Collecting 5 samples.
The current time is 15.1.2013 14:20:51 (local time).
Hopefully this will save you some time
How Windows time service works – Link to MS Technet