In the past few weeks we have had problems with the fact that Hyper-V servers do not get the correct time from the Active Directory domain controller and so the time sometimes deviates by up to 10 minutes. Of course, this should not be so, because usually the virtual machines (VMs) get the time from the Windows Hyper-V host on which they are running.
In order for the entire network to work correctly, the times of the servers and especially the domain controller should always be the same. Even small deviations can have negative effects on certain functions in the network.
To determine which time source the Windows server has entered, use the following command:
w32tm / query / source
If this is not correct, the correct timer can be entered with the following command:
w32tm / config /manualpeerlist:”servername.domain. ?? “/ syncfromflags: manual / update
An external timer or an internal timer can of course be stored here. This must be adjusted depending on the use.
After you issue the adjustment command, it will take a while until the time has really updated. You can check this with the command, for example
w32tm / monitor
The command “w32tm” has countless other parameters , which we cannot go into here. If you know any other useful commands related to the Windows timer, then we would be happy to receive a comment at the end of this article.
Conclusion: As I said, you should absolutely make sure that the times of the domain controllers are the same. As a rule, this should be checked by every IT department at regular intervals.
You can find further information on the subject of “times” under Windows here:
– Remove the time and date from the Windows 10 taskbar
– Activate the time with the seconds display in the Windows 10 taskbar
– Change Windows date and time using PowerShell
– Remove the date and time display from the Windows task bar using GPO
– Change the Windows timer (time) on a Windows server
