I’d suggest keeping all machines sync’ed using NTP stratum 2 (or 3) time server pools (should be exact enough). Since some PC clocks drift a lot
, we recommend to our users to sync every hour, and actually distribute a small .reg file (for Windows) to them that sets the correct time servers (not
Windows!) and the update interval to one hour.
Here’s an example of »set time.reg« for North America:
Windows Registry Editor Version 5.00
You might want to check out the NTP Pool Servers page
for more details. The tend to be a reliable source, since there usally several hundred servers in any one pool. (If you are not in North America, please select another appropriate pool.)
You can just copy the code into a text file, save it as »something_appropriate.reg«, double-click the file and answer »yes« to the security question.Hint:
If there is a long
update interval currently set (which is usually the case), it will do the first update only after
the current interval has expired. Rebooting helps Hint:
It also helps a lot if the servers are sync’ed to reliable NTP sources. Ask your provider, or set up the same NTP settings on your Linux server (a snap).