E
Ercan KOÇ
Hello,
On our servers in the domain structure, the clock setting is corrupted by itself. After a while, the time setting is automatically updated to the previous state.
When the clock setting is broken, the event log is saved as below.
Change Reason: An application or system component changed the time.
When the clock setting is correct, the event log is as follows.
The time service is now synchronizing the system time with the time source 192.168.1.6,0x01 (ntp.m|0x1|0.0.0.0:123->192.168.1.6:123).
192.168.1.6 is Primary DC.
w32tm query results at Server which is facing time sync issue.
PS C:\Users\ekoc> w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 3 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0889282s
Root Dispersion: 0.0936396s
ReferenceId: 0xC0A80106 (source IP: 192.168.1.6)
Last Successful Sync Time: 6.5.2019 13:35:25
Source: 192.168.1.6,0x01
Poll Interval: 12 (4096s)
w32tm query result at Primary DC
PS C:\Users\ekoc> w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0624775s
Root Dispersion: 0.2857063s
ReferenceId: 0x3E0CAD0C (source IP: 62.12.173.12)
Last Successful Sync Time: 5/6/2019 1:53:27 PM
Source: 0.pool.ntp.org,
Poll Interval: 6 (64s)
I've created this GPO but issue isn't resolved
Policies
Administrative Templates
Policy definitions (ADMX files) retrieved from the local computer.
System/Windows Time Service/Time Providers
Continue reading...
On our servers in the domain structure, the clock setting is corrupted by itself. After a while, the time setting is automatically updated to the previous state.
When the clock setting is broken, the event log is saved as below.
Change Reason: An application or system component changed the time.
When the clock setting is correct, the event log is as follows.
The time service is now synchronizing the system time with the time source 192.168.1.6,0x01 (ntp.m|0x1|0.0.0.0:123->192.168.1.6:123).
192.168.1.6 is Primary DC.
w32tm query results at Server which is facing time sync issue.
PS C:\Users\ekoc> w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 3 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0889282s
Root Dispersion: 0.0936396s
ReferenceId: 0xC0A80106 (source IP: 192.168.1.6)
Last Successful Sync Time: 6.5.2019 13:35:25
Source: 192.168.1.6,0x01
Poll Interval: 12 (4096s)
w32tm query result at Primary DC
PS C:\Users\ekoc> w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0624775s
Root Dispersion: 0.2857063s
ReferenceId: 0x3E0CAD0C (source IP: 62.12.173.12)
Last Successful Sync Time: 5/6/2019 1:53:27 PM
Source: 0.pool.ntp.org,
Poll Interval: 6 (64s)
I've created this GPO but issue isn't resolved
Policies
Administrative Templates
Policy definitions (ADMX files) retrieved from the local computer.
System/Windows Time Service/Time Providers
Policy | Setting | Comment | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Enabled | ||||||||||||||||
| ||||||||||||||||
Policy | Setting | Comment | ||||||||||||||
| <span class="explainlink" gpmc_settingdescription="This policy setting specifies whether the Windows NTP Client is enabled. Enabling the Windows NTP Client allows your computer to synchronize its computer clock with other NTP servers. You might want to disable this service if you decide to use a third-party time provider. If you enable this policy setting, you can set the local computer clock to synchronize time with NTP servers. If you disable or do not configure this policy setting, the local computer clock does not synchronize time with NTP servers. " gpmc_settingname="Enable Windows NTP Client" gpmc_settingpath="Computer Configuration/Administrative Templates/System/Windows Time Service/Time Providers" gpmc_supported="At least Windows Server 2003 operating systems or Windows XP Professional" style="color:#0000ff;cursor  ointer;" tabindex="0">Enable Windows NTP Client |
Continue reading...