On Thu, Aug 13, 2009 at 3:53 AM, Ulrich Windl<[email protected]> wrote:
> (Interestingly Windows "genuine" NTP client adjusts the clock once per > week by default. Why not use that service?) That is incorrect information. In WinXP and newer, The default value of UpdateInterval for the Windows time service is: Once every 100 ticks for windows domain controllers Once every 30000 ticks for Windows domain members Once every 360000 ticks for stand-alone machines (home computers) A tick is gnerally 1/64s on modern hardware, so that gives timings of: ~1.5 s for domain controllers ~8 minutes for domain members ~94 minutes for stand-alone systems You can set the UpdateInterval to whatever you want using Group Policies (local or network-based) or registry edits. I my experience, domain controllers using w32time stay within their stated precision of 16ms, as measured by another system runing ntpd using the same set of stratum 2-sources on a LAN. In our environment, even domain workstations rarely show more than 100 ms offset, despite only adjusting the system clock once every 8 minutes. Source: http://technet.microsoft.com/en-us/library/cc773263(WS.10,loband).aspx#w2k3tr_times_tools_uhlp -- RPM _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
