So why do we want to turn off the time sync in HyperV?

Because you want your domain controller to be the time sync, not the HyperV.


In SMB chances are that HyperV host is a workgroup, not a domain controller.  Only a domain controller should be the primary time keeper in a SMB firm.  So if you have a workgroup HyperV host that is not a DC and thus not advertising as the big kahuna of time for the domain, you therefore don’t want to keep that time sync box checked in HyperV.


You want the DC to be the time keeper.



Remember you can only be + or – 5 minutes off between workstations and the DC to connect to each other.  Thus it’s very key to have the DC be “THE CLOCK” for the domain.

3 Thoughts on “So why do we want to turn off the time sync in HyperV?

  1. Thanks :-)

  2. How do you turn off the time sync?

  3. Ben Armstrong (Virtual PC Guy) recommends to leave time sync enabled so that the Virtual Machine gets the right time set on startup, but then disable the VM Integration Components time provider inside the VM. This then allows the VM to be configured to use an external time source but with the added bonus of having the VM seeded with an accurate time prior to the initial sync with the external time source – critical for getting that first sync with the external time source working.

    http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/11/19/time-synchronization-in-hyper-v.aspx

    Your argument only makes sense if you don’t change default settings for W32Time on any of your servers. You want whatever device that is capable of tracking time accurately to be your authoritative time source, not some VM with a random sense of time that then spews this randomness throughout the network.

Post Navigation