Group Policy objects are not renamed on Windows 2000-based client computers (834645)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
SYMPTOMSWhen you rename an existing Group Policy object (GPO) that
contains a Microsoft Windows Installer package for deployment on a Microsoft
Windows 2000-based computer, you may find that the GPO name is not changed on
the Windows 2000-based client computers. The following event may be logged in
the application event log:
Event Type: Information Event Source: Application
Management Event Category: None Event ID: 301 Description: The
assignment of application Package_Name from policy
Policy_Name succeeded. CAUSEThis problem may occur when the policy name is not updated
in the following registry subkey on the client computers. The policy name is
not updated because the GPO name is derived from the ExtensionName attribute in the class store container. The ExtensionName attribute is set only one time, when the application is first
deployed in the GPO. If the GPO name is changed after the deployment, the
attribute will not be updated in the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Group Policy\AppMgmt\GUID\GPO Name WORKAROUNDTo work around this problem, rename the GPO that contains
the Windows Installer policy. To do this, follow these steps:
- Click Start, point to
Programs, point to Administrative Tools, and
then click Active Directory Users and Computers.
- Locate and then right-click the GPO, and then click
Properties.
- On the Group Policy tab, right-click the
appropriate application name in Group Policy Object Links, and
then click Rename.
- Type the name that you want.
Modification Type: | Major | Last Reviewed: | 2/9/2006 |
---|
Keywords: | kbtshoot kbprb KB834645 kbAudITPRO |
---|
|