JSI Tip 9660. The Group Policy preset values for the Windows Time service in Windows Server 2003 are more restrictive than the default registry values?

When you configure the Windows Time service using group policy at Computer Configuration\Administrative Templates\System\Windows Time Service, the preset value for LargePhaseOffset and SpikeWatchPeriod are different (more restrictive) than the corresponding registry defaults at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config, causing event log errors when you apply the policy.

The LargePhaseOffset preset should be 50000000 instead of 128000. This is the time difference between local and network time which W32Time will consider a spike. The higher value generates fewer warning messages. The 128000 generates a more accurate time synchronization.

The SpikeWatchPeriod the amount of time that a suspicious offset must persist before it is accepted as correct (in seconds). The preset should be 900 seconds instead of 90 seconds.

To change the values:

1. Use the Group Policy Editor to navigate to Computer Configuration\Administrative Templates\System\Windows Time Service.

2. Double-click Global Configuration Settings.

3. Change the value of LargePhaseOffset and SpikeWatchPeriod.

4. Press Apply and OK.

NOTE: See Windows Time Service



Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish