Microsoft KB Archive/328743

= XFOR: Best Practices for Using Exchange Migration Wizard to Migrate from Novell =

PSS ID Number: 328743

Article Last Modified on 11/7/2003

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-



This article was previously published under Q328743



SUMMARY
Exchange Server Migration Wizard is the primary tool for migrating mailbox data from Novell GroupWise to Exchange 2000. The Migration Wizard is available in the Exchange Server Administrator program. This article describes several best practices that were developed by Microsoft Consulting Services for using the Migration Wizard.



MORE INFORMATION
While you export data from your existing system, a set of migration files (a packing list file and primary and secondary files) is created. These files are imported into Microsoft Exchange Server by the Migration Wizard. You can also use the Migration Wizard to create mailboxes and addresses.

The GroupWise Migration Account
On the GroupWise Domain page, where you specify the location and security of the Novell GroupWise domain you are migrating from, the Migration Wizard prompts you for the path of the GroupWise domain, user account name, and password. The password is the GroupWise password, not the Novell Directory Services (NDS) password.

Microsoft Consulting Services recommends that you create a GroupWise account early in the migration process for the purpose of migration. This is the account that you have to type. The migration account must meet the following criteria:
 * The account that you type on the GroupWise Domain page must have complete access to the GroupWise domain and the post office in that domain that contains the users whom you want to migrate. Additionally, migration complications are significantly reduced if the GroupWise migration account also has read and write access to all files in the post office and proxy rights to every mailbox in the post office.
 * The GroupWise migration account must be in the same post office as the users you want to migrate.

In most GroupWise organizations, it is unlikely that every post office contains an account that meets both of these criteria. To simplify this step, create designated migration accounts.

GroupWise Migration Account Must Be Local to Migrating Post Office
As mentioned earlier, the GroupWise migration account (or any account that you type on the GroupWise Domain page) must be in the same GroupWise post office as the accounts that you plan to migrate. Being in the same GroupWise domain is not enough. Therefore, regardless of the number of GroupWise domains that you have in your organization, if you have multiple post offices, you must create a migration account for every post office.

Pointing Migration Wizard to Primary GroupWise Domain May Not Be Enough
The GroupWise Domain page is also where you type the path to the GroupWise domain that contains the users you want to migrate. To make sure that the migration is successful, the Migration Wizard has to point to the GroupWise domain that contains the post offices with the users whom you plan to migrate. Even if the Migration Wizard is set to point to the primary GroupWise domain, the Migration Wizard cannot see the post offices in secondary GroupWise domains. Therefore, in a multiple-domain GroupWise environment, type the domain that contains the post office containing the users whom you want to migrate, not any parent domains.