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 4: Prepare AddProxy program to establish user proxies

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.

Step 5: Configure flat-forwarding on 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: Configure temporary routing domains

NOTE: Steps 5–6 are conditional steps that apply only if you will configure some method of email coexistence during the migration—in which case these steps are optional, but recommended. If you will migrate without email coexistence, skip ahead to step 7.

Whether implementing SMTP mail connectivity or complete coexistence using Quest CMG, most migrating 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’ Office 365 mailboxes until just prior to their migration (in the Batch migration process, per user batch). With this approach, inbound external mail would 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, create them in DNS. One should direct traffic to Office 365 (for example, ex.domain.com). Mail sent to the GroupWise addresses of already-migrated users will be forwarded to the appropriate O365 mailboxes using this domain. After configuring the new domain in DNS, configure Office 365 to accept the SMTP domain and generate appropriate secondary SMTP addresses so all O365 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: Configure 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 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).

Remember that CMG’s Directory Connector does not support direct directory coexistence between GroupWise and Office 365. You may want to consider this "two-step" workaround if you intend to use Microsoft’s DirSync to provision Office 365 from a local AD:

The combination of the two, running sequentially, would configure an effective directory coexistence between GroupWise and Office 365.

Related Documents