3.2.1 Obtaining Exchange Login Credentials

The Migration Utility needs to run with administrator rights so that it can access all mailboxes on each Exchange server. The workstation where you run the Migration Utility must have a username and password identical to a username and password on each Exchange server. The most straightforward way to provide the proper access is to not use the default administrator users, but to create corresponding pairs of administrator users for the Migration Utility workstation and each Exchange server.

For example, on the first Exchange server that you plan to migrate, you might create an account and mailbox named administrator1 and a corresponding administrator1 account on the Migration Utility workstation. On the second Exchange server, you might create an account and mailbox named administrator2 and a corresponding administrator2 account on the Migration Utility workstation. Each Exchange server needs a unique administrator account and mailbox so that the Exchange Utility can access each Exchange server with the necessary rights.

3.2.2 Creating the Exchange Data File

In order to list the Exchange users, distribution lists/groups, and public folders on the Exchange server, the Migration Utility generates a CSV (comma-separated value) file containing that information. If you plan multiple migration sessions for a server, the utility keeps track of what you have already migrated so that the lists it displays accurately reflect what still needs to be migrated.

By default, the file is named exmigdata.csv and is created in the directory where the Migration Utility software is installed. You can change the name and location as needed.

During the first migration session for an Exchange server, the CSV file contains a complete list of users, distribution lists/groups, and public folders. For a server with a large quantity of data to migrate, you can manually edit the CSV file and divide the data up into multiple smaller CSV files. These subset CSV files can be used on other workstations to simultaneously run multiple migration sessions for the Exchange server.

3.2.3 Locating a GroupWise Domain Directory

A GroupWise domain database (wpdomain.db) provides all the information the Migration Utility needs about your GroupWise system. Specifically, it enables the Migration Utility to list all of the post offices in your GroupWise system. The information can be obtained from any domain database. Make sure you know a network username and password with sufficient rights to map a drive and access a domain directory.

3.2.4 Planning Post Office Contents

All the Exchange users, distribution lists/groups, and public folders on the Exchange server must be assigned to one or more GroupWise post offices. Taking into account the information you gathered when you surveyed your Exchange servers for number of users, distribution lists/groups, and public folders, consider where you want to migrate the Exchange data from this server. Make a plan that includes all the data from the server, even if you are planning multiple migration sessions for this server.

3.2.5 Selecting Migration Options

The Migration Utility provides options for whether or not certain types of mailbox items are migrated. By default, deleted items, sent items, journal items, and draft items are not migrated.

If you migrate journal items, they are placed in a folder in the GroupWise mailbox. GroupWise does not have the equivalent of the Journal feature, so the items are for reference only and no more journal items can be created. If you migrate draft items, they are placed in the GroupWise Work in Progress folder. You can also restrict migrated items by age.

3.2.6 Selecting a User ID Conversion Rule

Exchange user IDs can include periods (.) but GroupWise user IDs cannot. If you have Exchange user IDs that contain periods, they must be renamed before they can be migrated to GroupWise. There are three alternative formats offered by the Migration Utility:

If desired, you can manually rename the Exchange user IDs that contain periods using a convention of your own choice.

Although the Migration Utility must change the user ID to conform to the GroupWise user ID convention, this does not affect the user’s e-mail address. Periods in e-mail addresses are permitted. E-mail addresses are retained just as they were in Exchange.

3.2.7 Planning Public Folder Conversion and Ownership

Exchange public folders are converted into standard GroupWise folders in the mailboxes of GroupWise resources. All users are granted proxy access to the resource mailboxes so that they can access the contents of the folders. Before migrating your Exchange public folders, you should assess their contents. You might not need to migrate all of them.

GroupWise resources that store the folders must be owned by users. You might find it convenient to own the resources yourself or you can choose different owners.

3.2.8 Planning eDirectory Contexts for GroupWise Objects

GroupWise users require eDirectory User objects. GroupWise distribution lists require Distribution List objects. GroupWise resources that store folders require Resource objects. Objects exist in eDirectory contexts. You must create the eDirectory contexts before you perform the migration.

In Section 3.1.4, Planning eDirectory Object Organization, you planned all of the eDirectory contexts that are required for your entire GroupWise system. Now you need to determine the contexts into which you want to migrate the Exchange data from this Exchange server.

3.2.9 Selecting Users to Migrate

If you are planning more than one migration session for the current Exchange server, decide which users you want to migrate during the current migration session. The Migration Utility provides the number of items in each user’s mailbox, which is indicative of the size of each mailbox, so you can adjust your list as needed while performing the migration.

It is not necessary to prepopulate eDirectory with User objects for the Exchange users who are being migrated. The Migration Utility takes care of creating the necessary User objects.

3.2.10 Selecting Public Folders to Migrate

If you are planning more than one migration session for the current Exchange server, decide which public folders you want to migrate during the current migration session. The Migration Utility will provide the number of items in each folder, which is indicative of the size of each folder, so you can adjust your list as needed while performing the migration.

3.2.11 Notifying Migrated Users

By default, the Migration Utility sends out notification messages to users that have been migrated. The messages are sent to users’ Exchange mailboxes. Each message includes the user’s GroupWise user ID, password, and server address. The default notification message is:

Exchange migration status

Your Exchange account has been successfully migrated to GroupWise. A GroupWise account has been created. Your username is %USERID% and your password is %PASSWORD%. Your GroupWise server address is %SERVER%:%PORT%.

Each user’s personal information is inserted into the variables when the notification messages are sent. You can use the default message or compose your own.

By default, copies of the notification messages are sent to the Administrator user in the Exchange system as a record of each user’s personal information. This information is also available in the CSV file that the Migration Utility uses during the migration.