Migrator for GroupWise 4.7.1 - Scenarios Guide

Step 1: Install and configure your target Exchange environment

If you have not yet installed and configured your Exchange destination environment, do it now. Provisioning of Active Directory, if necessary, will occur later in this procedure.

Step 2: Verify that all system requirements are satisfied

All of the system requirements, including the necessary admin accounts and access privileges (see System Requirements in the Migrator for GroupWise Quick Start Guide) must be satisfied before you begin this process.

IMPORTANT: Remember that the Migrator for GroupWise migration profile on the admin workstation must not be configured for cached mode.

Step 3: Install and configure Migrator for GroupWise

Complete installation instructions are available in the Getting Started section of the Migrator for GroupWise Quick Start Guide, which is included with the product download and also is available on the Quest website.

It is also important to consider whether Migrator for GroupWise’s Self Service Desktop Migrator (SSDM) component will be used as part of the migration strategy. If so, it should also be installed and configured.

NOTE: This substep applies only if your target AD is configured for a resource forest and a user forest, with corresponding user accounts.

For the Admin-Driven Batch Migrator to properly enable mailboxes, and to properly associate the resource accounts with the user accounts, you must configure parameters in gwmigapp.ini, and prepare (or verify) the per-user values in a column of the exported directory data. These preparations are necessary for the Batch Migrator to properly associate the resource accounts with the user accounts and properly enable mailboxes.

Before you begin, you must determine which column in the UsersToMigrate.csv file will correspond to which AD attribute, for the program to match corresponding user accounts in the resource forest and user forest. The column (AdSearchCol) and attribute (AdAttribute) are both specified in the [ActiveDirectory2] section of the gwmigapp.ini file.

IMPORTANT: In the current Migrator for GroupWise version, this AdSearchCol parameter value must be set to SearchKey2 for the mailbox-enabling process to succeed. The parameter default is AdSearchCol=SearchKey2.

For example:

... tells the program to match AD objects with users such that the value of each AD object's userPrincipalName attribute matches the value of the corresponding user's SearchKey2 column in UsersToMigrate.csv.

Configure these program parameters now, as part of this Migrator for GroupWise installation and configuration step. In the [ActiveDirectory2] section of the gwmigapp.ini file, set the appropriate parameter value for AdAttribute, as described above.

Use Microsoft Excel (or another other csv-editing program) to enter or edit the contents of the column you designated as the AdSearchCol column.

MFG supports unambiguous GroupWise-to-Exchange mail forwarding for two users sharing the same name and Object ID, but residing in different Post Offices and different domains. This feature associates a particular Post Office/domain (in GroupWise) with its corresponding IPaddress:port. You can then configure as many of these associations as necessary to define a unique IPaddress:port for each GW Post Office/domain.

The associations are defined by parameters entered into the [GroupWise] section of gwmigapp.ini. For example, if:

... then you could define:

These settings would forward the mail for each John Doe (and any other user pairs sharing the same name and Object ID) to the appropriate target address in Exchange.

Step 4 (for proxy access only): prepare the AddProxy program to establish user proxies

NOTE: This step applies only if you want the Admin-Driven Batch Migrator to access user source data by proxy. If the program will access source data by password, or as a Trusted App, skip ahead to the next step.

For versions of GroupWise 6.5.x or higher, Migrator for GroupWise automatically establishes itself as a trusted application through the Trusted Application API. This feature is typically used for accessing the source mailboxes. If instead you require or prefer proxy access, Migrator for GroupWise includes a utility to automate the proxy configuration within GroupWise.

In that case, prepare Quest AddProxy program to establish proxy access to each user’s account, and modify the network login script of your migrating users to run the AddProxy program when they next login. For complete instructions see the AddProxy Utility chapter in the Migrator for GroupWise Administration Guide.

Note that steps 5–6 are conditional steps that apply only if you intend to configure email coexistence during the migration. If you will migrate without email coexistence, skip ahead to step 7.