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

Pre-migration preparations

Any migration scenario requires prior preparation of the source and target environments, configuration of admin accounts and a coexistence strategy, and preparation of the required software you will use as part of the migration process. These procedures can be complex because they include configuring necessary account permissions across separate environments, configuring applications running concurrently to facilitate the migration, and various other considerations. However, these tasks are typically performed once, before the first user group or first user is migrated, so they do not need to complicate the entire migration process.

The flow chart below illustrates these pre-migration preparations for migration to Microsoft’s Office 365. Note that the step numbers in the flow chart correspond to the step numbers in the process instructions here.

NOTE: This procedure does not create users’ Office 365 mailboxes until just prior to their migration (in the Batch migration process, per user batch), because O365 is unable to send a free/busy query to GroupWise for a not-yet- migrated user who already has an O365 mailbox. Office 365 can direct such a query only to its own O365 mailbox.

If you will not configure free/busy coexistence, you could create Office 365 mailboxes earlier in the process, as part of these Pre-Migration Preparations— as long as you also set Exchange-to-GroupWise mail forwarding during the transition for not-yet-migrated GroupWise users.

Step 1: Install and configure local Active Directory

If you have not yet installed and configured your local Active Directory, do it now. Provisioning of Active Directory, if necessary, will occur at a later step.

If you will use Microsoft’s DirSync tool to provision Office 365 from the local AD, you should also install the DirSync tool at this time. See Microsoft’s documentation for details, and note that the DirSync tool may reside on the admin's Migrator for GroupWise migration server if the Migrator for GroupWise computer also conforms to the DirSync tool’s requirements, which include:

OS must be 32-bit Windows Server 2003 Standard SP2, or 2003 R2 Standard SP2. (Both Migrator for GroupWise and the DirSync tool support other server versions, but the two listed here are the only versions supported by both.)
The computer must be joined to the AD forest you plan to synchronize, and must be able to connect to all other domain controllers for all the domains in your forest. (A forest is one or more AD domains that share the same class and attribute definitions, site and replication information, and forest-wide search capabilities.)

If the Migrator for GroupWise workstation does not meet those requirements, the DirSync tool must be installed on a different computer.


NOTE: Remember: Office 365 supports synchronization of up to 20,000 objects. To synchronize more than 20,000 objects, contact Microsoft’s Office 365 Support.

Step 2: Verify all system requirements are satisfied

All of the system requirements, including the necessary admin accounts and access privileges (see System Requirements in the Migrator for GroupWise Quick Start Guide) must be satisfied before you begin this process.

Step 3: Install and configure Migrator for GroupWise

Complete installation instructions are available in the Getting Started section of the Migrator for GroupWise Quick Start Guide, which is included with the product download and also is available on the Quest website.

It is also important to consider whether Migrator for GroupWise’s Self Service Desktop Migrator (SSDM) component will be used as part of the migration strategy. If so, it should also be installed and configured.

MFG supports unambiguous GroupWise-to-Exchange mail forwarding for two users sharing the same name and Object ID, but residing in different Post Offices and different domains. This feature associates a particular Post Office/domain (in GroupWise) with its corresponding IPaddress:port. You can then configure as many of these associations as necessary to define a unique IPaddress:port for each GW Post Office/domain.

The associations are defined by parameters entered into the [GroupWise] section of gwmigapp.ini. For example, if:

... then you could define:

These settings would forward the mail for each John Doe (and any other user pairs sharing the same name and Object ID) to the appropriate target address in Exchange.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating