Chat now with support
Chat with Support

Migrator for GroupWise 4.7 - Scenarios Guide

About this guide Scenarios overview Migration to a proprietary Exchange target
Pre-migration preparations Batch migration process Post-migration activities
Migration to Office 365
Migration to Office 365 Pre-migration preparations Batch migration process Post-migration activities
SSDM (per-desktop) migration

Step 13: Mail-enable the Active Directory objects

For Migrator for GroupWise to create mailboxes for the migration (in the Batch migration process below), the objects in Active Directory must be mail-enabled. If you are implementing full coexistence, there may now be two objects in Active Directory for each GroupWise user: the security principal, and the routing contact synchronized earlier in this procedure. In that case, run Migrator for GroupWise’s AD Object Merge Tool to merge the objects into a single mail-enabled user object in Active Directory prior to the migration.

NOTE: Remember the difference between mail-enabling and mailbox-enabling. A mail-enabled Active Directory object is one with a mail-address attribute for an address outside the Exchange domain, so AD can forward the object’s mail to its other address. A mailbox-enabled AD object is one that has an Exchange mailbox. A mail-enabled AD object that is not also mailbox-enabled cannot receive mail in Exchange since it does not have an Exchange mailbox; it can only forward mail to an object’s external forwarding address.

If contacts have not been added to AD in support of coexistence, the AD Object Merge Tool can still be used to mail-enable existing security principals. In this case, addresses and attributes are pulled from Migrator for GroupWise’s CSV files to mail-enable objects rather than pulling information from contacts within AD.

The AD Object Merge Tool applies its functions to AD accounts identified in a CSV file specified during the program run. You can run the AD Object Merge Tool for the entire UsersToMerge.csv file (generated by the Directory Exporter and updated in earlier steps) to perform these functions for all users at once. Or you could use the UsersToMerge.csv file as a template to create subset lists of users. Keep the header row and any rows corresponding to users you want to include in the merge. Then save the file to a new name, still in CSV format.

The result of the merge process (under any of the above scenarios) is a single, mail-enabled user object. Any existing security credentials and routing are preserved. For more information about this process, see the AD Object Merge Tool chapter of the Migrator for GroupWise Administration Guide.

Step 14: When appropriate, modify the MX record

Modify the MX record to direct incoming external (Internet) mail to the Exchange server. With the forwarding capabilities of Migrator for GroupWise, the DNS modification actually can occur any time after the users’ AD accounts have been mail-enabled—before, during or after the actual migration.

Many admins prefer to minimize change before and during the migration process, so they opt to do the routing updates after the migration is complete (as described in the Post-migration activities at the end of this chapter). Some admins prefer instead trying to minimize the "hops" in the forwarding route by modifying the DNS about halfway through the migration process.

Step 15 (if necessary): Copy users' archives to a centralized location

Migrator for GroupWise includes several options for migrating data that currently resides on users’ workstations. One approach uses the Self Service Desktop Migrator (SSDM), a component of Migrator for GroupWise that offers an optional Silent Mode to minimize user interaction and impact. This approach is discussed in greater detail in chapter 4 (SSDM (per-desktop) migration) of this Guide.

Some scenarios, however, require central migration of GroupWise archives. Migrator for GroupWise’s Admin-Driven Batch Migrator can be used to migrate GroupWise archives to Exchange (or to PSTs), but only if the program has access to the source archives. Typically, this means providing users access to a central share and having them copy their archives to this location prior to the migration. The Batch Migrator can also migrate archives from diverse, per-user locations, but only if you specify the location for each user in your user-list CSV file.

If this approach will be used for migrating archives, an appropriate location and process should be established. In addition, the approach and any end-user involvement should be communicated in advance of the migration.

Batch migration process

Migrator for GroupWise includes two migration engines:

Administrator-Driven Batch Migrator (Admin Batch Migrator) performs administrative functions (e.g. mailbox creation, routing updates, etc.), provisions Public Distribution Lists, and migrates batches of users all together in a single program run.
Self Service Desktop Migrator (SSDM) runs in memory on the local workstations and migrates content for one user. SSDM streamlines the process of migrating local content, reduces burden on the migration team, and offers a “Silent Mode” to minimize end user interaction and requirements. For more information on SSDM, see the SSDM (per-desktop) migration chapter later in this Guide.

Either application can be used independently for the entire data migration, or the two may be used together to meet a variety of project requirements.

This section provides process instructions for a typical migration, in which an administrator performs the migrations for multiple groups (batches) of users with no user interaction. The batch-migration process varies depending on whether you are migrating to a proprietary Exchange or Office 365. In this chapter we describe batch migration to a local, proprietary Exchange target. (Planning and deployment for the per-desktop SSDM are described separately, in chapter 4: SSDM (per-desktop) migration.)

The flow chart below summarizes the batch-migration process, and the step numbers in the flow chart correspond to the step numbers in the narrative process instructions that follow.

This batch-migration procedure is repeated for each group of users to be migrated, as shown by the looping arrow in the diagram below.

Related Documents