Server 2016 ntp not updating Sexy girl of new york web chat
You should not need to disable Hyper-V time synchronization in order to use a different time synchronization source – as long as it goes through the Windows time synchronization infrastructure.
In fact – if you are running a Domain Controller inside a virtual machine I would recommend that you leave Hyper-V time synchronization enabled but that you also setup an external time source.
So while this would solve the problem for our Linux running user base – the fact of the matter is that most of our users run Windows – and this would not work for them.
Hyper-V time synchronization was designed to “get along well” with other time synchronization sources.
Interestingly enough, at this point in time we will be reporting the correct (with some caveats) time in the systems RTC.
When we restore a virtual machines from a saved state or from a snapshot we put back together the memory and run state of the guest operating system to exactly match what it was when the saved state / snapshot was taken.
This includes the time calculated by the guest operating system.
UTC (which is the computer techy version of saying GMT) time would solve this problem nicely with only one problem.
Windows does not support UTC time in the BIOS (Linux does).