This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You deploy per-machine printer connections to client computers that are running Windows Server 2008 or Windows Vista Service Pack 1 (SP1) by using group policies.
You remove one or more per-machine printer connections by using group policies.
In this scenario, the per-machine printer connections are removed successfully on the print client. However, these connections are still displayed in the Group Policy object (GPO) report.
For example, you run Rsop.msc to obtain a GPO report after you remove a per-machine printer connection by using a Group Policy. However, the per-machine printer connection that was removed is still displayed in the GPO report.
The client-side Group Policy extension for pushed printer connections does not correctly record Windows Management Instrumentation (WMI) data when per-machine printer connections are removed. Additionally, the Group Policy Management Console (GPMC) does not correctly use WMI data when it generates GPO reports.
To fix this problem, install this hotfix on the print client computer that is running Windows Server 2008 or Windows Vista. Note We recommend that you install the hotfix that is described in KB 960594 before you install the hotfix that is described in this article. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960594 Per-machine printer connections that are deployed by using group policies may not be removed completely from Windows Server 2008 and Windows Vista S-based computers
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problemP1 that P2 described in this article. Apply this hotfix only to systems that are experiencing the problemP1 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, your computer must be running one of the following operating systems:
Windows Server 2008
Windows Server 2008 Service Pack 2
Windows Vista Service Pack 1
Windows Vista Service Pack 2
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other previously released hotfixes.
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. The MANIFEST files (.manifest) and the MUM files (.mum) that are 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 of Windows Vista SP1