Copyright
©1996, Que Corporation. All rights reserved. No part of this book
may be used or reproduced in any form or by any means, or stored in a database
or retrieval system without prior written permission of the publisher except
in the case of brief quotations embodied in critical articles and reviews.
Making copies of any part of this book for any purpose other than your
own personal use is a violation of United States copyright laws. For information,
address Que Corporation, 201 West 103rd Street, Indianapolis,
IN 46290 or at support@mcp .com.
Notice: This material is excerpted from Special Edition Using Microsoft Exchange Server, ISBN: 0-7897-0687-3. The electronic version of this material has not been through the final proof reading stage that the book goes through before being published in printed form. Some errors may exist here that are corrected before the book is published. This material is provided "as is" without any warranty of any kind.
Migration is the act of moving users from one messaging system to another. This can include mailboxes, mail, addresses, and schedule information from your existing system.
In the past, mail migration was not considered something for the "faint-footed." However, Microsoft Exchange is packed with migration features that support multiple scenarios for interconnecting to other Mail systems. Tools like Migration Wizard simplify the migration process and ensure a smooth transition to Microsoft Exchange.
In this chapter, you learn about the following:
Migration Strategy and Planning
Microsoft Exchange Server has many migration tools to be used with Microsoft Mail (PC). As you plan your migration you will need to consider the following:
Migration Levels: From Full Migration to Coexistence
There are three levels of migration: coexistence, mailbox creation, and mailbox migration. The type you choose depends on how much data you want to move from your existing system to Microsoft Exchange:
You can use one of these three migration levels exclusively, or you can use all three as part of your migration plan. For example, after you install your first new Exchange server, you can migrate addresses from MS Mail. For a test run, you can create new mailboxes without data. Once your testing is complete, you can migrate the mailbox contents to the new mailboxes and have the users upgrade their clients to Microsoft Exchange-based clients.
The following list describes issues associated with a migration from MS Mail to Exchange.
The following is a list of the types or levels of migration from MS Mail to Exchange. You should chose the proper phase for your organization.
Single-phase migration
Gives users some of the enhanced features before migration, while you are planning and testing the enterprise design.
Multi-phase migration
Gives all users a common user interface as you migrate mailboxes in stages.
Multi-phase migration with dual access
Enables users to retrieve mail from their old mailboxes after their mailboxes have been migrated to Microsoft Exchange Server.
Taking into consideration the previous two lists, you should be developing an idea of the migration strategy for your organization. As you plan your organizations' new messaging infrastructure, you'll probably want to break down the project into steps. The major steps of the migration process can be divided as follows:
Now that you are aware of the issues, phases, and steps to migrating MS mail to Exchange, keep in mind the affect of these items on your organization. The next section will take the previous lists and apply them to an actual organization.
Introduction to the Three-Phase Method
Large organizations might consider phased migrations, concentrating on more challenging sites prior to the major Exchange roll-out. There may also be longer periods of coexistence with legacy mail. Smaller organizations by contrast would most likely be able to do a very quick migration—almost instantaneous.
If you belong to a large organization, your migration plan will probably take place in three basic phases:
Sample Migration with a Three-Phase Method
A three-phased approach is used to simplify the task of migration. Inside of each phase may be numerous individual tasks. On a high level, these three phases will apply to any organization. The following sample will be used to walk you throught he migration process for an actual organization.
Digital Genesis has its headquarters in Los Angeles, and offices in Boston, MA and another Melbourne, Australia, see figure 7.1. The two American offices are connected over a T1 line. The headquarters and Australian office are connected over a wide area X.25 network that uses X.400 services.
Fig. 7.1
A sample migration—using the three-phase method.
Their e-mail system consists of four Microsoft Mail post offices: two in Los Angeles, one in Boston, and one in Melbourne. In this example, all the PCs are using the Microsoft Mail driver and the Microsoft Windows 95 operating system. This enables them to use the Microsoft Exchange client with their existing Microsoft Mail post offices.
Headquarters installs a Windows NT–based server with Microsoft Exchange Server on an existing Novell network. Then, using the built-in Migration tool, the company migrates its Microsoft Mail post offices at headquarters to Microsoft Exchange.
The Migration tool converts Microsoft Mail messages, Personal Address Book data, attachments, private folders, and meeting requests to the Microsoft Exchange format and creates new accounts on the Microsoft Exchange system. Microsoft Schedule+ 1.0 calendar files are automatically updated by the Microsoft Exchange group scheduling function. Because the X.400 gateway is integrated into Microsoft Exchange, this capacity is automatically installed with the initial setup.
At headquarters, they simultaneously start installing the Microsoft Exchange Server driver on each of the Windows 95–based workstations to access the Microsoft Exchange Server. Those still using the Mail 3.x driver can continue to communicate with other users of Microsoft Mail and Microsoft Exchange, but without the enhanced functionality provided by Microsoft Exchange. (See table 7.1 for a table comparison of Mail client versus Exchange client functionality.)
Installing Exchange Server consolidates the functions of three machines, the two Microsoft Mail post offices and the X.400 gateway, onto one machine. It also adds one stop administration, connection monitoring, and performance monitoring. Microsoft Exchange users can use Microsoft Mail 3.x gateways, and Microsoft Mail users can use the Microsoft Exchange gateways.
After the Microsoft Exchange driver is installed on all workstations, users in the L.A. office have access to the complete functionality of Microsoft Exchange, including:
Microsoft Exchange users in L.A. can continue to communicate with their counterparts in Boston and Melbourne. This enables the company to migrate in stages while still enabling all users to:
Table 7.1 Client Feature Comparison After Phases of Migration
| Feature | A | B | C |
| Rich text support | x | x | x |
| Auto reply | x | x | |
| Access to public folders | x | ||
| Flexible views | x | x | |
| Delegate access | x | ||
| Remote functionality | x | x | x |
| Rich searches | x | x | |
| Group Scheduling | x | x | x |
| Easy-to-use forms | x | x | x |
| Central forms registry | x | ||
| OLE 2.0 | x | x |
Next, the company installs Microsoft Exchange Server in the Los Angeles office, and combines existing users of the two Microsoft Mail post offices on that server.
The organization still uses MS Mail post offices at the remote locations. Using the Microsoft Exchange Server as an MTA between the Microsoft Exchange Servers and the MS Mail post offices offers different advantages:
Digital Genesis also installs Microsoft Exchange drivers on all PCs at headquarters to access the Microsoft Exchange Server. At the end of phase two, all users in L.A. and Boston have access to the complete functionality of the Microsoft Exchange system. They can also continue to exchange messages with users in Melbourne via the X.400 connector through a "pass-through gateway." Mail Connector manages the directory exchange between Microsoft Exchange and Microsoft Mail during this coexistence phase.
In the final migration phase, the Melbourne office installs NT Server and Microsoft Exchange on both the server and the workstations. This consolidates the Microsoft Mail 3.x post office and Mail gateway onto one server. Now, users across the enterprise have full use of Microsoft Exchange's rich functionality and are able to share information with everyone else in their organization, anytime.
The company has realized the cost savings of consolidating the functions of nine machines into three and have condensed the administration for all three offices onto one Windows NT–based workstation. They have a consistent enterprise-wide messaging and information exchange system with the features catalogued in the following list and can install additional Microsoft Exchange gateways to extend these capabilities beyond the enterprise:
Implementing Client Migration
The Microsoft Exchange Windows clients can be used as clients for Microsoft Mail (PC) post offices. This is done by adding the Microsoft Mail service provider to the profile. This can be done before migration or before and during phased migration to move users to the new client while retaining the post office infrastructure.
Even if only the clients are migrated to Exchange, they will enjoy all the benefits listed at the end of the previous section. With this strategy, all users will also have a consistent user interface.
To install Microsoft Exchange client, users need the Profile Wizard, included with the client setup software. The Profile Wizard pulls default information for connecting to the post office from the MSMAIL.INI file.
To use the MS Mail Post office, also called the MS Mail provider, you will need to make the Microsoft Mail (PC) provider the default for the client profile; for this you use the Setup Editor. The setup editor allows complete configuration of the Exchange client prior to installation on the user's pc. This is also true for installing the Microsoft Exchange provider.
After the client software is installed on the user's pc, the user then imports the contents of the Microsoft Mail Message File (MMF) file into the Exchange inbox format. If the MMF file is in the post office the user should first move the MMF to the local disk or a viewable network share before importing the contents. If the MMF file is left on the post office, the contents will be migrated to Microsoft Exchange when the mailbox is migrated.
Once a user begins using Microsoft Exchange client, there is no easy way to migrate the messages they receive to an MMF or mailbag file. He or she can copy the messages to a shared folder and then retrieve them with the old client, but this does not guarantee privacy of the messages.
When you migrate the user's mailbox to Microsoft Exchange Server, you have two options:
Implementing Server Migration
The Mail Server or Exchange Server is the "provider". A single provider option is full migration from one messaging server to another. A dual provider strategy is one in which both messaging systems coexist and two servers or providers are used.
Depending on the size of your organization and your human resources, you may be able to do a one-step migration. This can happen overnight, on a weekend, or on company shutdown time. If your organization can't tolerate the downtime or doesn't have the resources to migrate everyone in a weekend, phased migration is the best choice.
Instant migration may be better for your organization if:
Should you choose to go with a single mail provider, like Exchange Server, the single provider option provides for these scenarios:
Update the global address list and the directory. Mail sent to the old addresses from the personal address books and personal address lists will be returned as non-deliverable (if you delete the old mailbox) or pile up in the old mailbox.
With a multi-phase migration, you have two "providers," MS Mail Post office and Exchange server for instance. a Dual Provider provides for these scenarios:
The drawback of these options are that the profile must be edited three times: first when the client is installed, again when the Microsoft Exchange Server provider is added, and again when the Microsoft Mail (PC) provider is removed.
When configured for dual providers, the use of the MS Mail provider should be limited to retrieving mail for the old mailbox. Mail addressed with the MS Mail address book will be delivered and can be replied to. Choose the Reply to All option on mail messages addressed to both Microsoft Mail mailboxes (not as Microsoft Exchange custom recipients) and Microsoft Exchange mailboxes will fail to reach the Microsoft Exchange mailboxes.
If the message is sent to Microsoft Mail mailboxes as custom recipients, the client transfers the message to the Microsoft Exchange server. The Microsoft Exchange server updates the Microsoft Exchange mailbox addresses when it transfers the message to the MS Mail Connector so they can be replied to by Microsoft Mail recipients.
Now that we have discussed the one method for migration to Exchange, we will now discuss migrating the MMF files from MS Mail into the Exchange format. In addition, we will discuss issues associated with upgrading from Schedule+ v1.0 clients to Exchange Schedule+ v7.0 clients.
Microsoft Exchange client users must migrate their mail message files to a personal folder file. When MMF's are stored on a post office, you can use the MMFClean utility to manage their size and the age of messages (how long a message will be kept on file before it is automatically deleted). Personal folder files should not be stored on the post office.
The MMF Migration tool does not delete the MMF when it creates the personal folder file, move MMF files locally, or delete them after their contents are migrated to personal folder files.
Users that switch to the Microsoft Exchange client must also switch from Schedule+ 1.0 to Schedule+ 7.0. When they run Schedule+ 7.0 for the first time, it will migrate their CAL (Schedule+ 1.0 calendar format) file to SCD (Schedule+ 7.0 calendar format) file.
Schedule+ 7.0 can read CAL, POF (Schedule+ 1.0 post office free/busy times), and SCD files, but Schedule+ 1.0 can only read CAL and POF files. If your users make heavy use of Schedule+, switch everyone over to the new client at the same time. If some people switch to Schedule+ 7.0, the rest will not be able to view their calendars or act as their coworker's delegate.
Migrating everyone off of a postoffice at the same time is not always possible. Some users are waiting for hardware upgrades. The migration might be a pilot test or a limited rollout. When migrating partial postoffices, the following considerations are necessary:
No routing changes are required or allowed when doing a partial postoffice migration. The mailboxes remaining on the postoffice need mail addressed to them to continue to be delivered.
Part of your migration plan needs to include how many mailboxes at a time will migrate to Microsoft Exchange servers. As a general rule, migrating the whole post office (every mailbox) will be easier to plan for, implement, and maintain than migrating a partial post office. Migrating a partial post office is more likely to occur during a pilot or limited roll out, when the number of users is small and the issues are easier to solve or work around. The following section explains why this is so, and gives examples of each of these scenarios.
If you migrate every mailbox on a post office, you can maintain original Network/Post office/Mailbox Microsoft Mail address for each old mailbox as one of the proxy or e-mail addresses of the new mailbox. This has many advantages:
Retaining the original e-mail address provides for pass-through from Microsoft Mail (PC) gateways. The Microsoft Mail connector post office must have an access component for the gateway installed. Because the Microsoft Mail type addresses for migrated mailboxes have not changed, the mail will be routed from the gateway to the Microsoft Mail connector, and from there to the Microsoft Exchange mailbox.
Personal address book entries function similarly to replies. For Microsoft Mail (PC) users, their personal address book addresses continue to work for migrated mailboxes because the addresses are the same.
Migrated personal address book entries will work for Microsoft Mail (PC) mailboxes that have not migrated. This means that if you do not update your personal address book with the new Exchange email addresses, some email will still be directed to MS Mail mailboxes that no longer exist. Mail addressed with the migrated to mailboxes that have since migrated will get routed to the Microsoft Mail connector. The Microsoft Mail connector does not have a post office configured with that address and will return the mail as undeliverable. This undeliverable mail can be re-addressed from the Microsoft Exchange server global address list and be delivered normally.
There is no tool that updates the user's personal address book entries as changes are made in the Microsoft Exchange server global address list. To prevent undeliverable mail, users can remove all personal entries of the type, MS, from their personal address book after the entries are migrated to Microsoft Exchange mailboxes.
The Migration Package Elements
The following sections cover the main elements of Microsoft Exchange's Migration package. This package allows you to implement Exchange into environments with legacy mail systems. These tools assist with the extraction of email addresses from the legacy systems and import them into Exchange
There are several tools that assist with the migration from MS Mail to Exchange. These tools include the functionality to extract mailbox information from the legacy system. In addition, there is a server component called an Ms Mail "server" post office. This post office resides on the Exchange server and can only be accessed by the Exchange and Ms Mail MTAs.
There is a Source Extractor for every system such as MS Mail, PROFS, and the like. The Source Extractor extracts users, inboxes, folders, and address books from the source mail systems.
The following list are the components of the source extraction tool used to convert extracted addresses into the Exchange format and provide support information for the migration process. Other components include the directory agent to facilitate the dirsync process via the Exchange MS Mail server post office. Several other components include the free/busy connector to allow for group scheduling information and the passthrough connectivity to interconnect with Exchange.
The term Connector has taken the place of the Microsoft Mail Transfer Agent (MMTA) in MS Mail. The Connector is the main link between users of Exchange and Microsoft Mail (PC), as well as MS Mail gateways and Exchange gateways. There are three components to the Microsoft Mail Connector:
Together, these components make up the Mail Connector, allowing Microsoft Exchange users to transparently send and receive messages and files, meeting requests, and free/busy information with users on MS Mail.
The Directory Exchange Agent (DXA) in Microsoft Exchange enhances directory synchronization with flexible scheduling, better time zone management and update scheduling. Its multithreaded design improves throughput. Because the DXA includes multiple server support, the directory synchronization load is distributed across multiple "dirsync" servers for increased reliability and faster response. This reduces address list maintenance, increases security, and assures that updates occur more promptly.
The Microsoft Schedule+ Free and Busy Gateway enables users who remain on Schedule+ version 1.0 using MS Mail 3.x servers to see free/busy information in the planner view of users who are on the new release of Schedule+ on the Microsoft Exchange Server computer, and vice-versa. The data from each server platform is replicated across the connector to appear to users on the other platform.
Microsoft Exchange Server, offers hardy group distribution list support and enables MS Mail users to send messages to X.400 and SMTP environments through the Microsoft Mail Connector. Messages sent from the MS Mail 3.x users through the Microsoft Exchange Server computer can use the Microsoft Exchange X.400 Connector and the Internet Mail Connector to interchange messages with these environments. Alternatively, Microsoft Exchange users can send messages through any of the Microsoft Mail gateways, through the Microsoft Mail Connector.
Using the Migration Wizard
You can use the Migration Wizard to migrate one or more mailboxes on a Microsoft Mail for PC Networks post office. When each mailbox on the post office is migrated, you have a choice of what information to migrated.
The following is a list of available components to migrate into the Exchange environment. The list covers the components from the actual mailbox containing data to the schedule+ file and then the group or shared folders and the personal address book entries on a users' local pc.
Make sure there is no mail activity during migration.
The following preparations are recommended before migrating in order to ensure safe migration of data:
To create the user list from a Microsoft Mail (PC) post office:
1. (Optional) Map a drive letter or connect to a file server where the post office resides. You will need read and write access to the share or volume and have the name and password of the administrator.
2. In Program Manager, choose Microsoft Exchange.
3. In the Microsoft Exchange group, choose Microsoft Exchange Migration Wizard.
4. Select Migrate from Microsoft Mail for PC Networks, and choose the Next button.
5. Read the informational screen and choose the Next button.
6. In the Path to MS Mail Post office box, type the path to the post office.
or
7. Choose the Browse button to specify the path to the post office.
8. In the Account Name box, type the mailbox name of an administrator on the post office.
9. In the Password box, type the password for this mailbox and choose the Next button.
10. Select Two Step Migration and choose the Next button.
11. Select Extract a User List File and in the User List to Be Created box, type the path and file name of the new user list
or
12. Choose the Browse button to specify the path and file name.
13. Choose the Next button.
14. In the Select Which Accounts You Would Like to Migrate box, choose the mailboxes you want to migrate.
or
15. Choose the Select All button to select all mailboxes.
16. Choose the Next button to create the user list file.
You can make changes as needed in the user list file. If you need to change the directory name of a mailbox, do it before the mailbox is created. Other fields can be changed now in this text file, or later. To change them now, follow the process as outlined in the following paragraphs. To change them later, use the Administrator program to change them one at a time, or use the Directory Import command to change them in a batch mode.
To modify the user list file:
1. Make a backup copy of the user list file. You will need it later.
2. Open the user list file with a text editor.
3. Delete the first two lines that have post office information and save the file as text.
4. Open the modified user list file with a database program. The file is text, comma delimited, and the first row contains field names.
5. The fields in table 7.2 are in the user list. (The first two fields can't be changed, and the first six need to be kept in the same order.)
Table 7.2 User List Fields
| Field | Contents |
| SFS_UserName | The mailbox name or alias of this mailbox in the post office. Do not change this. |
| SFS_FullName | The full or display name of this mailbox in the post office. Do not change this. |
| MigrateUser | Should be "Y" if mailbox is to be migrated and "N" if the mailbox should not be migrated. |
| Obj-Class | This field should be "mailbox". Other valid values are "remote" for custom recipients and "dl" for distribution list. |
| Mode | Describes what should be done with this object—"create," "modify," and "delete" are valid options. The default is "create". |
| Common-Name | The directory name of the mailbox. This can't be changed later without deleting the mailbox and re-creating it, so change it now to match your naming convention. |
| Display-Name | The display or friendly name as seen in the address book. |
| Given-Name | The first or given name of the mailbox's user. |
| Surname | The surname or last name of a mailbox's user. |
| Home-Server | The home server of the mailbox. You can move a mailbox within the site later without difficulty, but you should decide where each group of mailboxes is to be created. |
| Comment | This is the address book comment. It can be used to distinguish between two people with the same or similar names, or for notes about contacts for Schedule+ resources. |
| Assoc Windows-NT Account | Each mailbox needs an associated Windows NT account that has user access. On a Schedule+ resource account this can be a Windows NT group or account that is responsible for managing the resource, or the administrator who is going to sign into the account once to set up forwarding rules and Schedule+ access permissions. |
*You can add additional directory import fields after Assoc-NT-Account.
1. After it is modified, export the file in CSV format.
2. Open the modified file and the backup file with a text editor. Copy the two lines from the backup file to the top of the modified file. Save the file as text.
After creating the user list and modifying it, you can migrate mailboxes from the post office to your site. This does not delete the mailboxes or remove mail, it only copies the information to the Microsoft Exchange servers where the new mailboxes are created.
To migrate mailboxes from a post office to a Microsoft Exchange server with a user list, follow these steps:
1. (Optional) Map a drive letter or connect to a file server where the post office resides. You will need read and write access to the share or volume and have the name and password of the administrator.
2. In Program Manager, choose Microsoft Exchange.
3. In the Microsoft Exchange group, choose Microsoft Exchange Migration Wizard.
4. Select Migrate from Microsoft Mail for PC Networks, and choose the Next button.
5. Read the informational screen and choose the Next button.
6. In the Path to MS Mail Post office box, type the path to the post office.
or
7. Choose the Browse button to specify the path to the post office.
8. In the Account Name box, type the mailbox name of an administrator on the post office.
9. In the Password box, type the password for this mailbox and choose the Next button.
10. Select Two Step Migration and choose the Next button.
11. Select Use a User List File to Do a Migration and in the Existing User List File box, type the path and file name of the modified user list.
or
12. Choose the Browse button to select the file.
13. Choose the Next button.
14. Select the import options based on your needs (see table 7.3).
Table 7.3 Import Options
| Option | Description |
| Information to Create Mailboxes | Create mailboxes for the selected users in the user list file. |
| Personal E-Mail Messages | Copy messages and folders from the selected users mailbox and server based MMF. You can select all messages or set a date range. |
| Shared Folders | Copy all shared folders to the public folder server of this server. |
| Personal Address Books | Copy PAB entries in the MMFs and put into the selected user's inbox in a special message. |
| Schedule Information | Copy calendar files from the CAL directory on the post office to a special message in the selected user's inbox. |
15. Choose the Next button.
16. In the Enter a Server Name box, type the name of the destination Microsoft Exchange Server computer. Choose the Next button.
17. Select the directory container for the new mailboxes.
You cannot move a mailbox from one directory container to another after the mailbox has been created.
18. If you are using a mailbox template to reduce the work of setting up new mailboxes, choose the Browse button and select the template mailbox from the address list.
19. Choose the Next button.
20. In For Users That Don't Have Windows NT Accounts, choose one of the options (see table 7.4).
Table 7.4 Options for Users Without NT Accounts
| Option | Description |
| Create Accounts and Generate Random Passwords | Accounts are created with names that match the alias and random passwords. The passwords are written to the file BIMPORT.PSW in the working directory of the Migration Wizard. For users to log on to Windows NT, distribute these passwords to them. |
| Create Accounts and Use Alias as Password | Accounts are created with names and passwords that match the alias. |
| Don't Create Windows NT Accounts | No accounts are created and the mailboxes can't be used by anyone until an account is assigned later. |
21. In the Choose a Windows NT Domain for New Accounts box, select the domain where the user's Windows NT accounts are located or to be created.
22. Choose the Next button to begin the migration process.
To migrate in one step from a Microsoft Mail (PC) post office, follow these steps:
1. (Optional) Map a drive letter or connect to a file server where the post office resides. You will need read and write access to the share or volume and have the name and password of the administrator.
2. In Program Manager, choose Microsoft Exchange.
3. In the Microsoft Exchange group, choose Microsoft Exchange Migration Wizard.
4. Select Migrate from MS Mail for PC Networks, and choose the Next button.
5. Read the informational screen and choose the Next button.
6. In the Path to MS Mail Post office box, type the path to the post office.
or
7. Choose the Browse button to specify the path to the post office.
8. In the Account Name box, type the mailbox name of an administrator on the post office.
9. In the Password box, type the password for this mailbox and choose the Next button.
10. Select the One Step Migration option, and choose the Next button.
11. Select the options based on your needs (see table 7.5).
Table 7.5 One Step Migration Options
| Option | Description |
| Information to Create Mailboxes | Creates mailboxes for the selected users in the user list file. |
| Personal E-Mail Messages | Copies all messages and folders from the selected users mailbox and server-based MMF. You can select all or set a date range. |
| Shared Folders | Select this check box to copy all shared folders to the public folder server of this server. |
| Personal Address Books | When selected, PAB entries in MMFs are copied and put into the selected user's inbox in a special message. |
| Schedule Information | Calendar files are copied from the CAL directory on the post office to a special message in the selected user's inbox. |
12. Choose the Next button.
13. In the Select Which Accounts You Would Like to Migrate box, choose the mailboxes you want to migrate.
or
14. Choose the Select All button to select all mailboxes.
15. Choose the Next button.
16. In the Enter a Server Name box, type the name of the destination Microsoft Exchange Server computer. Choose the Next button.
17. Select the directory container for the new mailboxes.
You cannot move a mailbox from one directory container to another after the mailbox has been created.
18. Choose the Next button.
19. Choose one of the options in For Users That Don't Have Windows NT Accounts (see table 7.6).
Table 7.6 One Step Migration, Options for Users with No NT Accounts
| Option | Description |
| Create Accounts and Generate Random Passwords | Accounts are created with names that match the alias and random passwords. The passwords are written to the file BIMPORT.PSW in the working directory of the Migration Wizard. For users to log on to Windows NT, you need to distribute these passwords to them. |
| Create Accounts and Use Alias as Password | Accounts are created with names and passwords that match the alias. |
| Don't Create Windows NT Accounts | No accounts are created and the mailboxes can't be used by anyone until an account is assigned later. |
20. In the Choose a Windows NT Domain for New Accounts box, select the domain where the user's Windows NT accounts are located or to be created.
21. Choose the Next button to begin the migration process.
As explained earlier in the migration tools section of this chapter, MMFs can be migrated by the user to personal folder files, or by the Administrator to the private information store, depending on the location of the MMFs. There are a few things to note about MMF migration:
If there is a network failure during MMF migration, the client or Migration Wizard retries the network connection every ten minutes to re-establish a connection. An error message is displayed during this retry time.
Any errors during client MMF migration are logged to a file in the client directory with a file name the same as the MMF name and an extension of .LOG. You can view them in notepad or any other text editor.
To import an MMF file with the Windows NT or Windows 16 client, follow these steps:
1. From the File menu, choose Import.
2. In the Specify File to Import window, select the MMF file.
3. In the Import Mail Data window, type the password for this MMF file.
4. Select the Import Messages check box to import all messages and folders.
5. Select the Import Personal Address Book Entries check box to create a Microsoft Exchange PAB file.
6. Choose OK.
Depending on your migration strategy, you will need to delete the Microsoft Mail (PC) mailboxes or hide the post office. It is possible to make a full backup of the updated information store.
From Here...
Exchange's Migration tools, will give you powerful interoperability with existing MS-Mail systems. After planning the steps and phases to migration, administrators, with the help of tools like Migration Wizard, can create a smooth transition to Exchange, so they and their users can sooner get down to the business of information exchange.
For technical support for our books and software contact support@mcp.com
Copyright ©1996, Que Corporation