@JaredBusch said in Domain Time off for some members: @Donahue said in Domain Time off for some members: found it. It was the individual time for that ESXi member. It was running on it's own time, neither host time or any NTP. It was off by the 6 minutes. So for some reason, VMWare was syncing this setting with the host's ESXi clock, not the hardware clock, even though the settings disallow that. How do you know the VMware tools was doing the sync?. As I said in my earlier post if windows goes and tries to get the hardware clock no matter what your tool says for heartbeat or times are pretty station it’s going to get the Clock from the host. look at the picture I posted above. It was vmtoolsd.exe that was causing it to jump forward and svchost.exe that was correcting it. I found this under event 4616

I would prefer the phones to go out to 0.us.pool.ntp.org and 1.us.pool.ntp.org for all of their time sync issues but they appear to be having some issue. Of which I am unable to determine what that could be with the error provided.

@ccwtech said in Computers not syncing with Domain Controller. Is my GPO blocking it?: @dbeato said in Computers not syncing with Domain Controller. Is my GPO blocking it?: @ccwtech said in Computers not syncing with Domain Controller. Is my GPO blocking it?: @dbeato said in Computers not syncing with Domain Controller. Is my GPO blocking it?: @ccwtech said in Computers not syncing with Domain Controller. Is my GPO blocking it?: Computers in a domain are not syncing time with the Domain Controller (Hyper-V). They are all set to the local CMOS clock. I had to restrict the ability for local users to change time by themselves. Is the GP that I created preventing the computers from syncing to the domain? The time can be in different zones and not affect connectivity to the domain as long as it is 5 minutes from the DC time via UTC. Now I would really make the computers to just point to the DC as their NTP Server instead of anything else. I thought they did by default in a domain. They should but it is not enforced. What do I need to do to enforce it? Or point them to the DC to use? @ccwtech said in Computers not syncing with Domain Controller. Is my GPO blocking it?: @dbeato said in Computers not syncing with Domain Controller. Is my GPO blocking it?: @ccwtech said in Computers not syncing with Domain Controller. Is my GPO blocking it?: @dbeato said in Computers not syncing with Domain Controller. Is my GPO blocking it?: @ccwtech said in Computers not syncing with Domain Controller. Is my GPO blocking it?: Computers in a domain are not syncing time with the Domain Controller (Hyper-V). They are all set to the local CMOS clock. I had to restrict the ability for local users to change time by themselves. Is the GP that I created preventing the computers from syncing to the domain? The time can be in different zones and not affect connectivity to the domain as long as it is 5 minutes from the DC time via UTC. Now I would really make the computers to just point to the DC as their NTP Server instead of anything else. I thought they did by default in a domain. They should but it is not enforced. What do I need to do to enforce it? Or point them to the DC to use? Enforce the time source on the DC https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/ For clients look at this one https://www.altaro.com/hyper-v/configuring-time-synchronization-for-all-computers-in-windows-domain/

@jt1001001 said in Unable to get time to sync on Server 2012 R2 DC: are any of your time services running under a domain accoutn instead of Local Service? Sounds like a service does not have permission to update the time Windows Time is set to run under "Local Service" (not local system account)

The question that I have is... why did people used to choose to work when it was dark... and then happily work in the light when DST was introduced? What insane set of circumstances made everyone do something seen as a bad idea one moment but happily just "fix it" the next and then spend half of the year going back to the poor way again for no reason? There are so many flaws with the DST theory.