Target custom recipients are not being replaced when migrating mailboxes. (NETIQKB1383)

  • 7701383
  • 02-Feb-2007
  • 02-Nov-2007

Resolution

fact
Exchange Migrator 1.x

fact
Exchange Migrator 2.x

symptom
Target custom recipients are not being replaced when migrating mailboxes.

cause
If you have used the EMCLI DIRSYNC utility prior to migrating with Domain Migration Administrator (DMA) you will end up with two objects in the target Windows 2000 AD; one Mail object (Contact) and one AD user object. Both should in fact be one object together. When you migrate the mailbox it will merge based on the NT account, thus leaving an orphaned Contact.

fix

In order to avoid this problem you should complete your DMA migration first. Then use EMCLI DIRSYNC with the /merge switch. This will mail-enable the AD user object (basically making the AD account the Contact) so you will not have duplicate objects. When the mailbox is migrated with Exchange Migrator the mailbox will be merged with the mail-enabled AD user account, thus mailbox enabling the correct object.

The recommended order to migrate objects is (in an Inter-Org migration):

  1. Use EMCLI DIRSYNC to synchronize source and target GALs.
  2. Migrate Custom Recipients that you want brought over to the target.
  3. Migrate Distribution Lists.
  4. Migrate Public Folders.
  5. Migrate Mailboxes.
  6. After each batch of mailboxes has been migrated you need to run Synchronize and Update Migrated Mailboxes and Synchronize and Update Migrated Public Folders.

The recommended order to migrate objects is (in an Intra-Org migration):

  1. Migrate Custom Recipients that you want brought over to the target site.
  2. Migrate Distribution Lists.
  3. Migrate Mailboxes.
  4. In a site-to-site migration NetIQ does not support migrating Public Folders. If you wish to move the Public Folders use native tools to re-home them. After each batch of mailboxes has been migrated you need to run Synchronize and Update Migrated Mailboxes and apply permissions to Public Folders by right clicking the project and selecting Update Source Public Folder Permissions. Make sure the Public Folders and the newly migrated objects are fully replicated between all sites.

For further EM best practices please see:

NETIQKB2197: Best Practices for using Exchange Migrator



Additional Information

Formerly known as NETIQKB1383