We have a previous post on setting up the Windows Time service here:
To date we have had decent success on reigning in a heavily loaded VM’s tendency to skew its time.
What we have come with via a number of sites listed below and a lot of reading in online forums follows.
- Hyper-V Integration Services: Time Synchronization remains enabled.
- Yes, even on DCs.
- Registry edit to allow the VM to pick up its time from the Hyper-V host only while booting:
- reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider /v Enabled /t reg_dword /d 0
- Copy and paste the above into Notepad to make sure there are no line breaks as it is all in one line.
- Edit the Windows Time registry settings to make the time service poll more frequently:
- w32tm /config /syncfromflags:manual "/manualpeerlist:0.ca.pool.ntp.org,0x1 1.ca.pool.ntp.org,0x1 2.ca.pool.ntp.org,0x1 3.ca.pool.ntp.org,0x1" /reliable:yes
- Note the quotes enclosing the time server names.
- MSDN Blogs: Ryan Sizemore: Configuring the Time Service: NtpServer and SpecialPollInterval
- Jaylee.org: Hyper-V, CPU Load and System Clock Drift
- Virtual PC Guy’s Blog: Time Synchronization in Hyper-V
- Yahoo Groups: SBS2K: SBS Time
- Great contributions by Chris Knight to this thread.
NOTE: This post may be updated at any time to reflect changes to the above methodology. Please keep in mind that this is a work in progress.
UPDATED 2012-03-06: Tweaked the registry settings as per comments below and the setting found in the MSDN article linked above.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book