Quest® GroupWise Migrator for Exchange

Version 3.5.0.16

Release Notes

February 2007

(Doc ID 044)

Welcome to GroupWise Migrator for Exchange

New in this Release

Resolved Issues and Enhancements

Known Issues

Upgrade and Compatibility

Welcome to GroupWise Migrator for Exchange

Quest Software's GroupWise Migrator for Exchange is a coordinated set of software applications designed to facilitate a variety of migration strategies for organizations moving from Novell GroupWise, versions 5.5.3 to 7.0, to an Exchange 2003 or 2007 environment. The Quest applications are designed to complement Microsoft's Exchange Connector for GroupWise and Outlook deployment tools, and provide a project-scale approach to overall migration planning and management. GroupWise Migrator for Exchange can:

Extract user data from the GroupWise server to mailbox-enable user accounts in the Active Directory, and preserve users' current SMTP addresses in their new AD accounts.
Migrate users' mail, appointments, tasks, personal address books, personal distribution lists and frequent contacts from the GroupWise environment to the Exchange server or Outlook Personal Folders (.pst) files.
Migrate users' archives from GroupWise either to Outlook .pst files, or to the new server.
Copy each user's GroupWise folder hierarchy into Exchange, and migrate the permissions that facilitate the sharing of folders.
Set and remove mail-forwarding rules between GroupWise and Exchange to assure correct mail routing throughout the transition period.

In a typical scenario, an administrator uses the GroupWise Migrator for Exchange batch-migration program to migrate groups of dozens of users at a time. But the Quest applications also contain a per-desktop migration program that lets an administrator visit individual desktops to perform migrations one user at a time, or end users can run the same per-desktop program to perform their own migrations. For that matter, an administrator can mix-and-match these strategies: migrating some users in batches, but others individually at their desktops, while still other users run the per-desktop tool themselves.

Quest's GroupWise Migrator for Exchange supports several such operational options that allow considerable flexibility in devising and implementing a suitable migration strategy for almost any set of circumstances and preferences.

GroupWise Migrator for Exchange, together with Microsoft's Exchange Connector and Outlook deployment tools, can perform or facilitate every administrative task associated with a GroupWise-to-Exchange migration. Meanwhile, the accompanying Quest documentation provides a truly project-scale approach to migration planning and management, with a comprehensive, broad-context 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.

New in this Release

Version 3.5.0.16 of GroupWise Migrator for Exchange corrects problems discovered in the product's folder-creation and group-provisioning features. This release contains no entirely new or updated features.

What Was New in Version 3.5.0.12 (initial release of version 3.5)

Updates in GroupWise Migrator for Exchange 3.5.0.12:

Per-desktop application renamed "Self-Service Desktop Migrator" - The per-desktop migration program, called the "End User-Driven Migrator" in previous releases, has been renamed to the "Self-Service Desktop Migrator."
Enhanced "silent mode" for Self-Service Desktop Migrator - The Self-Service Desktop Migrator now permits greater admin control over which screens and which fields will appear to the user in the GUI, and the values that will prevail for fields that are hidden from the user. These program customizations are accomplished by a set of INI-file parameters, documented in Appendix D of the GroupWise Migrator for Exchange User Guide.
Enhanced Log Viewer application - The Log Viewer now provides more detailed reports, an ordered listing of errors, with user list and the solution details from the solution website. Also, you can now optionally use the Log Viewer without contacting the Internet -- useful at sites that do not have or are blocked from Internet access.
More documentation for pre-migration planning - Chapter 1 of the GroupWise Migrator for Exchange User Guide now contains a much-expanded section on Pre-Migration Planning and Testing, with several new topics, and updated information and elaborations for most existing topics.

New Features in GroupWise Migrator for Exchange 3.5.0.12:

Exchange 2007 support - GroupWise Migrator for Exchange now supports migration to Exchange 2007, and mailbox creation with PowerShell for Exchange 2007 servers. GroupWise resources are now migrated to resource mailboxes in Exchange 2007.
GroupWise 7 support - GroupWise Migrator for Exchange now supports migration from GroupWise version 7.
"Smart" remigration by admin-driven batch migrator - The administrator-driven batch migrator now automatically detects if a GroupWise source item has been previously migrated, and if so will not create a duplicate item in Exchange. This feature can operate in either of two modes, determined by a boolean program parameter in the [Exchange] section of gwmigapp.ini:
[Exchange]
RemigrateMode=<#>

... where the parameter value is a single digit, 0 or 1:
- 0 (Update mode): If the program detects a duplicate message in Exchange, the message will be deleted in Exchange and then remigrated from the GroupWise source.
- 1 (default): If the program detects a duplicate message in Exchange, the GroupWise source will not be migrated, leaving the previously migrated copy in Exchange.
Log files now document system information - GroupWise Migrator for Exchange applications now log system information at the top of each log file, as appropriate (per application): versions of the Outlook and Groupwise clients installed on the migration workstation, versions of the GroupWise and Exchange servers, and versions of the Novell and GroupWise clients. (This feature will help Quest Support staff recreate a problem, to analyze and solve it.)
Documentation of mail-routing options for coexistence - The Pre-Migration Planning and Testing section of the GroupWise Migrator for Exchange User Guide now includes an explanation of mail-routing options for coexistence. The new material explains the advantages and disadvantages of mail routing and free/busy lookups via the Microsoft Connector vs. SMTP addressing vs. a hybrid scheme using both methods.
New Program Parameters documentation - The Program Parameters Reference, previously available only by separate download (under the title Program INI-Files Reference), is now included in the primary product kit and installed with the other documentation.

Resolved Issues and Enhancements

Issues Addressed and Enhancements Implemented in This Release

CR #22547	Outlook folder issues resolved: Reported problems with Outlook folder accessibility and the visibility of items within Outlook folders have been corrected. Some customers had reported being unable to move items into an Outlook folder after migration, but this problem is now resolved.
CR #22640	Group provisioning issues in Exchange 2007 resolved: In some network configurations, groups that had been provisioned into AD for an Exchange 2007 target environment were not mail-enabled as they should have been. This problem is now fixed.

Issues Addressed and Enhancements Implemented in Version 3.5.0.12 (initial release of version 3.5)

CR #[none]	Migration improvements: Embedded images for HTML messages are now displayed correctly in migrated messages. Checklist items now maintain their follow-up times and alarms. Migrated contacts now preserve multiple email addresses (up to three will be migrated).
CR #[none]	MAPI profile credentials now collected by GroupWise Migrator for Exchange: In previous releases, the Quest application let MAPI prompt for its own credentials, but in some circumstances the admin would be prompted to exit the application and then reenter the credentials. This problem does not occur now that the Quest application collects the credentials.
CR #[none]	New documentation help for coexisting applications on migration workstation: The System Requirements sections of the GroupWise Migrator for Exchange User Guide and Quick-Start Guide now include advice for how the multiple applications required on the admin's migration workstation can be installed in a particular order to minimize application conflicts and incompatabilities.
CR #[none]	Restored documentation section: A paragraph in the GroupWise Migrator for Exchange User Guide, offering suggestions for how an admin might distribute the per-desktop migration program, has been restored. The paragraph had been inadvertently deleted from the documentation in version 3.2.

Known Issues

Most of the known limitations of any migration process are due to feature inconsistencies between the source and target environments. That is, features that are available in the GroupWise environment simply cannot be migrated to a target environment that does not offer the same or comparable features. Other limitations are due to feature incompatabilities, where similar features are available in both the source and target environments, but their implementations are so different that the migration may be impractical. In any case, most administators regard these sorts of limitations as trivial or incidental to an overall migration project.

Appendix F of the GroupWise Migrator for Exchange User Guide provides a complete list of all such known limitations of the migration process as facilitated by the current version of Quest's GroupWise Migrator for Exchange.

Upgrade and Compatibility

There is no need to uninstall the previous version before installing the new version. The upgrade installation and setup will be fully automated, and will preserve any data already migrated by an earlier version, so that you may simply resume the migration process from wherever you left off with the previous version.

System Requirements

GroupWise Migrator for Exchange requires the installation and configuration of several components on various machines: the source GroupWise server, the destination Exchange server, the admin's migration workstation (sometimes two or more admin workstations), and end-user client desktops. In addition to the Quest components, a migration requires the installation and proper configuration of other, non-Quest applications including the GroupWise and Exchange servers, Active Directory, and the GroupWise and Outlook clients. The full installation and configuration requirements are therefore more detailed than the requirements summary provided here. See the GroupWise Migrator for Exchange Quick-Start Guide for complete System Requirements, including tips for how to get multiple applications from different vendors to cooperate when installed on a single admin workstation.

This list specifies the basic minimum hardware and software requirements for GroupWise Migrator for Exchange version 3.5.0.16:

On the GroupWise server:	Must be running Novell GroupWise version 5.5.3 to 7.0. If GroupWise Internet Addressing is not enabled, GroupWise Internet Agent LDAP Service must be configured to automate the creation of the Address Translation Table. For more information, see: http://www.novell.com/documentation/lg/gw55/index.html?gw55ia/data/a2zuwkc.html.
On the Exchange server:	Must be running either Exchange 2007 or Exchange 2003.
On each administrator workstation (running the GroupWise Migrator for Exchange admin components):	Workstation OS must be Windows XP (32 bit) SP2 or higher, or Windows 2003 Server (32 bit) SP1 or higher. GroupWise Migrator for Exchange does not support a 64-bit OS. Workstation must be a separate machine from the Exchange server, but a member of the same domain as AD and Exchange, and meeting these minimum hardware requirements: 1+ GHz processor. 1GB memory. 20GB free disk space. Recommendations for improved performance, especially for high-volume migrations: 3+ GHz processor. 2GB memory. 1 Gbps NIC. 1 Gbps or faster network connections among all migration workstations and the Exchange and GroupWise servers. Required for any Exchange 2003 administrative functions: Windows Admin Tools (adminpak.msi). Exchange System Manager (version to match the installed version of Exchange). Required for migration to Exchange 2007 (only): Exchange 2007 Management Tools (32-bit version), which in turn requires: .Net Framework 2.0, Microsoft Management Console (MMC), and Windows PowerShell. The 32-bit version of Exchange 2007 Management Tools is available (at this writing) at this Microsoft link, and see also Microsoft's installation instructions. The Novell NetWare Administrator program (NWAdmin or ConsoleOne) must be installed. The Novell client for NetWare (client version 4.7 or higher, 4.91 SP2 recommended), and the GroupWise client must both be installed. Outlook 2000, 2002 or 2003 must be installed. Note: If GroupWise 5.5 is installed on the server, then Outlook 2000 or 2002 (not 2003) is required. (Outlook 2003 is incompatible with GroupWise 5.5, so that combination is not supported.) The MAPI DLLs required to perform a migration must be those that are part of Outlook, not the downloadable Exchange 2007 "server" MAPI.
On user desktops (if running the Self-Service Desktop Migrator):	Must be running Microsoft Windows 2000 (or higher). Must be running Outlook 2000, 2002 or 2003. Must be running a GroupWise client version 5.5.3 to 7.0.
All machines:	Must have network access.

Global Operations

This section contains information about installing and operating this product in non-English or non-ASCII configurations, such as those needed by customers outside the USA. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

The platforms and configurations supported in this release may use any time zone, single-byte character encoding, language, or locale configuration to operate this product. Multibyte encodings (such as those used for the Chinese, Japanese, or Korean languages) may work appropriately but have not been tested and this product should be used with caution in those environments.

The migration server must be installed and operated on a machine where the code page associated with the runtime locale is identical to the encoding for each mailbox being migrated. The Groupwise APIs used to retrieve the data do not support retrieval of data from outside the current code page. For example, if the migration server were configured on a German machine (which uses code page 1252) and used to migrate a mailbox containing Polish data (which uses code page 1250), data would be lost during the migration.

The Exchange server which is a target for the migration may be in any locale, as that interface uses the Unicode character set.

Getting Started

Contents of the Release Package

The GroupWise Migrator for Exchange (GME) version 3.5.0.16 zip-bundled distribution file contains the following component applications, accessories and documentation files:

Quest GME Setup Wizard (to install and configure the other components listed below)
Quest GME components:
- Directory Exporter
- AD Object Merge Utility
- Administrator-Driven Batch Migrator
- End User-Driven Migrator
- AddProxy Utility
- Log Viewer
Quest GME product documentation:
- Release Notes (HTML document)
- PDF-format documents:
  - Quick-Start Guide: QStartGuide.pdf
  - GME User Guide: GMEUserGuide.pdf
  - Self-Service Desktop Migrator User Guide: SSDMUserGuide.pdf
  - Program Parameters Reference: GME_INI_Reference.pdf
- On-line Help systems (compiled HTML Help files):
  - gwdirapp.chm (for the Directory Exporter)
  - adobjmerge.chm (for the AD Object Merge Utility)
  - gwmigapp.chm (for the Admin-Driven Batch Migrator)
  - gwdtapp.chm (for the End User-Driven Migrator)
  - wlogview.chm (for the Log Viewer)

Installation Instructions

Refer to the GroupWise Migrator for Exchange Quick-Start Guide for installation instructions.

For More Information

Contacting Quest Software:

Email	info@quest.com
Mail	Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA
Web	http://www.quest.com

Refer to our Web site for regional and international office information.

Contact Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

Quickly find thousands of solutions (Knowledgebase articles/documents).
Download patches and upgrades.
Seek help from a Support engineer.
Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.

This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
Email: legal@quest.com

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.