Chat now with support
Chat with Support

Migrator for GroupWise 4.7 - 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

Coexistence with multiple AD domains

Server access rights, email routing, and calendar free/busy lookups will need some special attention in a coexistence when the target environment contains multiple AD domains. In this case, your Migration Plan must note:

Check the run logs for the Admin-Driven Batch Migrator and AD Object Merge Tool. Errors in the log such as Unable to create group or Unable to add group member usually indicate latency problems, which can be resolved by simply waiting a few minutes and running the program again.

End user communications

End user communications is a critical but often neglected element of a smooth migration. A user-communications plan should be a central component of your migration planning, to facilitate early and continuous communications with end users. Your end users will need to know:

If your end users will use the Self Service Desktop Migrator, they will also need the operating instructions for that application, and some admin guidance for how to use it for your purposes. The Migrator for GroupWise documentation suite includes a separate SSDM User Guide PDF that you may distribute to end users as needed.

Your Migration Plan should explain how and when you will deliver all of this information to your users. Many administrators compose one or more notification emails to deliver this sort of information, and send it to users prior to the migration. Some administrators also send another email to the new accounts as soon as they are migrated to the Exchange environment.

Test and pilot migrations

Any full-scale production migration should be preceded by test and pilot migrations, to confirm that your Migration Plan and procedures will accommodate the organization's requirements. A test migration uses copies of real users and real data in a segregated test environment, or dummy users and dummy data in your live production environment. A pilot migration uses a small portion of real users and real data in the live production environment.

In either case—a test or pilot migration—the data to be migrated should be a representative sample of the production data, and the test or pilot migration should be run with the Quest applications set for the same configuration and process options that you intend to use for the production migration. Select test or pilot users whose usage and data types make them representative of the total user population. Then run the migration for those users, just as you have defined the process in your Migration Plan. When the migration is complete, review the program log files for any errors or warnings. (Quest Log File Viewer application will help you view and interpret the program log file. See the Log Viewer chapter in the Migrator for GroupWise Administration Guide for more information.)

Quest recommends that you use both test and pilot migrations:

1
Perform one or more test migrations in a separate test environment, migrating test copies of real users and their real data. The separate test environment ensures that no test process will touch the data or configurations of your production environment. If a test exposes any problems with your Migration Plan, you can amend the plan and then repeat the test by simply "dumping" the entire test environment and recreating it from scratch.
2
When you are confident that your test migrations have sufficiently refined your Migration Plan, perform a pilot migration for 20 to 30 users in your production environment to verify that your plan is satisfactory for your "real world."

 

Other strategic and tactical issues

This chapter contains brief discussions of several topics that all admins should review, to prepare for making informed choices when developing a Migration Plan. Some of these topics may not apply to your organization, but most will, and these are things that migration planners need to understand and accommodate in the written Migration Plan.

Related Documents