A security principal disappears from the Authorization Manager store of a Windows Server 2003-based trusted child domain after you close and then reopen Authorization Manager

Consider the following scenario:

• You assign a security principal from a parent domain to a role in the Authorization Manager (Azman.msc) store of a Microsoft Windows Server 2003-based trusted child domain.
• You close and then reopen Authorization Manager.

In this scenario, the security principal disappears from the Authorization Manager store.

Note A security principal can be a user, a group, or a computer.

Additionally, when you try to add new users to a user group by using their object GUID, you receive the following LDAP error message: This problem occurs when the following conditions are true:

• The group and the user account are in different domains.
• The domain controller to which we connect in the group's domain is not a global catalog server.
  
  Note There can be other domain controllers that are configured as global catalog servers in the same domain.
• The domain controller uses Windows Server 2003 Service Pack 1.

Service pack information

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

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

No prerequisites are required.

Restart requirement

You must restart the 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 item in Control Panel.

Windows Server 2003, 32-bit x86-based versions

Windows Server 2003, 64-bit Itanium-based versions

Windows Server 2003, 64-bit x64-based versions

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

Steps to reproduce the behavior

Note The steps provided in this section are to reproduce the scenario where you receive the LDAP error message.

Obtain the GUID of the user account from the child domain

To obtain the GUID of the user account, follow these steps:

1. Click Start, click Run, type Ldp in the Open box, and then click OK.
2. On the Connection menu, click Connect.
3. In the Connect dialog box, type ChildDC in the Server box.
   
   Note ChildDC is a placeholder that represents a domain controller in the child domain.
4. Make sure that LDAP port 389 is specified in the Port box, and then click OK.
5. On the Connection menu, click Bind.
6. In the Bind dialog box, type the user name in the User box.
7. In the Password box, type the password.
8. In the Domain box, type the domain name, and then click OK.
9. On the Options menu, click General.
10. In the General Options dialog box, click Binary under Value Parsing, and then click OK.
11. On the View menu, click Tree.
12. In the Tree View dialog box, click OK.
13. In the left pane, locate the container where test user account resides. For example, the container that contains the Test User may resemble the following:
    CN=Users,DC=child,DC=root,DC=local
14. Expand the container, and then double-click the user account. For example, the entry for the user account will resemble the following:
    CN=Test User,CN=Users,DC=child,DC=root,DC=local
    
    NoteTest User is a placeholder that represents the user account in the child domain.
    
15. In the right pane, locate the object GUID of the user account. For example, the object GUID of the user account may resemble the following:
    1> objectGUID: b5 7d 56 ae 34 28 a2 41 bb 3a 0b 02 6e 30 8c a2 µ}V®4(¢A»:..n0Œ¢
16. Open the Notepad program, copy the GUID to the notepad, and then remove the symbols that are not required from the GUID. For example, the GUID will resemble the following after you remove the symbols that are not required:
    b57d56ae3428a241bb3a0b026e308ca2
17. On the Connection menu, click Disconnect.

Use the GUID to add the user account to a user group on the root domain

To use the GUID to add a user account to a user group, follow these steps:

1. Click Start, click Run, type Ldp in the Open box, and then click OK.
2. On the Connection menu, click Connect.
3. In the Connect dialog box, type RootDC2 in the Server box.
   
   NoteRootDC2 is a placeholder that represents a domain controller in the root domain that is not a global catalog server.
4. Make sure that LDAP port 389 is specified in the Port box, and then click OK.
5. On the Connection menu, click Bind.
6. In the Bind dialog box, type the user name in the User box.
7. In the Password box, type the password.
8. In the Domain box, type the domain name, and then click OK.
9. On the View menu, click Tree.
10. In the Tree View dialog box, click OK.
11. In the left pane, locate the container where the Test Group resides. For example, the container that contains the Test Group may resemble the following:
    CN=Users,DC=child,DC=root,DC=local
12. Expand the container, locate and right-click the entry for Test Group, and then click Modify. For example, the entry for the Test Group will resemble the following:
    CN=Test Group,CN=Users,DC=child,DC=root,DC=local
    
    
    NoteTest Group is a placeholder that represents the user group in the root domain.
    
13. In the Modify dialog box, type member in the Attribute box.
14. In the Values box, type <GUID= b57d56ae3428a241bb3a0b026e308ca2>
    
    Note The GUID value given here is copied from the notepad that you created earlier.
15. Click Enter, and then click Run.
16. Click Close. You see the LDAP_UNWILLING_TO_PERFORM error message appear in the right pane and the user account is not added to the user group. Generally, the user account must be added to the user group regardless of the domain controller to which you connect.
    
    Note This problem will not occur if the domain controller is not using Windows Server 2003 Service Pack 1 (SP1).
17. On the Connection menu, click Disconnect.

For more information about the standard terminology that is to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

Technical support for x64-based versions of Microsoft Windows

Your hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your x64-based version of Windows. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site: