Chat now with support
Chat with Support

Migrator for GroupWise 4.7.1 - 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 5: Run CMG Directory Connectors to update directories with recent changes

When the AD records are updated and/or Exchange mailboxes are created (as in the preceding step), run the CMG Directory Connector to ensure both directories are current.

Step 6: Run Admin Batch Migrator to migrate data

Run the Administrator-Driven Batch Migrator to migrate user data (mail, calendar, address books, archives, etc.) from GroupWise to Exchange for the users identified in the user-list csv file:

On the Select Operations screen, mark the checkbox for Migrate users.
If you are using Quest CMG for directory synchronizations, you should also Remove directory synchronization exclusion in this program run (on the Exchange Administrative Operations screen). This feature removes the attribute values (in AD) that exclude the users in this migration group from CMG dirsyncs in the Exchange-to-GroupWise direction. Removing the attribute will include these users in bidirectional dirsyncs—useful now that they will be migrated. For more information, see the CmgExcludeFromDirSync= parameter notes in Migrator for GroupWise’s Program Parameters Reference.

See the Administrator-Driven Batch Migrator chapter of the Migrator for GroupWise Administration Guide for complete instructions and application notes.

NOTE: For an Offline Migration (only): In this step you migrate user data from the intermediate storage location (from step 4 above) into Exchange. The Admin Batch Migrator will read the intermediate copy as if it were the live GroupWise server, but the data must be identified and copied to a file system. On the Specify GroupWise Login Information screen: Select the Direct Connection option and specify the path to the Post Office data files.

Step 7: Distribute PST files (if any)

GroupWise data is migrated to individual Exchange mailboxes, Personal Archives or PST files based on selections made in the Batch Migrator program. If any data is migrated to PST files, the admin must either distribute the newly created PST files to users’ desktops, or notify users of the locations of their new PST files (so each user can specify the location within his or her own local copy of Outlook).

Quest Admin Batch Migrator program names any new PST files by their associated User IDs, with incrementing numbers appended to the filename if more than one file is generated per User ID—for example, Smith.pst, Smith-1.pst, Smith-2.pst, and so forth.

When you are finished with this user group ...

Repeat these steps for each batch of migrating users until the entire user population is migrated. You may also integrate some of the SSDM (per-desktop) migration into this process, depending on your circumstances. When the last user batch migration is complete, proceed to the Post-Migration Activities (below) to complete the project.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating