Retain Migration Toolkit
Contents |
Overview
The Migration Toolkit automates the process of mail system migrations, removing the difficulties and tedium in creating users and moving mail and system data from GroupWise to Exchange.
The Migration Toolkit not only migrates users from GroupWise to Exchange, but does so in steps, allowing for a smooth setup of the Active Directory system. The steps available are Active Directory user, to mail user, to active mailbox, and also a merge for eDirectory users with Active Directory. This graduated approach provides options for either a measured setup or rapid deployment.
The Migration Toolkit functions from exported CSV files which the toolkit creates. Creation of the CSV file is the sole reason the Toolkit connects to the GroupWise system. Logging into eDirectory, the toolkit grabs all user objects and exports them to the CSV file. After the CSV file has been created, the toolkit only needs to have an active connection to Active Directory to migrate users into Exchange.
We have found that each migration is unique in some significant way. The Migration Toolkit is very flexible and allows significant customizing of the migration process.
Think of the Migration Toolkit as allowing you to setup a jig of how you want the data to be moved from one system to another. Once you have it setup for one user the rest will follow the same pattern.
Handling Problem Messages/Attachments
A new mailbox, mtk@qa.gwava.com, has been created to keep track of the messages that do not migrate correctly. Please forward to it the problematic messages from the source mailbox and mention the subject in the bug in the case where those messages are easy to identify.
For calendar items, they need to be delegated not forwarded. Retain_Migration_Toolkit
For more information on the QA mailbox, go to Routing Customer Problem Mail to QA
Errors
Cannot Find Endpoint
During a migration they get cannot find endpoint error.
ERROR ERROR (migrateMailbox) Cannot get endpoint for [userName]
If a user has multiple domains for their emails but only one for their Active Directory they will need to update their DNS srv file to support autodiscover.
http://support.microsoft.com/kb/940881/en-us
Impersonation
If you get impersonation account errors but you are sure that it is set up correctly try using EWSEditor
