Migrating to Exchange

MS Mail for PC Networks Migration

Migration Wizard supports migrating from Microsoft Mail for PC Networks version 3.x.

Note   You can migrate users from Microsoft Mail for AppleTalk Networks using the source extractor in the Migrate\Macmail folder of the Exchange compact disc; however, this utility is not supported by Microsoft Product Support Services.

You can migrate your system in several phases. Any multi-phase migration plan should include a plan for coexistence between the two systems. You can use Microsoft Mail Connector for PC Networks to provide messaging connectivity and directory synchronization, and you can use Microsoft Schedule+ Free/Busy Connector to provide calendar querying during the migration period. Directory synchronization generates contacts in Active Directory for Microsoft Mail users who haven't been migrated. Any messages addressed to a contact are delivered to the user in the Microsoft Mail system.

Migrating Partial or Full Postoffices

Generally, it is best to migrate the entire postoffice (every mailbox) because it is easier to plan for, implement, and maintain than migrating a partial postoffice.

If you migrate every mailbox in a postoffice at the same time, you can retain the original Microsoft Mail 10/10/10 (Network/Postoffice/Mailbox) addresses as MS type e-mail addresses. This has the following advantages:

This section contains the following topics:

Migrating from Additional Language Versions of MS Mail

MS Mail migration supports more than the six languages (French, German, Italian, Spanish, Japanese, and English) that Exchange is translated into. To migrate from MS Mail postoffice in languages other than the ones supported by Exchange 2000, you must have the appropriate language version of msfs32.dll in your winnt\system32 directory. Additional language versions of msfs32.dll reside in the migrate\msmail directory, located on the Exchange 2000 Server compact disc.

To migrate from additional language versions of MS Mail:

  1. Temporarily rename the existing msfs32.dll file on your server in the winnt\system32 directory to something similar to msfs32.tem.
  2. Manually copy the msfs32.dll file for the appropriate language from the migrate\msmail directory, located on the Exchange CD, to the winnt\system32 directory on your server.
  3. After performing migration, delete the msfs32.dll file from the winnt\system32 directory on your server.
  4. Rename the temporary file msfs32.tem to msfs32.dll in the winnt\system32 directory on your server.

Related Topics

Migrate from Microsoft Mail for PC Networks Upgrade to the Microsoft Outlook Client