Exchange Migrator 1.x
Exchange Migrator 2.x
EMProfileUpdate is not redirecting MAPI profiles correctly.
When logging in to their mailbox for the first time after migration, the end user is prompted to the Check Name button to resolve their new Exchange server name for their MAPI profile. Clicking Check Name resolves the mailbox, but the user may or may not be able to logon to the mailbox.
The migrated user cannot log on.
The Exchange server in the MAPI profile has not been changed to the target Exchange server.
Mailbox rights on the target mailbox are migrated inconsistently.
Thee known causes are:
- Manually modifying the exported tab file.
- Moving objects to a different OU prior to using the EMProfileUpdate utility.
- Migrating the end-user workstation to the target domain without translating security on local user profiles with Domain Migration Administrator, or third party product, before running EMProfileUpdate .
- Exporting an empty (zero KB) tab file with the Export Migrated Objects option.
To resolve the issue:
- Export a new tab file for the project and do not make manual edits.
- Do not move mailboxes to a different OU prior to using the EMProfileUpdate utility.
- Translate security for local user profiles on the computer with Domain Migration Administrator, or a third party product, then export the EMAMappings.tab file again.
- Run EMProfileUpdate with the
-reprocessswitch. For more information about the
-reprocessswitch, see the following Knowledge Base article NETIQKB27739: "How do I manipulate EMProfileUpdate to run against MAPI profiles that have previously been updated by EMProfileUpdate?"
- When you use the Export Migrated Objects option, ensure both the source and target Exchange Servers are available, otherwise, the exported tab file will be empty (zero KB).
- Add or remove the migrated source account to the mailbox rights, as needed.