Rename Objects During Migration
Updated: September 29, 2013
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)
In the Active Directory Migration Tool (ADMT), you can use an include file to rename user and group objects in the source domain so that they get a new name after they are migrated to the target domain.
You cannot rename computers that run Windows 7 or later during the migration. Those computers can be renamed as needed after the migration by using a script or Windows PowerShell. For more information, see Rename-Computer.
For more information about how to use an include file during a migration, see Use an Include File.
Use the following format in an include file to rename computer, user, or group objects during migration.
To rename objects using an include file
- Use SourceName, TargetRDN, TargetSAM, and TargetUPN as column headings at the top of the include file. SourceName is the name of the source account, and it must be listed as the first column heading.
If the target user principal name (UPN) for a user requires you to specify a domain name that is different from the target domain UPN, use this format to ensure that the user name is preserved and not altered by ADMT during migration.
You must specify the account name as user name, relative distinguished name, or canonical name. If you specify the account name as a relative distinguished name, you must also specify the source organizational unit (OU).
The TargetRDN, TargetSAM, and TargetUPN column headings are optional, and you can list them in any order.
The TargetUPN column heading is only relevant during user account migrations because group and computer accounts do not have a UPN.
The following are examples of valid include files in which the rename option is used:
This include file entry changes the TargetSam account name for user "abc" to "def." The TargetRDN and the TargetUPN, which you did not specify in the include file, does not change as a result of the migration.
This include file entry changes the TargetRDN for user abc to CN=def and the TargetUPN to email@example.com. The TargetSAM for user abc does not change as a result of the migration.
You must specify CN= before you use an RDN value.