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 (906381)

SYMPTOMS

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:

DSA is unwilling to perform (53).

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.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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

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

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Ntdsa.dll	5.2.3790.393	1,532,928	20-Aug-2005	02:09	x86	None	RTMQFE
Ntdsatq.dll	5.2.3790.393	32,768	20-Aug-2005	02:09	x86	None	RTMQFE
Ws03res.dll	5.2.3790.393	59,392	19-Aug-2005	23:50	x86	None	RTMQFE
Ntdsa.dll	5.2.3790.2513	1,517,056	20-Aug-2005	02:26	x86	SP1	SP1QFE
Arpidfix.exe	5.2.3790.2513	32,256	20-Aug-2005	00:48	x86	None	Not Applicable

Windows Server 2003, 64-bit Itanium-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Ntdsa.dll	5.2.3790.393	4,058,112	19-Aug-2005	15:06	IA-64	None	RTMQFE
Ntdsatq.dll	5.2.3790.393	82,432	19-Aug-2005	15:06	IA-64	None	RTMQFE
Ws03res.dll	5.2.3790.393	58,880	19-Aug-2005	15:06	IA-64	None	RTMQFE
Wws03res.dll	5.2.3790.393	59,392	19-Aug-2005	15:06	x86	None	WOW
Ntdsa.dll	5.2.3790.2513	4,242,944	19-Aug-2005	15:06	IA-64	SP1	SP1QFE
Wntdsa.dll	5.2.3790.2513	1,517,056	19-Aug-2005	15:06	x86	SP1	WOW
Arpidfix.exe	5.2.3790.2513	74,752	19-Aug-2005	15:06	IA-64	None	Not Applicable

Windows Server 2003, 64-bit x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Ntdsa.dll	5.2.3790.2513	2,951,168	19-Aug-2005	15:06	x64	SP1	SP1QFE
Wntdsa.dll	5.2.3790.2513	1,517,056	19-Aug-2005	15:06	x86	SP1	WOW
Arpidfix.exe	5.2.3790.2513	43,008	19-Aug-2005	15:06	x64	None	Not Applicable

MORE INFORMATION

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:

Click Start, click Run, type Ldp in the Open box, and then click OK.
On the Connection menu, click Connect.
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.
Make sure that LDAP port 389 is specified in the Port box, and then click OK.
On the Connection menu, click Bind.
In the Bind dialog box, type the user name in the User box.
In the Password box, type the password.
In the Domain box, type the domain name, and then click OK.
On the Options menu, click General.
In the General Options dialog box, click Binary under Value Parsing, and then click OK.
On the View menu, click Tree.
In the Tree View dialog box, click OK.
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
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.
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»:..n0O¢
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
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:

Click Start, click Run, type Ldp in the Open box, and then click OK.
On the Connection menu, click Connect.
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.
Make sure that LDAP port 389 is specified in the Port box, and then click OK.
On the Connection menu, click Bind.
In the Bind dialog box, type the user name in the User box.
In the Password box, type the password.
In the Domain box, type the domain name, and then click OK.
On the View menu, click Tree.
In the Tree View dialog box, click OK.
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
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.
In the Modify dialog box, type member in the Attribute box.
In the Values box, type <GUID= b57d56ae3428a241bb3a0b026e308ca2>

Note The GUID value given here is copied from the notepad that you created earlier.
Click Enter, and then click Run.
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).
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:

824684 Description of the standard terminology that is used to describe Microsoft software updates

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:

http://www.microsoft.com/windowsxp/64bit/default.mspx

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

http://www.microsoft.com/windowsserver2003/64bit/x64/default.mspx