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

Post-migration activities

These post-migration activities apply to migrations to a proprietary Exchange (either local or non-local). Perform these tasks only after you have migrated the last user batch (by the Batch Migrator) or the last individual user (by the SSDM).

Step 1: Provision public distribution lists in Exchange

Run Migrator for GroupWise’s Admin-Driven Batch Migrator to provision GroupWise public distribution lists (PDLs) as Exchange distribution groups. The program reads a Groups­ToProvision.txt data file, generated by the Directory Exporter, to provision PDLs in Exchange. If necessary, you can update PDL content and/or membership in the GroupsToProvision.txt file prior to provisioning the PDLs into AD.

PDLs are typically provisioned in Exchange separately, after users are migrated in the batch-migration process. For operating instructions and application notes, see the Administrator-Driven Batch Migrator chapter of the Migrator for GroupWise Admin Guide.

After your distribution lists are provisioned in Exchange, check the Message Delivery Restrictions settings for any Exchange group to which you want GroupWise users to be able to send messages. Any such Exchange group must be of the universal distribution type to be mail-enabled. To change the settings, beginning in the Exchange Management Console:

Select the group under Recipient Configuration | Distribution Group, then double-click the group you want to edit.
Click the Mail Flow Settings tab, and highlight Message Delivery Restrictions, then click Properties above.
Unmark the check box Require that all senders are authenticated.
Save, and then restart the MS Exchange transport service.

Step 2: Modify routing

Migrator for GroupWise is commonly used to automatically update mail forwarding in both systems to ensure proper routing during the migration. When the user and group migration is complete, routing can be permanently updated.

Depending on the specifics of the environment, this may involve modifying the MX record(s), updating routing tables, and/or firewall modifications. If you haven’t yet redirected your inbound external mail to Exchange, do it now, since all users have now been migrated.

NOTE: Step 14 of the Pre-Migration Preparations explains that you can redirect your inbound mail to Exchange at any time after the users’ AD accounts have been mail-enabled—before, during or after the actual data migration. Most organizations prefer to minimize change before and during the migration process, so they opt to do the routing updates after the migration is complete.

Step 3 (conditional/optional): Configure Quest Directory Connector for ongoing coexistence

If you will keep the GroupWise environment up and running for a time, with an active GroupWise directory, you may want to configure Quest CMG Directory Connector to run recurring directory updates for as long as the GroupWise and Exchange environments coexist.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating