Chat now with support
Chat with Support

Migrator for GroupWise 4.7 - Quick Start Guide

The solution: Quest Migrator for GroupWise

Quest Migrator for GroupWise is a set of coordinated software applications designed to facilitate a variety of migration strategies for organizations moving from Novell GroupWise to an Exchange environment—either to a proprietary Exchange network, or to Office 365.

The Migrator for GroupWise applications are designed to complement other Quest and Microsoft products, to deliver these comprehensive, integrated solutions to the challenges of a GroupWise-to-Exchange migration:

Migration of server data: Migrator for GroupWise migrates mail, appointments, tasks, personal address books, and frequent contacts from the GroupWise environment, and lets you specify the destinations for different data types, either to the Exchange server or to Outlook personal folders (.pst) files.
Migration of GroupWise archives: Migrator for GroupWise can migrate archives from either a central file server or user desktops, to either Outlook .pst files or the Exchange server.
User involvement: Migrator for GroupWise lets an administrator migrate most, or even all, user data with no user involvement whatsoever. In a typical migration scenario, all user data is migrated in batches by an administrator—a hundred or more users migrated at a time, over a series of migration runs.
Provisioning: Migrator for GroupWise extracts user data from the GroupWise server to mail-enable user accounts in Active Directory that were provisioned by Migrator for NDS, which facilitates Exchange-to-GroupWise mail routing for not-yet-migrated users. The batch-migrator component then mailbox-enables the accounts as users are migrated, copies users' GroupWise addresses, aliases and nicknames from GroupWise to Active Directory, and provisions GroupWise personal distribution lists directly into Active Directory.
Coexistence: While Quest CMG Directory Connector can synchronize the two directories, Migrator for GroupWise's Directory Exporter updates the data files that Quest migration programs use to migrate data and convert addresses. Migrator for GroupWise also offers dynamic mail forwarding that automatically sets, updates and removes mail-forwarding rules in user mailboxes, on both servers, to assure correct mail routing throughout the transition.

Migrator for GroupWise, together with Quest Migrator for NDS and CMG Directory Connector, and Outlook deployment tools, can perform or facilitate every administrative task associated with a GroupWise-to-Exchange migration. Other CMG components can facilitate short- or long-term mail and calendar coexistence as well. All Quest programs support operational options that allow great flexibility in devising and implementing a suitable migration strategy to suit most any network configuration, circumstances and preferences.

Meanwhile, the accompanying Quest documentation provides a truly project-scale approach to migration planning and management, with a comprehensive checklist of pre-migration planning topics, and broad-context process instructions that explain how the Quest tools fit into the overall flow of a variety of migration scenarios.

Product components

Migrator for GroupWise contains several related applications, which may be used in various combinations to accomplish a wide range of migration strategies:

Directory Exporter: Extracts user data from the GroupWise directory to build four data files, which provide necessary source data to other Migrator for GroupWise applications.
AD Object Merge Tool: Merges users’ GroupWise addresses into AD security objects, to mail-enable the accounts. Also, if the program finds Exchange Contacts for users who also have AD accounts, the program merges some of the Contact attributes into the corresponding accounts, and then deletes the Contacts, to merge the pair into a single mail-enabled security object per user.
Addproxy: Automates the process of setting proxy rights for migrating users. (Used only for administrator-driven batch migrations when resetting users' GroupWise passwords is impractical or otherwise inadvisable.)
Administrator-Driven Batch Migrator: Used by an administrator to provision GroupWise public distribution lists (PDLs) in Active Directory, or to perform various combinations of these tasks for the users specified in a user-list .csv file:
Admin Account Pool Utility: Helps an administrator manage a "pool" of Office 365 admin accounts to improve migration throughput to Office 365 within the constraints of Microsoft throttling limitations.
Discovery.exe: Pre-migration discovery tool that collects mailbox and archive information. This information is written to a csv file, and can be used to plan a migration.
Self Service Desktop Migrator: Used by end users, or by administrators on behalf of end users, to migrate users’ GroupWise data to Exchange.
Log File Viewer: Simplifies the viewing and interpretation of Quest program log files, which are generated by most Migrator for GroupWise components to document process errors and warnings.
Migrator for GroupWise Prerequisites Checker: Scans the environment to determine whether it conforms to the system requirements for the Migrator for GroupWise applications. The Migrator for GroupWise Prerequisites Checker looks for required software and settings, connectivity, permissions, and access rights.

System requirements

This section applies only if you are migrating to a proprietary Exchange target. If you are migrating to Office 365, skip ahead to Account permissions for migration to Office 365.

Different organizations have varying network security standards that determine the number and configuration of user accounts necessary to perform a migration. It is possible to configure a single migration admin account in Active Directory with all the necessary rights in both AD and Exchange to run a full migration. But many organizations prefer, and Quest recommends, not to concentrate so much administrative authority in a single account. The alternative is to configure two separate accounts, each with more restrictive access rights to perform different portions of the overall migration process: one account for access to Active Directory containers and data, and the other for access to Exchange mailboxes. We describe both approaches here.

Account permissions and security considerations for migration to a proprietary Exchange target

This section applies only if you are migrating to a proprietary Exchange target. If you are migrating to Office 365, skip ahead to Account permissions for migration to Office 365.

Different organizations have varying network security standards that determine the number and configuration of user accounts necessary to perform a migration. It is possible to configure a single migration admin account in Active Directory with all the necessary rights in both AD and Exchange to run a full migration. But many organizations prefer, and Quest recommends, not to concentrate so much administrative authority in a single account. The alternative is to configure two separate accounts, each with more restrictive access rights to perform different portions of the overall migration process: one account for access to Active Directory containers and data, and the other for access to Exchange mailboxes. We describe both approaches here.

Related Documents