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 5 (for email coexistence only): configure flat-forwarding on the GroupWise Internet Agent

This step ensures traffic routed from GroupWise to Exchange during the transition period will appear from the original sender with the content inline—rather than from the user’s GroupWise mailbox with an attachment. The GWIA configuration can be updated in gwia.cfg. Additional information is available in this Novell article.

Step 6 (for email coexistence only): Configure temporary routing domains

Whether implementing SMTP mail connectivity or complete coexistence using Quest CMG, most organizations use temporary SMTP domains to route traffic between GroupWise and Exchange. The routing domains may be subdomains of the primary domain (e.g., gw.domain.com and ex.domain.com) or completely separate SMTP domains. As long as they are unique to the respective mail systems, they will suffice for routing purposes.

NOTE: This procedure does not create users’ Exchange mailboxes until just prior to their migration (in the Batch migration process). Inbound external mail would therefore never be routed to GroupWise, but mail coexistence does require a routing subdomain for GroupWise. Exchange-to-GroupWise routing will be necessary during the transition period to route internal mail sent from already-migrated Exchange users to not-yet-migrated GroupWise recipients.

If appropriate SMTP domains are not readily available, they should be created in DNS and added as acceptable domains/addresses in the respective mail systems. One should direct traffic to Exchange (for example, ex.domain.com). Mail sent to the GroupWise addresses of already-migrated users will be forwarded to the appropriate Exchange mailboxes using this domain. After configuring the new domain in DNS, configure Exchange to accept the SMTP domain and generate appropriate secondary SMTP addresses so all Exchange users will be able to receive mail at this domain. The other SMTP domain (e.g., gw.domain.com) can be used to route mail back to GroupWise for users that have not yet migrated. GroupWise must also be configured to accept mail to the new SMTP domain/address.

Step 7 (for coexistence only): Configure your coexistence strategy

Configure your coexistence strategy:

For SMTP mail routing: Confirm the temporary routing domains created in the preceding step and verify routing between the two environments.
For complete coexistence with Quest CMG: Refer to the CMG documentation to install and configure the desired components (Directory Connector, Free/Busy Connector, and/or Mail Connector). If applicable, Directory Connectors should be created and run to update GroupWise and Active Directory with routing objects corresponding to the users in the other system (to establish complete directories).
IMPORTANT: If you already have existing mail-enabled objects in Active Directory, enable the Migrator for GroupWise Compatability Mode for the CMG Directory Connector(s) that will populate AD from GroupWise, to avoid duplicate entries in AD. The CMG Mail Connector and Free/Busy Connector can be configured similar to other scenarios. See the CMG User Guide for much more information.

Step 8 (for local Exchange 2013 or 2010 target only): configure throttling policy

Some migrations to Exchange 2013 or 2010 have achieved improved throughput using a custom throttling policy. This topic is discussed in greater detail in this article: http://blog.tiensivu.com/aaron/archives/2010/11/C7.html.

Related Documents