W32 Time problems on a virtual domain controller. Changing itself to CMOS source or other.
Posted on 2016-10-24
We are having network time issues on one of our Domain Controllers. The server is running 2012 R2 on a virtual machine. We have the server set to pick up time from a range of four sources –
What we are finding is that after a reboot (does not appear to happen after every reboot), the server is either:
1) Taking the time from the CMOS (and rapidly drifting by up to 5 minutes).
This is proven by the command w32tm /query /status
2) At other times, a short time after reboot, the server is failing to obtain the time from one of our four sources (uk.pool.ntp.org), despite the w32tm /query /status showing the current four valid sources after a reboot.
When the machine is in this state, it appears to take over an hour to actually drift out and then propagate the wrong time to the network machines.
The domain controller is correctly announcing itself as a valid time source and other machines in the domain are taking their time from this server.
We are not pulling down the time from the host machine, we have unticked the Time Synchronization option a number of months ago.
The issue does not happen on every reboot but appears to be happening more regularly.
This morning we have set the time to be taken from our other domain controller, which is a physical box.
Would appreciate any comments on why you think the time settings are deviating from our settings or failing after a time.