I am running a newly migrated DC on a EXSi 5.5.0 vsphere box. And for the life of me i cannot get it to sync with an outside time source.
By default any VM built on VMWare or Hyper-V will sync time with Host. So there are chances that even if we sync time with external sources, Host time sync will take precedence. Time.synchronize.tools.enable = “0”. Useful Registry values for NTP server settings. Key to find the poll interval with external sources. Path: HKEY_LOCAL.
I opened my firewall to allow traffic on 123 TCP UDP(pool servers respond to my pings). I have configured the required Registry Keys as noted.
I have run net stop w32time && net start w32time and w32tm /resync /rediscover with no changes. I am not sure what i am missing. Everything seems to point to the new time source however DC keeps using its CMOS Clock.
Any assistance would be appreciated. Output from: w32tm /query /status C: Users.w32tm /query /status Leap Indicator: 0(no warning) Stratum: 1 (primary reference - syncd by radio clock) Precision: -6 (15.625ms per tick) Root Delay: 0.0000000s Root Dispersion: s ReferenceId: 0x4C4F434C (source name: 'LOCL') Last Successful Sync Time: 1/19/2016 11:11:58 AM Source: Local CMOS Clock Poll Interval: 6 (64s). Looks like some a few machines are that have authenticated through my DC2 are still pulling a incorrect time. When i run /status on those devices they are pointing to my dc2 for time. My DC2 is getting its time from DC1 (fSMO DC).
Poll interval is 1024Seconds. Not really sure how they are off since everything ends up pointing to DC1.
Also I seem to be locked out of my Terminal server. It is probably on the old time and wont let me authenticate because of the time difference.
Should i just wait it out? Looks like everything is resolving it's self. JordonLovik wrote: looks like some a few machines are that have authenticated through my DC2 are still pulling a incorrect time. When i run /status on those devices they are pointing to my dc2 for time. My DC2 is getting its time from DC1 (fSMO DC).
![]()
Poll interval is 1024Seconds. Not really sure how they are off since everything ends up pointing to DC1. Also I seem to be locked out of my Terminal server. It is probably on the old time and wont let me authenticate because of the time difference. Should i just wait it out? Looks like everything is resolving it's self. Everything should slowly update itself.
Anything that you need right away a reboot should force the clock to sync.
Completely Disable Time Synchronization for your VM posted January 6, 2016 Some administrative practices, like a bad habit, have more lives than the proverbial cat – they tend to stay around forever. It is, therefore, very comforting when one finds a problematic administrative practice that has not just been universally abandoned by administrators, but is also on the top of any junior administrator’s “configurations sure to get you dis-invited from the next user group meetup” list.
Take the case of the old practice of synchronizing a virtual machine’s clock with its host’s clock in a vSphere environment. That used to be “the thing to do” way back when. It was actually the default configuration option on the ESX platform in those days.
Until everyone got wiser and the message went out to every admin far and wide that such configurations was no longer kosher. Even VMware got religious and stopped making that option the default behavior. Now, if you are like one of the hundreds of vSphere administrators with whom I have interacted over the past years, you are probably unaware of the fact that, even when the “Synchronize clock with ESXi host” option is disabled (unchecked) on the VMware Tools properties of the virtual machine, the virtual machine will still occasionally synchronize its clock with the ESXi host.
Oh, you knew that? Show-off 🙂 You probably did because VMware actually documented the behavior in a rather oft-overlooked knowledge base article – As mentioned in that KB, the following vSphere operations can cause the clock on a virtual machine to be reset (backward or forward) to match the clock on the host on which it resides.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |