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.

Group Policy preference item-level targeting does not work for 64-bit versions of Windows 7


View products that this article applies to.

Symptoms

In an Active Directory Domain Services (AD DS) environment, you use Group Policy preference item-level targeting to push files that contain file paths to different operating systems.

However, the Group Policy preference item-level targeting does not work for 64-bit versions of Windows 7.

The following is a sample scenario:
  • You configure Group Policy Preferences by using the following settings:
    Mode of GPP: Replace
    Source File Location: \\server\share\x64.ini
    Target File Location: c:\temp\x64.ini
  • You configure the Group Policy item-level targeting rules by using the following settings:
    The operating system is Windows 7 (64-bit Enterprise Edition)
    OR the operating system is Windows 7 (64-bit Business Edition)
    OR the operating system is Windows 7 (64-bit Ultimate Edition)
In the sample scenario, the 64-bit versions of Windows 7 operating systems cannot correctly obtain the x64.ini file from the source file location.

↑ 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 website: 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 be running the following operating system:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
Additionally, you must be running a 64-bit version of Windows 7.

Registry information

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

Restart requirement

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.

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 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 files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.1.760
    0.20xxx
    Windows 7RTMLDR
    6.1.760
    1.21xxx
    Windows 7SP1LDR
  • 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 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Gpprefcl.dll6.1.7600.20861784,89618-Dec-201006:06x64
Gpprefcl.dll6.1.7601.21624784,89618-Dec-201008:51x64
Gpprefcl.dll6.1.7600.20861584,19218-Dec-201005:27x86
Gpprefcl.dll6.1.7601.21624584,19218-Dec-201007:57x86
Gpprefcl.dll6.1.7600.20861584,19218-Dec-201005:27x86
Gpprefcl.dll6.1.7601.21624584,19218-Dec-201007:57x86

↑ Back to the top


Workaround

Workaround for Windows 7

To work around this issue, use the following environment variable for the Group Policy item-level targeting filter.

<Filters>
<FilterOs bool="AND" not="0" class="NT" version="WIN7" type="NE" edition="NE" sp="NE" />
- <FilterCollection bool="AND" not="0">
<FilterVariable bool="AND" not="0" variableName="%Processor_Architecture%" value="AMD64" />
</FilterCollection>
</Filters>

↑ 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

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

For more information about how to use Group Policy Preferences to manage diversity, visit the following Microsoft webpage:
For more information about Group Policy Preferences, visit the following Microsoft webpage:

Additional file information

Additional file information for Windows 7

Additional files for all supported x64-based versions of Windows 7
File nameAmd64_1f23aa3dcd73640161bcf67ce13e6da7_31bf3856ad364e35_6.1.7601.21624_none_9f1caacd5de91682.manifest
File versionNot applicable
File size713
Date (UTC)20-Dec-2010
Time (UTC)21:33
PlatformNot applicable
File nameAmd64_34811dd9971d07f4b90259b2a60a0044_31bf3856ad364e35_6.1.7600.20861_none_00bffa7f2c83ce11.manifest
File versionNot applicable
File size715
Date (UTC)20-Dec-2010
Time (UTC)21:33
PlatformNot applicable
File nameAmd64_949a15c1646f007ba1540fb36cf63711_31bf3856ad364e35_6.1.7600.20861_none_15282c5275e5fd0d.manifest
File versionNot applicable
File size713
Date (UTC)20-Dec-2010
Time (UTC)21:33
PlatformNot applicable
File nameAmd64_d063ee55f940ebfb78d0754a7e98a690_31bf3856ad364e35_6.1.7600.20861_none_e18e2d3ff8204f70.manifest
File versionNot applicable
File size1,070
Date (UTC)20-Dec-2010
Time (UTC)21:33
PlatformNot applicable
File nameAmd64_d5062463e09086e8f9afeae1a5ada28c_31bf3856ad364e35_6.1.7601.21624_none_7be3ad88bd4e9dbb.manifest
File versionNot applicable
File size715
Date (UTC)20-Dec-2010
Time (UTC)21:33
PlatformNot applicable
File nameAmd64_e98220e070175d6c26a988e427f5e28c_31bf3856ad364e35_6.1.7600.20861_none_d193cea90d3739f9.manifest
File versionNot applicable
File size715
Date (UTC)20-Dec-2010
Time (UTC)21:33
PlatformNot applicable
File nameAmd64_fdb9102779c801a1373d69d8cd032451_31bf3856ad364e35_6.1.7601.21624_none_557f5c7ed094fc0c.manifest
File versionNot applicable
File size715
Date (UTC)20-Dec-2010
Time (UTC)21:33
PlatformNot applicable
File nameAmd64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20861_none_93d969ad7bbdf1b1.manifest
File versionNot applicable
File size53,972
Date (UTC)18-Dec-2010
Time (UTC)06:52
PlatformNot applicable
File nameAmd64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.21624_none_95ee074178c139de.manifest
File versionNot applicable
File size53,972
Date (UTC)18-Dec-2010
Time (UTC)09:25
PlatformNot applicable
File nameWow64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20861_none_9e2e13ffb01eb3ac.manifest
File versionNot applicable
File size34,836
Date (UTC)18-Dec-2010
Time (UTC)05:51
PlatformNot applicable
File nameWow64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.21624_none_a042b193ad21fbd9.manifest
File versionNot applicable
File size34,836
Date (UTC)18-Dec-2010
Time (UTC)08:24
PlatformNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20861_none_37bace29c360807b.manifest
File versionNot applicable
File size53,968
Date (UTC)18-Dec-2010
Time (UTC)05:58
PlatformNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.21624_none_39cf6bbdc063c8a8.manifest
File versionNot applicable
File size53,968
Date (UTC)18-Dec-2010
Time (UTC)08:32
PlatformNot applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2460922
Revision : 1
Created on : 1/7/2017
Published on : 2/10/2011
Exists online : False
Views : 175