Article ID: 929493 - Last Review: October 11, 2007 - Revision: 1.2

Error message when you use ADMT version 3 to migrate computer accounts from one Windows Server 2003 domain to another: “ERR3:7075 Failed to change domain affiliation”

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

SYMPTOMS

When you use Active Directory Migration Tool (ADMT) version 3 to migrate computer accounts from one Microsoft Windows Server 2003 domain to another, one or more of the following error messages are logged in the ADMT migration log:

Error message 1

ERR3:7075 Failed to change domain affiliation, hr=800706fb The security database on the server does not have a computer account for this workstation trust relationship.

Error message 2

DateTime ERR2:7625 Unable to connect to \\Computer.Domain.local\ADMIN$ The machine might be down or its Server, Netlogon service might not be started. rc=1722 The RPC server is unavailable.
DateTime ERR2:7014 The Active Directory Migration Tool Agent Service on \\<Computer>.<Domain>.local did not start. See the application log on \\<Computer>.<Domain>.local for details.

Error message 3

DateTime WRN1:7372 ADMT does not process BUILTIN accounts or change the membership of BUILTIN groups (Administrators, etc.). Skipping Domain Users 2006-04-07 08:47:49 ERR2:7228 Error updating user rights for CN=TSMITH, rc=-2147023162 The array bounds are invalid. DateTime Operation completed.

Back to the top

CAUSE

This problem occurs if one of the following conditions is true:

The ADMT agent on a client computer cannot locate the domain controller on which the computer account was created.
The Domain Name System (DNS) server names on a client computer are fixed. Therefore, these names are not retrieved from a Dynamic Host Configuration Protocol (DHCP) server. The DNS settings point to external DNS servers.
A firewall program is running on a client computer.

Back to the top

RESOLUTION

To resolve this problem, use one or more of the following methods until the problem is resolved.

Back to the top

Method 1

Troubleshoot all network problems, and then make sure that the ADMT agent on the client computer can connect to the domain controller on which the computer account was created.

For more information about how to troubleshoot network connectivity problems, click the following article number to view the article in the Microsoft Knowledge Base:

325487 (http://support.microsoft.com/kb/325487/ ) How to troubleshoot network connectivity problems

Alternatively, migrate computer accounts to a domain controller to which the ADMT agent can connect.

Back to the top

Method 2

Configure DNS settings on the client computer to retrieve DNS server names from a DHCP server.

Back to the top

Method 3

Disable all firewall programs that are running on the client computer.

Back to the top

Method 4

Make sure that you can connect to the source and target domain controllers from the client computer by typing the following command:

ping fully qualified domain name

Back to the top

Method 5

If the previous methods do not resolve the problem, follow these steps:

Use an account that has administrator credentials to log on to the client computer.
Click Start, point to Settings, and then click Control Panel.
Double-click Network Connections, right-click the connection that you want, and then click Properties.
On the General tab, click Client for Microsoft Networks, and then click Uninstall.
Restart the computer.
Click Start, point to Settings, and then click Control Panel.
Double-click Network Connections, right-click the connection that you want, and then click Properties.
On the General tab, click Install, click Client in the Select Network Component Type dialog box, and then click Add.
In the Network Client list, click Client for Microsoft Networks, and then click OK two times.
Restart the computer.