SceCli 1202 events are logged every time Computer Group Policy settings are refreshed on a computer that is running Windows Server 2008 R2 or Windows 7

Symptoms

Consider the following scenario:

• On a computer that is running Windows Server 2008 R2 or Windows 7, you use Group Policy Management Editor to manage a Group Policy object (GPO).

• Many changes are made to the "User Rights Assignment" settings in the GPO and these settings have a per-service SID defined.

In this scenario, when the Group Policy is applied, you may experience the following problems:

• A SceCli 1202 event is added into the Application event log:
  
  The following is an example of a SceCli 1202 event log entry:

• Some applications or services may not start. These applications or services use the per-service SID to configure security settings.
  
  For example:

  1. You install Active Directory Domain Services on a Windows Server 2008 R2-based member server.

  2. You make a change to the "User Rights Assignment" setting in a GPO from a computer that is running Windows Server 2008 R2 or Windows 7.

  3. This GPO is applied to the domain controller that is running Windows Server 2008 R2.

  In this situation, you encounter the issue. Some services, such as the "Diagnostic System Host" service cannot start because of the issue.

Cause

When the Group Policy Management Editor modifies settings under User Rights Assignment, it translates per-service SIDs to the service names. For example, the "WdiSystemHost" service name.

The Group Policy Management Editor does not add the prefix "NT Service" to the service name to perform the lookup in the internal “NT Service” domain. When the Group Policy Management Editor writes the previously parsed name back into the GptTmpl.inf file, it tries to resolve only the "WdiSystemHost" name against the default Active Directory domain. However, this attempt fails. Additionally, the "WdiSystemHost" string is written to GptTmpl.inf file instead of the SID. This behavior replaces the per-service SID with the service name.



When the next policy refresh occurs, the refresh tries to resolve the service name to a SID as if it were a user or group account. However, this fails together with the error 0x534 "No mapping between account names and security IDs was done."

Resolution

Note The hotfix does not automatically resolve this problem. After you apply this hotfix, you must manually append "NT SERVICE\" directly in the GptTmpl.inf file. For example, you must replace "WdiSystemHost" with "NT SERVICE\WdiSystemHost" by using the Local Group Policy Editor.

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=supportNote 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.

Status

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

More Information

After the issue occurs, the following error is added to the Winlogon.log file:

Note The Winlogon.log file is located in the following folder:

%windir%\security\logs

If you open the GptTmpl.inf file in the following related Group Policy folder, you find some SQL service names:

%SYSTEMROOT%\SYSVOL\<domainname.com>\Policies\<Unique ID>\Machine\Microsoft\Windows NT\SecEdit

The following is an example of the WDI service names that are found in the GptTmpl.inf file:

[Privilege Rights]

SeAssignPrimaryTokenPrivilege = WdiServiceHost,*S-1-5-20,*S-1-5-19

SeChangeNotifyPrivilege = WdiServiceHost,*S-1-5-32-554,*S-1-5-11,*S-1-5-32-544,*S-1-5-20,*S-1-5-19,*S-1-1- 0

Note The hotfix does not automatically resolve this problem. After you apply this hotfix, you must manually append "NT SERVICE\" directly in the GptTmpl.inf file. For example, you must replace "WdiSystemHost" with "NT SERVICE\WdiSystemHost" by using the Local Group Policy Editor.

For more information, 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