About this guide
Scenarios overview
About Migrator for GroupWise scenarios and this Guide
Offline migration
Phased (staged) migration options
Migration to a proprietary Exchange target
Pre-migration preparations
Migration to Office 365
Step 1: Install and configure your target Exchange environment
Step 2: Verify that all system requirements are satisfied
Step 3: Install and configure Migrator for GroupWise
Step 4 (for proxy access only): prepare the AddProxy program to establish user proxies
Step 5 (for email coexistence only): configure flat-forwarding on the GroupWise Internet Agent
Step 6 (for email coexistence only): Configure temporary routing domains
Step 7 (for coexistence only): Configure your coexistence strategy
Step 8 (for local Exchange 2013 or 2010 target only): configure throttling policy
Step 9: Run Quest Directory Exporter
Step 10: Review CSV files to verify attributes and matching attributes
Step 11: Provision AD with NDS users and groups
Step 12: Verify target/forwarding addresses
Step 13: Mail-enable the Active Directory objects
Step 14: When appropriate, modify the MX record
Step 15 (if necessary): Copy users' archives to a centralized location
Batch migration process
Step 1: Run Directory Connectors to update directories with recent changes
Step 2: Run Directory Exporter to update CSV Files with recent changes
Step 3: Prepare a migration group user-list .csv file
Step 4: Run Admin Batch Migrator to create mailboxes (and other administrative functions)
Step 5: Run CMG Directory Connectors to update directories with recent changes
Step 6: Run Admin Batch Migrator to migrate data
Step 7: Distribute PST files (if any)
When you are finished with this user group ...
Post-migration activities
Migration to Office 365
SSDM (per-desktop) migration
Throttling and throughput
Provisioning and mailbox creation
Coexistence with Office 365
Access and security with an Office 365 target
Pre-migration preparations
Step 1: Install and configure local Active Directory
Step 2: Verify all system requirements are satisfied
Step 3: Install and configure Migrator for GroupWise
Step 4: Prepare AddProxy program to establish user proxies
Step 5: Configure flat-forwarding on GroupWise Internet Agent
Step 6: Configure temporary routing domains
Step 7: Configure coexistence strategy
Step 8: Run Quest Directory Exporter
Step 9: Review CSV files to verify addresses and matching attributes
Step 10: Provision local AD with NDS users and groups
Step 11: Mail-enable local Active Directory objects
Step 12: Configure Migrator for GroupWise parameters for Office 365
Step 13 (if necessary): Copy users' archives to a centralized location
Step 14: Prepare for Office 365 Wave 15 throttling
Batch migration process
Step 1: Run Directory Connectors to sync the GroupWise directory and the local AD
Step 2: Run Directory Exporter to refresh CSV files with recent changes
Step 3: Prepare a migration group user-list CSV file
Step 4:Prepare local AD accounts for Microsoft's DirSync
Step 5: Provision Office 365
Step 6: Run Migrator for GroupWise's Admin Batch Migrator for administrative functions
Step 7: Migrate data
Step 8: Distribute PST files (if any)
When you are finished with this batch ...
Post-migration activities
Why and when to use the SSDM
Before running the SSDM
If you want to run the SSDM with App-V
Distribution of SSDM program and user communications
Migrating from a cached GroupWise mailbox
Did it work?
Customizing the SSDM
Silent mode options
Providing program entry values in gwdtapp.ini
Choices in the Specify Data for Migration screen
Outlook Profile in the Select Profile screen
Archive Destination Folder in the Specify Directory for Migrated Archive screen
Filter conditions in the Select Date and Size Filters screen
Hiding entire screens from the user
Hiding certain user choices on the Specify Data for Migration screen
For example: to migrate archives only
Command-line switches for running the SSDM in silent mode
Step 3 (conditional/optional): Configure Microsoft DirSync for ongoing directory coexistence
|
NOTE: This step applies only if you used Microsoft’s DirSync tool to provision Office 365, and only if you will keep the local AD in addition to Office 365. For any other configuration, skip ahead to step 4. |
Refer to Microsoft’s documentation to configure the Microsoft Online Services DirSync tool for regularly scheduled synchronizations between your local, proprietary Active Directory and Office 365. Remember that you might also configure a "two-step" coexistence between GroupWise and Office 365—as described above in step 6 of the Batch Migration Process, for the Set user visibility feature.
Step 4 (optional): Prepare for any future migration
|
NOTE: Optional (But Recommended) Step: Even if you are certain you will have no need for any future migration, this step is still a good precaution. |
Step 5: Post-migration "cleanup"
To "clean up" after the last user has been migrated:
|
2 |
If you were using SMTP mail coexistence (with or without Quest CMG): Delete any temporary routing MX domains (e.g., migrate.domain.com). This is the temporary subdomain you created in the Pre-Migration Preparations to support routing between GroupWise and Office 365 during the transition. Now that all users have been migrated to Office 365 and inbound traffic is routing directly to Office 365, the mail-forwarding rules and temporary subdomain should no longer be required. |
|
3 |
If you no longer need the GroupWise environment: After you have verified GroupWise is inactive, you may take a final backup and decommission the environment. |