Network users may experience extended logon times in Windows 2000

Your network user accounts may take a long time to log on to the network, especially if your network has several trusted domains.

Additionally, user rights assignments may not work as expected. On affected client computers, the event log may contain the following entry:

Event Type: Warning
Event Source: SceCli
Event Category: None
Event ID: 1202
Date: <MM/DD/YYYY>
Time: <HH:MM:SS AM|PM>
User: N/A
Computer: %<ComputerName>%
Description: Security policies are propagated with warning. <ErrorCode>: No mapping between account names and security IDs was done. Please look for more details in TroubleShooting section in Security Help.

For more information about troubleshooting SceCli 1202 events, click the following article number to view the article in the Microsoft Knowledge Base: Check the Gpttmpl.inf file to verify user rights settings. The Gpttmpl.inf file is located in the following Group Policy folder, where the default path for the Sysvol folder is %SystemRoot%\Sysvol: The GUID entry in the Gpttmpl.inf file will be similar to the following, where user right is a user right such as SeBackupPrivilege or SeInteractiveLogonRight:The operator accounts in this entry are only examples. This problem may occur with any one of the following groups in the Windows 2000 Active Directory built-in container:

• Account operators
• Administrators
• Backup operators
• Guests
• Pre-Windows 2000 Compatible Access
• Print operators
• Replicator
• Server operators
• Users

When Windows saves the Gpttmpl.inf file, the accounts that are listed in the "Symptoms" section of this article are not saved to the policy using the security identifier (SID). Instead, the Gpttmpl.inf file has the account names in the Group Policy user interface (UI) section.

Client computers experience this problem if one or more of the following conditions are true:

• An account does not exist on domain members.
• The SAM account name of an account differs from the name in the domain. This also applies to clients that are running the Multilingual User Interface Pack (MUI) with a different default language.
• The SAM account name of an account was renamed on the clients.

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 this specific problem.

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, submit a request to 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

No prerequisites are required.

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 file attributes) 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.hNote This hotfix does not change the account names of the SIDs in the affected policies. To correct the policy .inf files, you must make a change to the security settings of the affected group policies on the domain controller that is running the hotfix. Then, the .inf files will be written back to SYSVOL with the SIDs.

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

When you install this hotfix, generic accounts are preserved as SIDs in the policy. Built-in accounts behave differently. The following accounts appear as SIDs and are also stored as follows:

• *S-1-5-32-548 (Account Operators)
• *S-1-5-32-549 (System Operators)
• *S-1-5-32-550 (Print Operators)

This behavior occurs because the accounts do not exist on the member computer and cannot be resolved. The SID still indicates that it is a built-in account that is resolved locally. These accounts are written back to the policy as SIDs and do not cause a problem.

The following 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, the following accounts are stored as the English equivalent if the computer and the 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 behavior is a limitation of the object picker.

Many of the accounts that have issues that are listed in this article are primarily used in the Default Domain Controller policy. We recommend that you change this policy only when you are working on a domain controller through Terminal Services and not when you are running MUI.

Other accounts have limited or no use in user rights assignment for domain members. We recommend that you use global groups or user accounts to grant user rights. These accounts do not have the problem when they are stored under their names.

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base: