Microsoft KB Archive/931026

= Error message when you try to apply a computers or users policy if PolicyMaker Standard Edition is installed: &quot;Policy for [computers or users], in the GPO '[GPO name]{[GPO GUID]}' was not applied because there was an error determining usage&quot; =

Article ID: 931026

Article Last Modified on 1/30/2007

-

APPLIES TO


 * PolicyMaker Standard Edition 2.0
 * PolicyMaker Standard Edition 1.0

-



SYMPTOMS
When you try to apply a computers policy or a users policy on a computer that has Desktop Standard PolicyMaker Standard Edition installed, the following error message is logged in the application event log:

Policy for [ ], in the GPO '[ ]{[ ]}' was not applied because there was an error determining usage.



CAUSE
This issue occurs because one of the following conditions is true:  Special characters appear in the name of one of the following objects:  Organizational unit (OU) Container of the user Container of the computer

For example, a slash mark (/) or an ampersand (&) appears in the name. The Authenticated Users group does not have Read permission for the Group Policy object (GPO).

This issue occurs if the computers or users policy item is located under User Configuration instead of under Computer Configuration. Additionally, the following versions of PolicyMaker Standard Edition products are used:  PolicyMaker Standard Edition 2.5.0</li> PolicyMaker Software Update 1.3.0</li> PolicyMaker Application Security 1.1.0</li></ul>

These specific versions of PolicyMaker products obtain a GPO license that applies across the whole system. Therefore, the computer accounts must have Read permission to the GPO.</li></ul>

<div class="workaround_section">

WORKAROUND
To work around this issue, use one of the following methods:  If this issue occurs because special characters appear in the name of an OU, delete the special characters from the name of the OU.

Note We recommend that you do not use special characters in the name of an OU.

</li> If this issue occurs because the Authenticated User group does not have Read permission for the GPO, grant the Authenticated User group Read permission to the GPO. Alternatively, grant Read permission to a group that contains the relevant computer accounts. The relevant computer accounts are for those users who want to log on to the GPO.

Note This issue will be resolved in the next release of the specific versions of PolicyMaker products that are mentioned in the &quot;Cause&quot; section.

</li></ul>

Keywords: kbtshoot kbexpertiseinter kbprb KB931026

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.