Network and server time will not stay set in a Hyper V virtual environment does anyone know what I am missing here?
I am having an ongoing issue with Network and server time continuously getting skewed and causing massive issues across the network. this is a newly deployed Hyper V virtual environment on a host server running Server 2008 R2 Datacenter.
We have statically set the Primary Domain Controller to get time from the national time institute, and all other servers and workstations on the network are configured to pull time from the PDC by either registry setting (servers) or by means of a login script (workstations).
some days everything is fine others, time gets skewed normally by about 13-15 minutes, however; today after having to put out several fires regarding authentication issues, email acess issues and even 1 workstation that would not allow the user to log in, I found the host server to be off by a time interval of almost 40 minutes.
I am at my wits end with all of this as nothing I have set or done seems to resolve the issue permanently.
We have statically set the Primary Domain Controller to get time from the national time institute, and all other servers and workstations on the network are configured to pull time from the PDC by either registry setting (servers) or by means of a login script (workstations).
some days everything is fine others, time gets skewed normally by about 13-15 minutes, however; today after having to put out several fires regarding authentication issues, email acess issues and even 1 workstation that would not allow the user to log in, I found the host server to be off by a time interval of almost 40 minutes.
I am at my wits end with all of this as nothing I have set or done seems to resolve the issue permanently.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Darius Ghassem
Go to the properties of VM in the settings disable time sync with Host.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
sorry for the delayed response I went in and set the host to acquire time from the samp NTP server as the PDC, and all was well till this morning when again the host time went off by 15 mminutes.
Would it be adviseable to DC promo the host server and make it the new PDC emulator?
Would it be adviseable to DC promo the host server and make it the new PDC emulator?
Do you have any other software running on your VM Host? I've seen some buggy software cause heavy time drift in the past.
The VM shouldn't be getting timem the Host uncheck this
ASKER
I have unchecked the time setting for all the VMs on the host server. I need to keep track of this over the next few days to make sure that addresses the issue, but hopefully thanks to both of your suggestions we may have the issue resolved.
I just need a couple days to see that there are no further issues arising and I will split the points :)
I just need a couple days to see that there are no further issues arising and I will split the points :)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks for all the hep our time issues have been resolved annd we have had no issues for over a week now!
Are any of your DCs on physical boxes? If they are then set them up to pull time from pool.ntp.org. Then set up your hosts and guests to pull from that DC. Allow firewall exceptions for NTP inbound on that DC.
If all DCs are VMs then set up one of the physical hosts to poll pool.ntp.org for time and then set the VMs to poll the host. Again set the firewall accordingly.
http://blog.mpecsinc.ca/2011/01/hyper-v-preparing-high-load-vm-for-time.html
We have had a lot of pain over the time skew situation for VMs.
The above methods work for us. In some cases we drop in an HP MicroServer with Win2K8 R2 running as a DC and set it up to poll pool.ntp.org and then have all VMs poll it for time.
The problem has to do with the polling frequency needed as indicated in the blog post. Do that to ntp.org's servers and they will pass along the Kiss-Of-Death packets basically killing the ability to poll their servers for time.
If all DCs are VMs then set up one of the physical hosts to poll pool.ntp.org for time and then set the VMs to poll the host. Again set the firewall accordingly.
http://blog.mpecsinc.ca/2011/01/hyper-v-preparing-high-load-vm-for-time.html
We have had a lot of pain over the time skew situation for VMs.
The above methods work for us. In some cases we drop in an HP MicroServer with Win2K8 R2 running as a DC and set it up to poll pool.ntp.org and then have all VMs poll it for time.
The problem has to do with the polling frequency needed as indicated in the blog post. Do that to ntp.org's servers and they will pass along the Kiss-Of-Death packets basically killing the ability to poll their servers for time.