Troubleshooting Computer Migration Issues
Applies To: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
Applies to: Active Directory Migration Tool 3.2 (ADMT 3.2)
This topic describes known issues related to migrating computers with the Active Directory Migration Tool (ADMT).
Intraforest computer migration does not disable the computer account in the source domain
After an intraforest computer migration, the migrated computer account in the source domain is neither disabled nor deleted. This is by design.
To disable or delete the accounts of migrated computers in the source domain, write a simple Active Directory Service Interfaces (ADSI) script.
Computer account is created even if migration fails
If a computer migration fails as the result of an agent-related error, the computer account that is created for the computer in the target domain is not deleted.
Note
If you select Migrate and merge conflicting objects on the Conflict Management page of the Computer Account Migration Wizard, you do not have to delete the computer account that was created in the target domain before you attempt to migrate the computer again.
Migrate computers before any groups in an intraforest migration
When you perform an intraforest migration, if you have any computers that are members of groups (other than the Domain Computers group), you must migrate those computers before you migrate the groups to which they belong. This is a condition for intraforest migrations, and it prevents those computers from losing their group membership.
Intermittent failure of ADMT remote agent service
If a failure occurs when you deploy the ADMT remote agent service on a remote computer as part of a computer migration, security translation, service account identification, or account reference report, it is possible that the agent might fail to stop or uninstall itself. If this occurs, you receive the message “An instance of the agent is already running” with each subsequent agent deployment until either the ADMT agent process is closed or the remote computer is rebooted.
Computer migration may fail if a computer account with the same NetBios name already exists in the target domain
When you migrate a computer back and forth between two domains, the agent dispatch might fail if a computer account with the same NetBIOS name as the computer that is being migrated from the source domain already exists in the target domain.
ADMT could not change the domain affiliation of a particular computer. This failure caused the computer to lose affiliation with any domain.
Cause: This can be caused by an incorrect migration environment configuration or some malfunction with either the source computer or target computer.
Solution: Join the computer to a domain and create the computer account in the domain as described in the following procedures.
To join a domain, you must enter credentials of an account with administrative permissions on the domain that you want the computer to join. You must restart the computer to complete the joining of the computer to the domain.
To change the domain membership of a computer
Log on to the computer that is using an account with local administrator credentials.
Click Start, right-click Computer, and then click Properties.
Click Change settings.
On the Computer Name tab, click Change.
In Computer Name Changes, select Domain, and then type the name of the domain that you want the computer to join. Click OK, and when you are prompted to restart the computer, click OK again.