Database Modeling has been used to change account properties during a migration. (NETIQKB3740)

  • 7703740
  • 02-Feb-2007
  • 07-Feb-2008

Resolution

fact
Domain Migration Administrator 7.1

cause
Database Modeling has been used to change account properties during a migration.

fix
You may have migrated some users using the database modeling feature while others were not modeled. This may be causing the difference in CN that you are seeing.  For more information on database modeling in DMA, please refer to Chapter 9 of the User Guide.

When you do not use database modeling, DMA sets the target account's CN equal to the source SamAccountName. When you select the migration wizard option 'Migrate data using data modeling as source?', DMA sets the target account's CN equal to the source Full Name. DMA will create accounts in this way even if you did not model the account, but chose to use modeling as a source.

Another possibility is that some users have been migrated using DMA, while other user accounts have been created using Active Directory Users and Computers. When DMA migrates users from NT 4 to Active Directory, it will use the user logon name (SamAccountName) to populate the Active Directory Display Name and CN. When a user is created in Active Directory using native tools, the Display Name is used for the Display Name and CN. Therefore, you may be seeing some accounts that were created using Active Directory Users and Computers along with the users that have been migrated.

Additional Information

Formerly known as NETIQKB3740