The GroupWise® Migration Utility 2.1 for Microsoft* Exchange moves Exchange e-mail accounts smoothly into a GroupWise 6.5 system. The Migration Utility accomplishes the following during the migration process:
After you have migrated your Exchange data into your GroupWise system, users can migrate personal items using the GroupWise Import Utility for Microsoft Outlook* to import data from Outlook PST (Personal Folder Storage) files on their workstations or other personal locations into their GroupWise mailboxes or archives.
For complete migration instructions, see the GroupWise Migration Utility 2.1 for Microsoft Exchange Installation and Migration Guide (ExchangeMigrationGuide.pdf).
GroupWise Migration Utility 2.x is compatible for GroupWise 6.5.
During installation, if the Migration Utility displays a message about a component not being properly installed, make sure you are logged into Windows* using an account with administrator rights on the local computer.
If the Migration Utility doesn't display any post offices in the GroupWise Post Office drop-down list, make sure you have read/write access to the domain directory and databases.
If the Migration Utility is unable to list the users on the Exchange server and displays an error in the log file, make sure your current Windows username and password are also valid as a domain username and password with Exchange administrator rights.
On Exchange 5.5, the domain user must be given the Service Account Admin role for the domain object in Exchange Administrator.
On Exchange 2000, the domain user must be allowed full access to the Server object in the Exchange System Manager.
The Migration Utility uses the e-mail address format userID@internet_domain_name for migrated users. If the Exchange system or the GroupWise system is configured to use a different e-mail address format (for example, firstname.lastname@internet_domain_name), then migrated messages cannot be replied to or forwarded from GroupWise.
If you receive a "DIAG COM exception; Invalid pointer" error in the error log during public folder migration, it indicates that the Collaboration Data Objects (CDO) component of Microsoft Outlook is not installed on the computer where you are running the migration. To resolve the problem:
The Migration Utility does not search eDirectory for existing User objects that match the usernames of Exchange users that are being migrated into the GroupWise system. If you have existing eDirectory User objects, make sure that you provide the Migration Utility with the correct contexts where existing objects are located, as described in eDirectory Preparation in the GroupWise Migration Utility for Microsoft Exchange Installation and Migration Guide. If existing User objects are not located in the contexts specified when configuring the migration, duplicate users result.
Migrating large numbers of recurring appointments is a time-consuming process. The Migration Utility might appear to have stopped processing, but it has not.
Recurring items are stored in GroupWise as multiple, individual items, rather than as a single recurring item. The Migration Utility stops creating GroupWise items for recurring Exchange items after 365 days or 20 years. For example, a recurring item every day with no end date would be scheduled one year in advance, and an anniversary with no end date would be scheduled for the next 20 years.
If you are migrating Exchange mailboxes into an environment where the Migration Utility might encounter existing User objects, passwords, and authentication requirements, the migration might fail. Proper preparation for such a migration is described in Planning Your Migration from GroupWise to Exchange in the GroupWise Migration Utility for Microsoft Exchange Installation and Migration Guide.
The Migration Utility is provided in English. In the Migration Options dialog box, if you select Migrate Inbox into Primary GroupWise Mailbox, the contents of the Outlook Inbox folder are migrated into a GroupWise folder named Mailbox (in English). If you select Migrate Drafts into GroupWise Work in Progress, the contents on the Outlook Drafts folder are migrated into the GroupWise folder named Work in Progress (in English). Non-English users must move the items from the folders with English names into the corresponding folders with localized names.
In addition to this Readme, see the GroupWise Migration Guide for Microsoft Exchange on the GroupWise 6.x Gateways page for complete information about the Exchange migration utilities.
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.
Copyright © 2005 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
GroupWise and Novell are registered trademarks of Novell, Inc. in the United States and other countries.
eDirectory is a trademark of Novell, Inc.
All third-party trademarks are the property of their respective owners.