I'm looking for information on how the Windows TIme Service over a domain affects the hardware clock. The machines are clients on a Windows AD domain with the basic time services. It's not our network so I don't have a lot of detail.
1) We are doing some transaction based processing with a remote host. We normally see the a difference of about 250 ms between OS clocks included network delays. This is fine.
2) If the computer is rebooted the difference is about 10 seconds. It takes about 30 minutes to get back down to the 250 ms again. I believe this is called convergence.
I'd like some direction on where to look for information regarding:
a) Does the Windows Time service ever update the real-time hardware clock to keep it close? b) Is there a way to tell the Time service to do a faster convergence? c) I think this service is a bit different from NTP which could be configured. Right?
My searches have not addressed the RTC and ways to speed up the convergence.