Article ID: 902229 - View products that this article applies to.
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.
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:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about Windows Time Service tools and settings, visit the following Microsoft Web site:
Article ID: 902229 - Last Review: July 6, 2013 - Revision: 6.0