On a Microsoft Windows Server 2003-based computer, you notice that the preset values for the Windows Time service Group Policy settings are different from the corresponding Windows Time service registry entries.
Specifically, the preset Group Policy settings are more restrictive than the corresponding default registry entries. These more restrictive settings may trigger event logging instead of the expected time synchronization with the server.
The registry entries for the Windows Time service are found under the following registry subkey:
Certain Group Policy settings have the same names as the registry entries for the Windows Time service. For example, the LargePhaseOffset and SpikeWatchPeriod Group Policy settings appear in the following location in the Group Policy Object Editor:
Computer Configuration\Administrative Templates\System\Windows Time Service
However, the policy updates the following location in the system registry:
This issue occurs because some of the preset values that are configured in the System Administrative template file (System.adm) for the Group Policy object (GPO) settings are different from the corresponding default registry entries.
To work around this issue, use the Group Policy Object Editor to change the value for the LargePhaseOffset Group Policy setting. To do this, follow these steps:
Click Start, click Run, type gpedit.msc, and then click OK.
In the Group Policy Object Editor, expand Computer Configuration, expand Administrative Templates, expand System, and then click Windows Time Service.
On the right pane, double-click Global Configuration Settings.
On the Setting tab, change the value of the LargePhaseOffset Global Group Policy setting. The recommended preset value is 50000000.
For more information about the LargePhaseOffset setting, visit the following Microsoft Web site: