ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Domain Time off for some members

    Scheduled Pinned Locked Moved IT Discussion
    server 2012 r2windowstimentpdomainvmware
    46 Posts 8 Posters 4.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DonahueD
      Donahue
      last edited by

      does anyone know a better tool that I can use to find out what is triggering this to happen?

      1 Reply Last reply Reply Quote 0
      • DonahueD
        Donahue
        last edited by Donahue

        I think I may have found the cause. I looked into event 4616 under the security log. I can see a consistent pattern of three records repeating over and over again. The first thing is that VMWare tools was setting the clock ahead 6 minutes. Then a little later, svchost was setting it back, and then resetting it again. Then a little later VMWare tools would set it ahead again and the pattern repeats.
        time sync cause.PNG

        1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller
          last edited by

          Ah yes, competing time sources.

          1 Reply Last reply Reply Quote 0
          • DonahueD
            Donahue
            last edited by

            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.

            DashrenderD JaredBuschJ 2 Replies Last reply Reply Quote 0
            • notverypunnyN
              notverypunny
              last edited by

              If your hardware supports it (Dell PE gear with IDRAC for instance) you could have it syncing with an NTP source as well.

              1 Reply Last reply Reply Quote 0
              • DashrenderD
                Dashrender @Donahue
                last edited by

                @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.

                Any mention of a bug in VMWare tools about this?

                dbeatoD 1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch @Donahue
                  last edited by

                  @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.

                  DashrenderD DonahueD 2 Replies Last reply Reply Quote 0
                  • dbeatoD
                    dbeato @Dashrender
                    last edited by

                    @Dashrender 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.

                    Any mention of a bug in VMWare tools about this?

                    Not much https://kb.vmware.com/s/article/1318?srcvmw_so_vex_pgrev_242=

                    1 Reply Last reply Reply Quote 0
                    • DashrenderD
                      Dashrender @JaredBusch
                      last edited by

                      @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.

                      I didn't think Windows ever did that in a domain environment? I thought it always got it from the PDC emulator.....

                      dbeatoD 1 Reply Last reply Reply Quote 0
                      • dbeatoD
                        dbeato @Dashrender
                        last edited by

                        @Dashrender said in Domain Time off for some members:

                        @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.

                        I didn't think Windows ever did that in a domain environment? I thought it always got it from the PDC emulator.....

                        In a VM it does get overwritten a lot by the hypervisor Host Clock.

                        DashrenderD 1 Reply Last reply Reply Quote 0
                        • DashrenderD
                          Dashrender @dbeato
                          last edited by

                          @dbeato said in Domain Time off for some members:

                          @Dashrender said in Domain Time off for some members:

                          @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.

                          I didn't think Windows ever did that in a domain environment? I thought it always got it from the PDC emulator.....

                          In a VM it does get overwritten a lot by the hypervisor Host Clock.

                          Why would that be? I ask this especially in the case where the integration software has been specifically set to disable time syncing with the host.

                          dbeatoD 1 Reply Last reply Reply Quote 0
                          • dbeatoD
                            dbeato @Dashrender
                            last edited by

                            @Dashrender said in Domain Time off for some members:

                            k this especially in the case where the integration software has been specifically set to disable time syncing with the host.

                            https://blogs.msdn.microsoft.com/virtual_pc_guy/2010/11/19/time-synchronization-in-hyper-v/

                            1 Reply Last reply Reply Quote 0
                            • DonahueD
                              Donahue @JaredBusch
                              last edited by

                              @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

                              1 Reply Last reply Reply Quote 0
                              • 1
                              • 2
                              • 3
                              • 3 / 3
                              • First post
                                Last post