Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. After you apply a WMI filter, the GPO does not take effect on a client computer that is running Windows 7 or Windows Server 2008 R2

After you apply a WMI filter, the GPO does not take effect on a client computer that is running Windows 7 or Windows Server 2008 R2

View products that this article applies to.

Symptoms

In the Active Directory domain environment, you apply a Windows Management Instrumentation (WMI) filter to a Group Policy object (GPO). If a client computer is running Windows 7 or Windows Server 2008 R2, then the GPO does not take effect on this computer.

↑ Back to the top

Resolution

Hotfix information

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:
http://support.microsoft.com/contactus/?ws=support
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

There are no prerequisites to apply this hotfix.

Registry information

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

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Gpprefcl.dll6.1.7600.20617583,16814-Jan-201007:37x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Gpprefcl.dll6.1.7600.20617782,84814-Jan-201008:12x64
Gpprefcl.dll6.1.7600.20617583,16814-Jan-201007:37x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Gpprefcl.dll6.1.7600.206171,499,13614-Jan-201006:54IA-64

↑ Back to the top

Status

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

↑ Back to the top

More Information

Steps to reproduce the problem

You have the following configuration in the Active Directory domain:
  1. On the domain controller, create an Organizational Unit (OU) and link a GPO to this OU.
  2. Create a user, for example, "TestUser", and put this user into the OU.
  3. In Active Directory Users and Computers, open the properties of TestUser.
  4. On the General tab, input a string such as InTACT in the Office field, and then click OK.
  5. In Group Policy Management Console (GPMC), open the GPO and locate the following preference settings:

    User configuration\Preferences\Windows Settings\Drive Maps
  6. Create a new mapped drive entry, enable Item-level Targeting, and then use WMI filters.
  7. Set the details of the filter as following:
    Query : Select * FROM DS_User where DS_Name =" TestUser" AND DS_physicalDeliveryOfficeName="intact"
    Namespace : Root\directory\LDAP
    Property : DS_Name
  8. On a computer that is running Windows 7 or Windows Server 2008 R2, restart the computer, and then login by using the account "TestUser".
In this scenario, you notice that the drive is not mapped.

The WMI Query filter in Item-level Targeting always runs in the system context, as same as the WMI filter linked to the GPO. Its result may be different from the result received after you manually execute the same WMI Query by using test applications such as the Windows Management Instrumentation Tester (WBEMTest.exe) utility.

For more information about how to create the WMI filters, visit the following Web site:
http://technet.microsoft.com/en-us/library/cc904288(WS.10).aspx
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameX86_72fddc14da1040bb068e89610b8efeb2_31bf3856ad364e35_6.1.7600.20617_none_944a01f2649e1b15.manifest
File version
File size711
Date (UTC)15-Jan-2010
Time (UTC)19:21
PlatformNot Applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20617_none_37f6dbb5c3329282.manifest
File version
File size53,968
Date (UTC)14-Jan-2010
Time (UTC)08:00
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_72fddc14da1040bb068e89610b8efeb2_31bf3856ad364e35_6.1.7600.20617_none_f0689d761cfb8c4b.manifest
File version
File size713
Date (UTC)15-Jan-2010
Time (UTC)19:21
PlatformNot Applicable
File nameAmd64_826aa820e203ee415137ba5da3422484_31bf3856ad364e35_6.1.7600.20617_none_defe928378762732.manifest
File version
File size715
Date (UTC)15-Jan-2010
Time (UTC)19:21
PlatformNot Applicable
File nameAmd64_f405a82fbb3d4cc192f971cd3d532525_31bf3856ad364e35_6.1.7600.20617_none_a6912af8bbad115b.manifest
File version
File size715
Date (UTC)15-Jan-2010
Time (UTC)19:21
PlatformNot Applicable
File nameAmd64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20617_none_941577397b9003b8.manifest
File version
File size53,972
Date (UTC)14-Jan-2010
Time (UTC)08:48
PlatformNot Applicable
File nameWow64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20617_none_9e6a218baff0c5b3.manifest
File version
File size34,836
Date (UTC)14-Jan-2010
Time (UTC)07:52
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_7276223ede535c2920439763f656c9e5_31bf3856ad364e35_6.1.7600.20617_none_df9aa1ba45539720.manifest
File version
File size713
Date (UTC)15-Jan-2010
Time (UTC)19:21
PlatformNot Applicable
File nameIa64_72fddc14da1040bb068e89610b8efeb2_31bf3856ad364e35_6.1.7600.20617_none_944ba5e8649c2411.manifest
File version
File size712
Date (UTC)15-Jan-2010
Time (UTC)19:21
PlatformNot Applicable
File nameIa64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20617_none_37f87fabc3309b7e.manifest
File version
File size53,970
Date (UTC)14-Jan-2010
Time (UTC)08:30
PlatformNot Applicable

↑ Back to the top

Keywords: kbexpertiseinter, kbprb, kbsurveynew, kbhotfixserver, kbautohotfix, kbqfe, kbfix, kb

↑ Back to the top

Article Info
Article ID : 979383
Revision : 1
Created on : 1/7/2017
Published on : 1/4/2011
Exists online : False
Views : 213