Resolution
Can I use data modeling to change the samAccountName when remigrating the accounts?
fact
Domain Migration Administrator 7.x
fix
The samAccountName is the only property that you should not model after the accounts have already been migrated. Domain Migration Administrator (DMA) would create new accounts when the samAccountName was modeled for existing users. The reason this happens is that DMA uses the samAccountName to determine if an account in the target already exists. If the samAccountNames match, DMA will follow the settings that were chosen in the Naming Conflicts dialog box. If they do not match, DMA will create a new account.
The best option is to make the changes outside of DMA and run the Refresh Migrated Objects report to update the database with the changes so that future translations will not be affected by account name changes.
note
Please note that if you migrate a user, use modeling to change the Full Name and samacctname, and migrate that user again. DMA will create a new user as explained above. When you look at the migration.log, it might appear as if the accounts that were created have the same name, but they do not. Without modeling, DMA logs the samacctname. With modeling, DMA will log the Obj Name in an NT to NT migration scenario or the CN in an NT to W2K migration.
note
For more information regarding the Refresh Migrated Objects report, please refer to the following Knowledge Base article:
What is the 'Refresh Migrated Objects' report?
https://www.netiq.com/kb/esupport/consumer/esupport.asp?id=NETIQKB1149