There is time sync issue in couple of server's. Below is the Description
There are two identical server's with same OS and same set of software's running. And they are pretty new server's.In every 30 Min or so OS time gets changed to some random time. There is no chance of CMOS battery going bad. As these are new we even replaced the motherboard.
I ran the W32tm /query /status
command in two of the server's and below is what i see.
Source in two server differ and also Stratum: 1 (primary reference - syncd by radio clock) and ReferenceId: 0x4C4F434C (source name: "LOCL").
How do i get the Problematic server running with correct time.
Server with No Problem: Server:1
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: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 8/9/2016 8:49:46 AM
Source: Local CMOS
Clock Poll Interval: 10 (1024s)
Server with Problem: Server:2
Leap Indicator: 3(last minute has 61 seconds)
Stratum: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s Root
Dispersion: 0.0000000s
ReferenceId: 0x00000000 (unspecified)
Last Successful Sync Time: unspecified
Source: Free-running
System Clock Poll Interval: 10 (1024s)
w32tm /config /syncfromflags:DOMHIER
w32tm /resync /rediscover
You can use NetTime
to configure automatic SNTP clock synchronization. It is very fast and very reliable.
If you are running hyper-v and hosting a domain controller, that will cause all sorts of time drift. I found that if I run [nistime32.exe1 on the physical hyper-v machine, it solves my time drift problem. I recommend creating a scheduled task that runs every hour to solve the problem.
User contributions licensed under CC BY-SA 3.0