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.

Error message when you run the "Set-GPPermission" cmdlet or the "Get-GPPermission" cmdlet: ""_ploc" is not a valid security group"


View products that this article applies to.

Symptoms

When you use the "Set-GPPermissions" Windows PowerShell cmdlet or the "Get-GPPermissions" Windows PowerShell cmdlet together with a well-known security principal as the TargetName, you receive the following error message on a computer that is running a non-English version of Windows Server 2008 R2 or of Windows 7:
Set-GPPermissions / Get-GPPermissions: The operation cannot be completed because " <Well-Known security principal>_ploc" is not a valid security group in the <domain name> domain. Make sure that the TargetName and TargetType parameters specify a valid security group for the domain. Then, run the command again. Parameter name: TargetName

↑ Back to the top


Cause

This issue occurs because both of the commands query Active Directory domain for the TargetName parameter. However, the "_ploc" suffix is incorrectly added to the well-known security principals in this operation. This behavior causes the error message that is mentioned in the "Symptoms" section.

↑ 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: 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, your computer must be running one of the following operating systems:
  • Windows 7
  • Windows Server 2008 R2
Additionally, a computer that is running Windows 7 must have the Remote Server Administration Tools (RSAT) installed, and a computer that is running Windows Server 2008 R2 must have the Group Policy Management Console (GPMC) installed.

Note RSAT includes the GPMC and the Group Policy cmdlets.

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 English (United States) 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.grouppolicy.commands.dll6.1.7600.20604135,16824-Dec-200907:05x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.grouppolicy.commands.dll6.1.7600.20604135,16824-Dec-200907:45x86
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.grouppolicy.commands.dll6.1.7600.20604135,16824-Dec-200906:25x86

↑ 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

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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msil_microsoft.grouppolicy.commands_31bf3856ad364e35_6.1.7600.20604_none_ff051cfc7e762117.manifestNot Applicable1,64324-Dec-200907:34Not Applicable
Update.mumNot Applicable1,45824-Dec-200911:37Not Applicable
X86_9dbaae6bedff681f5b798b030dbacdd5_31bf3856ad364e35_6.1.7600.20604_none_44969b6068f97278.manifestNot Applicable70124-Dec-200911:37Not Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_9dbaae6bedff681f5b798b030dbacdd5_31bf3856ad364e35_6.1.7600.20604_none_a0b536e42156e3ae.manifestNot Applicable70324-Dec-200911:37Not Applicable
Msil_microsoft.grouppolicy.commands_31bf3856ad364e35_6.1.7600.20604_none_ff051cfc7e762117.manifestNot Applicable1,64324-Dec-200910:11Not Applicable
Update.mumNot Applicable1,67924-Dec-200911:37Not Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ia64_9dbaae6bedff681f5b798b030dbacdd5_31bf3856ad364e35_6.1.7600.20604_none_44983f5668f77b74.manifestNot Applicable70224-Dec-200911:37Not Applicable
Msil_microsoft.grouppolicy.commands_31bf3856ad364e35_6.1.7600.20604_none_ff051cfc7e762117.manifestNot Applicable1,64324-Dec-200908:12Not Applicable
Update.mumNot Applicable1,45424-Dec-200911:37Not Applicable

↑ Back to the top


Keywords: kbqfe, kbhotfixserver, kbsurveynew, kbautohotfix, kbexpertiseinter, kbbug, kbfix, KB978838

↑ Back to the top

Article Info
Article ID : 978838
Revision : 1
Created on : 2/8/2010
Published on : 2/8/2010
Exists online : False
Views : 490