The Group Policy Object Editor MMC snap-in displays a Group Policy setting as "Not configured" when the value of the setting is longer than 1,024 characters

On a Windows Server 2003-based computer, you configure an administrative template Group Policy setting. For example, you configure the following setting: If the value of the setting is longer than 1,024 characters, the Group Policy Object Editor Microsoft Management Console (MMC) snap-in displays the Group Policy setting as "Not configured."

Note The state of the Group Policy setting is displayed correctly in the Group Policy Management console (GPMC) MMC snap-in.

Additionally, when you run the Resultant Set of Policies (Rsop.msc) utility to check this Group Policy setting, you find that the setting is not listed. However, this setting is active, and it can be applied successfully to client computers.

The issue causes the administrator to be unable to modify the policy because the current content is missing when they open the setting. If the Administrator clicks OK in the Settings dialog box, the setting is reset to an empty string and the current setting is removed.

Two of the settings that have a good chance of exceeding the 1024 character limit are:
User Configuration\Administrative Templates\System\User Profiles\Exclude directories in roaming profile
User Configuration\Windows Settings\Internet Explorer Maintenance\Connection/Proxy Settings

Note This problem also occurs in Windows Vista and Windows Server 2008.

This problem occurs because the registry extension engine that is used by the Group Policy Object Editor snap-in cannot load settings that are longer than 1,024 characters.

A hotfix is available to resolve this problem. After you apply this hotfix, the Group Policy Object Editor snap-in and the rsop.msc utility can load settings that contain up to 4,096 characters.

Hotfix information for Windows Server 2003

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.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 2 installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix. This is true if the Group Policy Management MMC snap-in and the Group Policy Editor MMC snap-in are running.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

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 Server 2003 Service Pack 2, x86-based versions

Windows Server 2003 Service Pack 2, x64-based versions

Windows Server 2003 Service Pack 2, Itanium-based versions

Hotfix information for Windows Vista and Windows Server 2008

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.

Prerequisites

To apply this hotfix, the computer must run one of the following:

• Windows Vista
• Windows Vista SP1
• Windows Server 2008

Restart requirement

You have to restart the computer after you apply this hotfix. This is true if the Group Policy Management MMC snap-in and the Group Policy Editor MMC snap-in are running.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

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 Server 2008 and Windows Vista note

The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and Windows Vista

For all supported x64-based versions of Windows Server 2008 and Windows Vista

For all supported Itanium-based versions of Windows Server 2008

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008