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: Provision Office 365

Microsoft’s DirSync tool can provision Office 365 and create the O365 mailboxes from a proprietary local AD. If you will provision Office 365 this way, you have already provisioned the local AD (in the Pre-migration preparations above). If you will not have a local AD, Migrator for GroupWise can provision Office 365 directly from the GroupWise source, and would also create the O365 mailboxes. Alternatively, you could provision Office 365 manually, by scripting or by the Office 365 portal.

The Establishing Permissions and Access topic below applies to all methods of provisioning Office 365. Read this topic, and then continue with the instructions for your chosen provisioning method.

Access to Microsoft’s Office 365 must be set at the mailbox level through Remote PowerShell. To do so, you must first establish a Remote PowerShell session:

Note: You may receive an error that says a script cannot be executed. If you haven't yet set your ExcecutionPolicy you may also need to change it to RemoteSigned:

After establishing the session, you can issue Exchange commands to Office 365. For example, to establish permissions for the migration admin account(s) to facilitate data migration:

... where <user1> is a migrating user, and <MigrationAdmin> is one of the accounts used for migration in the environment. This command must be run for each migrating mailbox, so scripting will be helpful for larger migrations.

Refer to Microsoft’s documentation to copy the objects in your local Active Directory to Office 365. This DirSync also creates the Office 365 mailboxes. Then go on to step 6.

Run Migrator for GroupWise’s Admin-Driven Batch Migrator to create the O365 accounts and mailboxes. On the Exchange Administrative Operations, select:

Create Office 365 accounts: Creates new Office 365 mailboxes and sets user properties for users in the current user-list CSV file. Migrator for GroupWise can provision the O365 objects directly from GroupWise, and create the O365 mailboxes. This feature can be valuable where security principals do not already exist in a local AD. This approach is also useful for provisioning resource objects in some migrations. For more information, see the MBoxFromContact=1 parameter notes in the Migrator for GroupWise Program Parameters Reference.
Remove user free/busy forwarding to GroupWise: Removes forwarding of CMG free/busy queries to the GroupWise server for the users in the current batch. Now that these users will have Exchange mailboxes, future free/busy queries must be routed to their Exchange mailboxes.

See the Admin-Driven Batch Migrator chapter or the Migrator for GroupWise Administration Guide for more information, with screen-by-screen field notes.

Step 6: Run Migrator for GroupWise's Admin Batch Migrator for administrative functions

Before actually migrating this group of users (next step below), most organizations should run the Admin-Driven Batch Migrator to perform certain administrative functions that are appropriate for their scenarios.

TIP: Some admins report network latency issues when trying to migrate users in the same program run with the admin features listed below. Quest therefore recommends that you not Migrate users in this run of the Admin-Driven Batch Migrator. Instead, you can run the program again (next step below) to perform the actual data migration for this user group.

On the GroupWise Administrative Operations screen, select any number and combination of these features that are appropriate to your circumstances:

Set [GroupWise-to-Exchange] forwarding: Now that the users in this batch are being migrated, any mail for them that arrives in GroupWise must be forwarded to their new Office 365 mailboxes.
Set [GroupWise] user password: Changes users’ GroupWise passwords to new values (specified in a later program screen). Select this option only if you will use passwords to access GroupWise user data for the migration. Some organizations prefer changing GroupWise passwords to encourage use of the new Office 365 environment.
Set user visibility [in the GroupWise directory]: This feature lets you specify the scope of users’ visibility in the GroupWise directory. User visibility determines whether Quest CMG Directory Connector will be able to synchronize the GroupWise account into AD.

If you used Microsoft DirSync to provision Office 365, and if the current user-list CSV file contains any GroupWise resources, then also select this feature on the Exchange Administrative Operations screen:

Set Office 365 resource capacity: This creates Office 365 mailboxes for GroupWise resources, since Microsoft’s DirSync tool does not provision resources. The program will read (from the local AD) the capacities of all resource objects in the user-list CSV file, and copy that data to the corresponding new object records in Office 365.

In any case, most organizations should also select this admin feature, also in the Exchange Administrative Operations:

Remove user free/busy forwarding to GroupWise: Removes forwarding of CMG free/busy queries to the GroupWise server for the users in the current batch. (Now that these users will have Exchange mailboxes, future free/busy queries must be routed to their Exchange mailboxes.)

See the Admin-Driven Batch Migrator chapter or the Migrator for GroupWise Administration Guide for more information, with screen-by-screen field notes.

Step 7: Migrate data

Run the Admin-Driven Batch Migrator again to migrate user data (mail, calendar, address books, archives, etc.) from GroupWise to Office 365 for the users identified in the user-list CSV file. In the Select Operations screen, select Migrate users.

If you have configured Quest CMG Directory Connector for a "two-step" directory coexistence (as described in the preceding step for Set user visibility), you can now run the Batch Migrator one more time for this user group, to select this feature from the Exchange Administrative Operations screen:

Remove directory synchronization exclusion: Removes the attribute values (in the local 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.
IMPORTANT: In this scenario, this feature must be selected in a separate run of the Admin Batch Migrator because Migrator for GroupWise cannot address two different targets in the same program run. (The dirsync exclusion feature must be applied to your local AD, whereas the Migrate users feature migrates data to Office 365.)

See the Administrator-Driven Batch Migrator chapter of the Migrator for GroupWise Administration Guide for more information.

Step 8: Distribute PST files (if any)

GroupWise data is migrated to the individual Exchange mailboxes or PST files based on selections made within Migrator for GroupWise’s Batch Migrator program. If any data has been migrated to PST files, the administrator must either:

Migrator for GroupWise's Admin-Driven Batch Migrator 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.

Related Documents