We have 2 physical hyper-V servers running 8 VMs between them, each physical server has a Domain controller on it running in a VM and all servers are 2008R2
The VM PDC is set to NTP and to sync with time.microsoft.com and the rest including the physical servers are NT5DS. This Main VM PDC definately holds the FSMO and is UDP 123 is active
when i run w32tm /query /status
Im getting VM IC Time Synchronization Provider on both VM DCs, i know this means syncing with the host.
When i run w32tm /resync /rediscover
I got "did not resync because no time data was available " and an event ID 134 in the logs any ideas on that?
I also looked through the logs and have got event 144 & 12
I have followed MS KB details on setting up an external time source and made all registry changes but i think the DNS is getting me?
But when i change the time on one of the physical machines this is where the time is being set from. Maybe if i unregister them all and register and update and sync but im afraid il create a bigger problem!
I am trying to leave time sync between the VM and Hyper-V Host enabled as i believe this to be best practice from what i have read.
Thanks for your help
I have finally got it working! The goal of this is to help people out who are starting at the beginning of setting a Domains time.
In this example all Servers, Primary Domain Controller (PDC), other Domain Controllers (DC) and other servers are running Windows 2008 R2 and are virtualised with Hyper-V.
First things first you will read to disable the 'Time Synchronization Integration Service' on any virtual machine within Hyper-V but instead you should manipulate the Windows Time Service (w32tm service) from within the virtual DC, you should not disable this because when a VM restarts this will cause problems, it should be done with w32tm. http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/11/19/time-synchronization-in-hyper-v.aspx
You will need to find out what server is the PDC and running FSMO roles. Run this: netdom query fsmo The result should be your PDC and this is where you make most of your changes.
Make sure in the firewall there is an “Outbound” rule on UDP123 and the program is %SystemRoot%\System32\w32tm.exe just browse to windows directory and find the exe for time
This is where the registry changes go down! HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time
Make sure the PDC under config in the above registry address is set to NTP for “type“and all other servers are NT5DS, this means NTP is the daddy! Best practise here is to have the PDC look externally for time and everything sync to it.
Run this on all domain controllers (including PDC), it will partially disable windows time so it does not look at the host machine for time, important because we are virtualised. reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider /v Enabled /t reg_dword /d 0
You can go to the ntp.org http://support.ntp.org/bin/view/Servers/WebHome site to find a server closest to you to sync your external time. I recommend not using Microsoft as they are heavily used and can slip out because of this.
Below command will set the PDC to look externally but also check the registry settings as defined here to sync externally (you need to do both) http://support.microsoft.com/kb/816042
Run this on PDC w32tm /config /manualpeerlist:“0.pool.ntp.org,0x1” /syncfromflags:MANUAL /reliable:yes w32tm /config /update w32tm /resync w32tm /resync /rediscover
Run these 2 commands at any time on any server to see their source and when they last updated, these will be used throughout this exercise to make sure your PDC and other servers are getting time from the right place w32tm /query /status w32tm /query /source
Then run this on all DC except the PDC, it will make them look at the PDC for time and resync to it w32tm /config /syncfromflags:DOMHIER /update net stop w32time net start w32time w32tm /resync /force
Issues: When you run the Status or Source query give them a minute or 2 after changes, you should not be looking at the Local CMOS Clock and you should not be using vm ic time synchronization provider as source either.
If successful the PDC should read the external site you have set and the other servers should say the PDC as source
Hope this helps people good luck!