Thanks in advance for helping me find the right forum for the following question.
For testing purposes, I sometimes have to change the date/time on a Windows Server 2012 R2 virtual machine (VMWare) that is on our domain. To ensure that the time does not resync with the domain controller, I turn off the w32time service. However, sometimes
I return to the server to find that it has resynced with the domain controller. Below is the most recent example.
I set the server's time to 5 days in the future. It stayed "in the future" for 5 days. Then, early this morning, the w32time service started, synced, and stopped. I'm having trouble finding the cause. Below are the event logs I see.
The WinHTTP Web Proxy Auto-Discovery Service service entered the running state.
The Windows Error Reporting Service service entered the running state.
The Windows Time service entered the running state.
The time provider NtpClient is currently receiving valid time data from dc.domain.local (ntp.d|0.0.0.0:123->192.168.100.11:123).
The system time has changed to 2016-11-28T07:23:36.098146100Z from 2016-12-03T07:22:30.984984500Z.
Change Reason: An application or system component changed the time.
The time service has set the time with offset 431934 seconds.
The time service is now synchronizing the system time with the time source dc.domain.local (ntp.d|0.0.0.0:123->192.168.100.11:123).
The system time has changed to 2016-11-28T07:23:36.112000000Z from 2016-11-28T07:23:36.120351400Z.
Change Reason: An application or system component changed the time.
The system time has changed to 2016-11-28T07:23:36.111000000Z from 2016-11-28T07:23:36.112822700Z.
Change Reason: An application or system component changed the time.
The Windows Time service entered the stopped state.
The Windows Error Reporting Service service entered the stopped state.
The WinHTTP Web Proxy Auto-Discovery Service service entered the stopped state.
