Preset values for the Windows Time service Group Policy settings are different from the corresponding Windows Time service registry entries in Windows Server 2003

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.

Notes

• The registry entries for the Windows Time service are found under the following registry subkey:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time
• 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:
  HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\W32Time
  The LargePhaseOffset and SpikeWatchPeriod registry entries appear under both the following registry subkeys:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
  
  
  HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\W32Time\Config
  
  However only the values of the following registry subkey are applied:
  HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\W32Time\Config