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

    Domain Computers: Clock Sync

    IT Discussion
    ntp clock domain server 2012
    7
    11
    806
    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.
    • gjacobse
      gjacobse last edited by

      I'm getting a few reports from one of our clients that they desktop are showing incorrect clock times even though they are set by the Primary DC.

      the DC is set to pull time from a known good NTP server.

      Even after rebooting, the clocks are incorrect.

      Any thoughts as to why this could be?

      1 Reply Last reply Reply Quote 0
      • JaredBusch
        JaredBusch last edited by

        You never stated if the DC was actually correct.

        1 Reply Last reply Reply Quote 2
        • gjacobse
          gjacobse last edited by

          When I checked it the other day - it was, but oddly - today it is 6 minutes fast.

          re-setting all the NTP servers

          S 1 Reply Last reply Reply Quote 0
          • travisdh1
            travisdh1 last edited by

            It's the default client sync still only once per week? I'd they're all different but close, it could be the local clocks going bad (bios batteries starting to go possibly).

            1 Reply Last reply Reply Quote 0
            • S
              StorageNinja Vendor @gjacobse last edited by

              @gjacobse Is it Virtual? If so what hypervisor? (Different best practices)

              gjacobse 1 Reply Last reply Reply Quote 2
              • gjacobse
                gjacobse @StorageNinja last edited by

                @storageninja said in Domain Computers: Clock Sync:

                @gjacobse Is it Virtual? If so what hypervisor? (Different best practices)

                Good point - I can sync the VM all day long, but the the HyperVisor is off,.. nothing will change.

                Updated the HV, and now the VM seem correct.

                stacksofplates 1 Reply Last reply Reply Quote 1
                • stacksofplates
                  stacksofplates @gjacobse last edited by

                  @gjacobse said in Domain Computers: Clock Sync:

                  @storageninja said in Domain Computers: Clock Sync:

                  @gjacobse Is it Virtual? If so what hypervisor? (Different best practices)

                  Good point - I can sync the VM all day long, but the the HyperVisor is off,.. nothing will change.

                  Updated the HV, and now the VM seem correct.

                  I'm sorry, what does this mean?

                  Especially this statement "but the the HyperVisor is off,.. nothing will change". Not being a jerk, I honestly couldn't follow it.

                  Kelly 1 Reply Last reply Reply Quote 0
                  • gjacobse
                    gjacobse last edited by gjacobse

                    DC4 is a virtual machine. changes to it are likely over rode by the Hypervisor or physical hardware that were wrong.

                    By updating the physical hardware, and then running w32tm /resync the time updated.

                    dbeato 1 Reply Last reply Reply Quote 1
                    • Kelly
                      Kelly @stacksofplates last edited by

                      @stacksofplates said in Domain Computers: Clock Sync:

                      @gjacobse said in Domain Computers: Clock Sync:

                      @storageninja said in Domain Computers: Clock Sync:

                      @gjacobse Is it Virtual? If so what hypervisor? (Different best practices)

                      Good point - I can sync the VM all day long, but the the HyperVisor is off,.. nothing will change.

                      Updated the HV, and now the VM seem correct.

                      I'm sorry, what does this mean?

                      Especially this statement "but the the HyperVisor is off,.. nothing will change". Not being a jerk, I honestly couldn't follow it.

                      At least Hyper-V has the clients pull time from the host by default. It doesn't matter what the settings are in the OS, it is a hypervisor setting that has to be turned off before your w32tm settings will do a thing.

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        StorageNinja Vendor @Kelly last edited by StorageNinja

                        @kelly said in Domain Computers: Clock Sync:

                        At least Hyper-V has the clients pull time from the host by default. It doesn't matter what the settings are in the OS, it is a hypervisor setting that has to be turned off before your w32tm settings will do a thing.

                        VMware VMtools will also pull time from the host. From this, you should..

                        1. Check the Host BIOS Time (UTC)
                        2. Set the Host BIOS to draw from NTP (iDRAC/iLO)
                        3. Set ESXi (If also used) to use NTP also (Service off by default).

                        Note there are a lot of free NTP clocks to poll from.
                        time.windows.com is generally up.

                        If you are running ESXi there is a built-in health check (under vSAN health Checks) that will alert you to time drift between any hosts and the vCenter to identify this.

                        1 Reply Last reply Reply Quote 2
                        • dbeato
                          dbeato @gjacobse last edited by dbeato

                          @gjacobse said in Domain Computers: Clock Sync:

                          DC4 is a virtual machine. changes to it are likely over rode by the Hypervisor or physical hardware that were wrong.

                          By updating the physical hardware, and then running w32tm /resync the time updated.

                          The issue will resurface again as the BIOS is losing time and will be pulled again wrongly on the host. Have you tried not syncing the time of the VM through the Hypervisor and turning of Time Synchronization for this DC?

                          1 Reply Last reply Reply Quote 2
                          • First post
                            Last post