This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario. On a Windows Server 2008-based computer or on a Windows Vista Service Pack 1-based computer, you enable the Computer configuration/Policies/Administrative Templates/System/Windows time service/Global configuration Group Policy setting. Then, you configure some of its settings in a Group Policy object (GPO). After you specify the settings that you want, some other settings of the global configuration are also changed. Therefore, unexpected behavior may occur in the Windows Time service.
Note A hotfix was developed that replaces the .admx and .adml files that cause this problem. This hotfix enables the policy default values to comply with the recommended values.
This problem occurs because the default values of the Global Configuration settings do not correspond to the operating system default values. When you enable this policy and then edit some settings, other settings are also enabled. This causes changes in the behavior of the Windows Time service.
For example, the following settings may be changed.
OS Registry Default
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.
To apply this hotfix on Windows Vista-based computers, you must have Windows Vista Service Pack 1 (SP1) installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
No prerequisites are required for Windows Server 2008-based computers.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Vista and Windows Server 2008 file information notes
The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed by using a Microsoft digital signature. The attributes of these security files are not listed.
For all supported 32-bit versions of Windows Server 2008 and Windows Vista
For all supported 64-bit versions of Windows Server 2008 and Windows Vista
To work around this problem, adjust the operating system default values manually when you enable this policy. For more information, visit the following Microsoft Web site: