This Question is mostly for other people to learn from and to satisfy my own curiosity if someone knows why it does the following.
We had a problem with our DC not having the right time due to it being virtualized, that has since been fixed. But some of our clients and servers needed the updated time. So I tried running the following commands as admin w32tm /query /source to make sure it was getting the time from our Domain Controller then w32tm /resync to sync the time, both commands had no errors but the time didn’t change.
I see something similar to the following line in the event logs. The system time has changed to 2014-09-08T21:31:33.328000000Z from 2014-09-08T21:31:33.342455400Z.
So I try the command a few more times with no change and go search around on Google for a bit, only to come back and find the client has the right time now, but nothing new in the event logs.
I tried on a second client with the same result but I didn’t leave the client but poked around the logs a bit and out of pure luck I looked down at the clock and noticed that time was getting closer to the real time. It was slowing drifting back to the right time. Every now and then the clock would go up by 2 seconds, or a second would change to the next digit before a whole second had gone by. It would do this until the clock had reached the right time.
My question is why does it do this? why not just change the time to the correct time instantly like my personal computer does when I sync the time to an NTP server?