ADMT Version 2 Does Not Migrate a Computer If an Account with an Identical NetBIOS Name Exists (316073)



The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition

This article was previously published under Q316073

SYMPTOMS

If you use the Active Directory Migration Tool (ADMT) version 2 to migrate a computer account from one Windows 2000-based domain to another, the migration may not succeed and an "Access Denied" message may be returned when you dispatch a migration agent to the computer. This behavior can occur if a computer account with the same NetBIOS name already exists in the target domain. This is often the result of a computer having been migrated previously and then manually rejoined to the source domain.

CAUSE

When ADMT version 2 is running in the target domain, it passes the NetBIOS name instead of the DNS name for the computer accounts that are to be migrated. Therefore, an invalid Kerberos service ticket that cannot be interpreted by the computer that is being migrated may be constructed. This issue can occur whether or not you specify the Replace conflicting accounts option.

WORKAROUND

To work around this issue, delete the identical machine accounts in the target domain.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

The error code that is returned by this condition is AP_ERR_MODIFIED. If the machine account in the target domain has been disabled, the error code is STATUS_ACCOUNT_DISABLED.

The Dispatch.log file that is created contains entries that are similar to:
2002-01-09 13:31:18 ERR2:7037 You do not have administrator privileges on \\ADMTW2K-WS1. The agent will not be installed.
2002-01-09 13:31:18 ERR2:7005 Failed to launch agent on \\ADMTW2K-WS1, hr=80070005 Access is denied.

Modification Type:MajorLast Reviewed:6/5/2003
Keywords:kbbug kbfix KB316073