Time Synchronization in AD Environment

[Guest]

My question is :
How can you take impact of the "polling interval" for AD Clients ?

1.) First I enabled tracing actions from w32time services to a log file,
because getting information from the "event log" is nearly useless.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config]
"FileLogName"="C:\\Temp\\W32Time.log"
"FileLogEntries"="0-116"
"FileLogSize"=dword:1000000
2.) The log file shows that the polling intervall (starting with 1024 sec)
is doubled after maybe 4-5 successful actions (reaching 32768 sec, about 9 h,
or more).
PeerPollingThread: waiting 1024.000s
....
PeerPollingThread: waiting 2048.000s
....
3.) We need really exact time clock on our PCs for broadcasting operations.
So I would like to configure a "not variable" polling interval.
All settings that I found in the regestry documentation doesn't have impact
on the working flow of the w32time service (s. 2)
4.) I tried the following keys without success.
4.a)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient]
"ResolvePeerBackoffMinutes"=dword:0000000a
"ResolvePeerBackoffMaxTimes"=dword:00000000
4.b)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config]
"MaxPollInterval"=dword:0000000f
4.c)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient]
"SpecialPollInterval"=dword:0000000f

Kindly regards

 

[Alex Nichol]

"Harald Thiel (RTL-Television)" <Harald Thiel

My question is :
How can you take impact of the "polling interval" for AD Clients ?

1.) First I enabled tracing actions from w32time services to a log file,
because getting information from the "event log" is nearly useless.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config]
"FileLogName"="C:\\Temp\\W32Time.log"
"FileLogEntries"="0-116"
"FileLogSize"=dword:1000000
2.) The log file shows that the polling intervall (starting with 1024 sec)
is doubled after maybe 4-5 successful actions (reaching 32768 sec, about 9 h,
or more).
PeerPollingThread: waiting 1024.000s
...
PeerPollingThread: waiting 2048.000s
...
3.) We need really exact time clock on our PCs for broadcasting operations.
So I would like to configure a "not variable" polling interval.

A major point about W32Time is that it adjusts the system's idea of the
actual interval between timer interrupts (counted by windows clock as
its base) so that after a few occasions this is very near accurate, and
very frequent updates no longer needed. But you have to make sure that
your application processes are in fact interrogating the windows clock,
and not keeping their own time on the basis of a default assumption of
the interval, which may be quite a bit out. I have an independent clock
on the desktop, and it runs in time out of sync, until next restarted
(and after the DST change has to be restarted so it is not an hour out)

 

[Guest]

Thanks for your answer,

of course basically its a good idea to adjust the polling interval
automatically by w32time service.
On the other hand, microsoft offers the ability to set fixed interval
periods by regestry settings, and these settings don't work...
My experience with w32time service is, that in case of unsynchronizity of
local time clock, the increasing of the polling interval is to less...

Kindly regards

"Harald Thiel (RTL-Television)" <Harald Thiel

My question is :
How can you take impact of the "polling interval" for AD Clients ?

1.) First I enabled tracing actions from w32time services to a log file,
because getting information from the "event log" is nearly useless.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config]
"FileLogName"="C:\\Temp\\W32Time.log"
"FileLogEntries"="0-116"
"FileLogSize"=dword:1000000
2.) The log file shows that the polling intervall (starting with 1024 sec)
is doubled after maybe 4-5 successful actions (reaching 32768 sec, about 9 h,
or more).
PeerPollingThread: waiting 1024.000s
...
PeerPollingThread: waiting 2048.000s
...
3.) We need really exact time clock on our PCs for broadcasting operations.
So I would like to configure a "not variable" polling interval.

A major point about W32Time is that it adjusts the system's idea of the
actual interval between timer interrupts (counted by windows clock as
its base) so that after a few occasions this is very near accurate, and
very frequent updates no longer needed. But you have to make sure that
your application processes are in fact interrogating the windows clock,
and not keeping their own time on the basis of a default assumption of
the interval, which may be quite a bit out. I have an independent clock
on the desktop, and it runs in time out of sync, until next restarted
(and after the DST change has to be restarted so it is not an hour out)