Chat now with support
Chat with Support

Migrator for GroupWise 4.7.1 - Pre-Migration Planning Guide

About this guide Introduction Critical considerations Other strategic and tactical issues Known limitations of the migration process Summary of features and capabilities

Phased migration strategy

If your migration scale makes a single-weekend cutover impractical, a phased- migration approach may let you bypass the need for server coexistence and directory synchronizations. By this strategy, users remain on the GroupWise server(s) throughout most of the transition period, receiving and sending mail and managing their calendars in GroupWise just as they always have, while their oldest data (90-95% or even more of the total) is migrated to the new Exchange environment. After the older data has been migrated, the proportionately smaller volume of data remaining can be migrated relatively quickly, so that larger numbers of users can be migrated together within a shorter window, typically in one final cutover weekend. Since Migrator for GroupWise migrates copies of GroupWise data (does not delete the originals), the older data is still available to users in GroupWise throughout the transition period.

This strategy is explained in chapter 1 of the Migrator for GroupWise Scenarios Guide.

Provisioning Active Directory

Your organization may already have an Active Directory running for login and security purposes. Part of your migration process will depend on whether you already have a running AD and, if so, the state of any objects already provisioned there--whether they are mail-enabled, or mailbox-enabled, or neither. If you are migrating to Office 365, you can use Microsoft's DirSync tool to copy objects from a local AD.

Your choice of a provisioning method is critical to defining your migration scenario, which in turn determines the process you must follow to prepare for and perform the migration.

Provisioning to a local Active Directory

Your existing NDS users and groups must be provisioned as security principals in your local Active Directory. Quest Coexistence Manager for Notes (CMG) or Migrator for NDS (separate Quest products, not part of Migrator for GroupWise) offers the most complete capabilities for this task, but other methods are also possible.

Quest Migrator for NDS copies data from NDS to create security objects in a local AD, or add NDS data to existing AD objects, but the AD objects are not mail-enabled by this process. Migrator for GroupWise’s AD Object Merge Tool can then merge GroupWise source addresses into the corresponding AD accounts to mail-enable them. And finally, Migrator for GroupWise’s Admin-Driven Batch Migrator mailbox-enables the accounts—creating the users’ mailboxes in Active Directory.

NOTE: A mail-enabled Active Directory object is one with a mail-address attribute for an address outside the Exchange domain, so AD can forward the object’s mail to its other address. A mailbox-enabled object is one that has an Exchange mailbox. An AD object that is mail-enabled but not also mailbox-enabled cannot receive mail in Exchange since it does not have an Exchange mailbox; it can only forward mail to an object’s external forwarding address.

You could instead use Migrator for GroupWise’s Admin-Driven Batch Migrator to provision Active Directory and create Exchange mailboxes directly from contact objects. This can be a valuable feature in environments where security principals do not already exist in AD, and Quest CMG is used to create routing contacts in AD. This approach is also useful for provisioning resource objects in some migrations. For more information, see the MBoxFromContact parameter in the Migrator for GroupWise Program Parameters Reference.

Migrator for GroupWise’s AD Object Merge Tool can be used to consolidate duplicate objects in AD. For example, if migrating users already use Active Directory security objects for network authentication, some provisioning tools may create corresponding contacts in AD. In this case, the AD Object Merge Tool can (and should) be used prior to migration to consolidate such duplicates, to merge the contacts and existing security objects into a single mail-enabled object per user. This is described in more detail in chapter 3 of the Migrator for GroupWise Administration Guide.

Provisioning to Office 365

If you are migrating to Office 365 and will use Microsoft’s DirSync to provision the hosted AD from a local AD, you can keep the local AD active after the migration for local login and security. For Office 365, this method of provisioning (only) permits single sign-on, also called identity federation, so users can access Office 365 services with the same corporate credentials (user name and password) they use for their local Active Directory environment.

Migrator for GroupWise does not require a local Active Directory or use of the Microsoft DirSync tool. Alternatively, you could provision Office 365 manually, by scripting, or by the Office 365 portal.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating