While modifying that registry value may update the "next sync time" displayed in the control panel, I have found it does not actually affect how often the clock is synched. There is a SpecialPollInterval setting under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\NtpClient (note: it has moved at least once between Windows versions) which is the time (in minutes) between time syncs.
How not to do it 2: The SpecialPollInterval registry value In that situation it's still up to the Windows Time service when to actually performs a sync, which will be once per week. Upon investigation, that task simply makes sure the Windows Time service is running and if it's already running the task does nothing. I tried making that task run once a day and my clocks still drifted. I've seen suggestions that you change the existing Synchronize Time scheduled task so that it runs more often. How not to do it 1: The Synchronize Time task Despite the apparent awfulness of PC clocks, Windows doesn't provide any user-facing options to change the clock-sync frequency below once a week. They seem to drift by about five minutes each week and that messes up things like scheduled TV recordings or stating that it is 13:37 o'clock on IRC when it's not.
I don't know about your machines but both my desktop and my HTPC have terrible clocks. This was tested on Windows 7 but should work with Windows XP and above.
Make mac check for updates more often how to#
This page explains how to make the Windows network time (NTP) client synchronize its time more often than the default once per week.