Cannot apply policies that are edited with a computer running Multilingual User Interface Pack

Article translations Article translations
Article ID: 329816 - View products that this article applies to.
This article was previously published under Q329816
Expand all | Collapse all

On This Page

SYMPTOMS

Permissions defined in local security settings are not applied when one of the following conditions are true:
  • You install the Multilingual User Interface (MUI) pack, and you select a non-english language as the preferred language for menus and dialog boxes.
  • You have a mixture of operating system languages installed in your domain environment.
The following messages are recorded in the application event log:
Event Type: Warning
Event Source: SceCli
Event Category: None
Event ID: 1202
Date: 10/16/1999
Time: 10:13:10 am
User: N/A
Computer: Computername
Description: Security policies are propagated with warning. 0x534 : No mapping between account names and security IDs was done. Please look for more details in the Troubleshooting section in Security Help.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 10/16/1999
Time: 10:13:11 am
User: NT AUTHORITY\SYSTEM
Computer: Computername
Description: The Group Policy client-side extension Security was passed flags (17) and returned a failure status code of (1332).
The second error message occurs when you edit domain group policies on a computer that is running MUI and on which the language for the logon screen and new users (the computer language) differs from the user's user interface language. In this case, the accounts in the user rights section of the policies are written by using the computer language instead of the SID of the accounts. You can examine the Computer\Microsoft\Windows NT\SecEdit\Gpttmpl.inf file in the policy for the user names. This problem affects built-in accounts and generic accounts; it does not affect accounts in the Users container or accounts that you create.

CAUSE

When you select a language other than English in the MUI and edit group policies, the account names for the default accounts in the Group Policy files are replaced with the localized names. This causes the group policies not to be applied on English installations.

RESOLUTION

Windows XP

Hotfix information

To resolve this problem, obtain the latest service pack for Windows XP. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack

Prerequisites

To apply this hotfix, you must have Windows XP Service Pack 1 (SP1) installed.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows XP, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Scecli.dll5.1.2600.1158173,56819-Feb-200306:14x86
Sceprov.dll5.0.1636.1164,35219-Feb-200306:14x86
Scesrv.dll5.1.2600.1163307,71219-Feb-200306:14x86
Secedit.exe5.1.2600.115816,89620-Jan-200302:59x86

Windows XP, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Scecli.dll5.1.2600.1158491,00819-Feb-200306:15IA-64
Sceprov.dll5.0.1636.1593,40819-Feb-200306:15IA-64
Scesrv.dll5.1.2600.1163849,40819-Feb-200306:15IA-64
Secedit.exe5.1.2600.115836,35220-Jan-200302:59IA-64
Wscecli.dll5.1.2600.1158173,56820-Jan-200302:59x86
Wsecedit.exe5.1.2600.115816,89620-Jan-200302:59x86

Windows 2000

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To apply this hotfix, you must have Windows 2000 Service Pack 3(SP3) installed.

Restart Requirement

You must restart your computer after you apply this hotfix.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Adsldp.dll5.0.2195.6748124,68802-Sep-200303:21x86
Adsldpc.dll5.0.2195.6748132,36802-Sep-200303:21x86
Adsmsext.dll5.0.2195.674863,76002-Sep-200303:21x86
Advapi32.dll5.0.2195.6815381,71202-Sep-200303:21x86
Browser.dll5.0.2195.675369,39202-Sep-200303:21x86
Dnsapi.dll5.0.2195.6680134,92802-Sep-200303:21x86
Dnsrslvr.dll5.0.2195.678096,52802-Sep-200303:21x86
Eventlog.dll5.0.2195.681047,37602-Sep-200303:21x86
Kdcsvc.dll5.0.2195.6759148,24002-Sep-200303:21x86
Kerberos.dll5.0.2195.6758205,07218-Jun-200302:43x86
Ksecdd.sys5.0.2195.669571,88826-Mar-200306:37x86
Lsasrv.dll5.0.2195.6797509,71201-Aug-200302:40x86
Lsass.exe5.0.2195.679733,55201-Aug-200302:40x86
Msv1_0.dll5.0.2195.6786109,84017-Jul-200308:13x86
Netapi32.dll5.0.2195.6601311,56802-Sep-200303:21x86
Netlogon.dll5.0.2195.6791361,23202-Sep-200303:21x86
Ntdsa.dll5.0.2195.6810931,60002-Sep-200303:21x86
Samsrv.dll5.0.2195.6742392,46402-Sep-200303:21x86
Scecli.dll5.0.2195.6815113,93602-Sep-200303:21x86
Scesrv.dll5.0.2195.6815259,85602-Sep-200303:21x86
Sp3res.dll5.0.2195.68015,232,12814-Aug-200303:58x86
W32time.dll5.0.2195.660151,47202-Sep-200303:21x86
W32tm.exe5.0.2195.660157,10415-Aug-200222:32x86
Wldap32.dll5.0.2195.6741126,22402-Sep-200303:21x86

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was first corrected in Microsoft Windows XP Service Pack 2.

MORE INFORMATION

After you install MUI and modify the default language for menus and dialog boxes, all well-known security IDs (SIDs) such as Everyone, Authenticated Users, and Interactive are translated to the new language. Local security settings are stored in the %SystemRoot%\Security\database\Secedit.sdb file, which is actually a Microsoft Jet database. User and group accounts are stored as strings, not as SIDs. Therefore, for example, after you change the language with MUI, the "Everyone" string cannot be mapped to a valid SID and permissions cannot be applied if they previously included an account whose name has changed.

When you install the hotfix that is listed in this article, generic accounts are preserved as SIDs in the policy. However, built-in accounts behave differently. These accounts appear as SIDs and are also stored as such:
  • *S-1-5-32-548 (Account Operators)
  • *S-1-5-32-549 (System Operators)
  • *S-1-5-32-550 (Print Operators)
This occurs because the accounts do not exist on the member computer and cannot be resolved. The SID itself still indicates that it is a built-in account that is resolved locally. These are written back to the policy as SIDs and do not cause a problem.

These accounts are loaded as SIDs from the policy but are stored as strings in the computer language:
  • Administrators
  • Backup Operators
  • Guests
  • Pre-Windows 2000 Compatible Access
  • Replicator
  • Users
These SIDs are known on the member computer, but the language mappings cannot be performed correctly with the current design of Windows XP.

When you add accounts to a policy, these accounts are stored as the English equivalent if the computer and user language do not match:
  • Account Operators
  • Administrators
  • ANONYMOUS LOGON
  • Authenticated Users
  • Backup Operators
  • CREATOR GROUP
  • CREATOR OWNER
  • ENTERPRISE DOMAIN CONTROLLERS
  • Everyone
  • Guests
  • INTERACTIVE
  • NETWORK
  • Pre-Windows 2000 Compatible Access
  • Print Operators
  • Replicator
  • RESTRICTED
  • SELF
  • Server Operators
  • SERVICE
  • Users
This is a limitation of the object picker.

Many of the accounts with the issues that are listed in this article are used primarily in the Default Domain Controller policy. Microsoft recommends that you change this policy only while you are working on a domain controller (through Terminal Services), not when you are running MUI.

Other accounts have limited or no use in user rights assignment for domain members. It is a better idea to use global groups or user accounts to grant user rights. These accounts do not have the problem when they are stored under their names.

REFERENCES

890737 You receive a "No mapping between account names and security IDs was done" error when you edit and then save a Group Policy object in Windows XP Professional

Properties

Article ID: 329816 - Last Review: November 4, 2007 - Revision: 6.7
APPLIES TO
  • Microsoft Windows XP Professional
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
Keywords: 
kbhotfixserver kbqfe kbtshoot kbwinxpsp2fix kbbug kbfix kbwinxppresp2fix KB329816

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com