Resolution
fact
Exchange Migrator 1.x
fact
Exchange Migrator 2.x
symptom
Exchange Migrator (EM) overwrites the pre-Windows 2000 user logon name (SAMAccountName) with the 5.5 alias.
cause
If there is an existing NT account in the Microsoft Active Directory that a mailbox will collide/merge on and a Domain Migration Administator Mapping (i.e. protar.mdb) has not been imported, Exchange Migrator will overwrite the SAMAccountName (pre-Windows 2000 logon name) with the source Exchange 5.5 mailbox's alias name.
fix
Exchange Migrator 1.x
fact
Exchange Migrator 2.x
symptom
Exchange Migrator (EM) overwrites the pre-Windows 2000 user logon name (SAMAccountName) with the 5.5 alias.
cause
If there is an existing NT account in the Microsoft Active Directory that a mailbox will collide/merge on and a Domain Migration Administator Mapping (i.e. protar.mdb) has not been imported, Exchange Migrator will overwrite the SAMAccountName (pre-Windows 2000 logon name) with the source Exchange 5.5 mailbox's alias name.
fix
This issue is resolved in Exchange Migrator 2.21 Hotfix027949. EM 2.21 Hotfix027949 can be downloaded from the following link:
For versions of Exchange Migrator prior to EM 2.21 Hotfix027949, use one of the following options:
- Create a script to use in conjuction with an Exchange Migrator mailbox post task event.
- Import the protar database from Domain Migration Administrator into Exchange Migrator.
- Please see NETIQKB1886 : How do I import a mapping file (Protar.mdb) from a DMA migration into Exchange Migrator
Additional Information
Formerly known as NETIQKB3213