GMEUser Guide

User Guide
Version 3.5
Quest GroupWise Migrator for Exchange

GroupWise Migrator for Exchange User Guide
Updated - January 2007 (Doc ID 003)
Software Version - 3.5
2007 Quest Software, Inc.

ALL RIGHTS RESERVED.
This guide 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.
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
www.quest.com
email: legal@quest.com
Refer to our Web site for regional and international office information.
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.
User Guide
TRADEMARKS
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.
iii
CONTENTS
ABOUT THIS GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
HOW TO USE THE PRODUCT DOCUMENTATION . . . . . . . . . .12
DOCUMENTATION CONVENTIONS . . . . . . . . . . . . . . . . . . .14
ABOUT QUEST SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . .15
CONTACTING QUEST SOFTWARE . . . . . . . . . . . . . . . . . . .15
CONTACTING CUSTOMER SUPPORT . . . . . . . . . . . . . . . . . .15
CHAPTER 1: INTRODUCTION AND PLANNING . . . . . . . . . . . . . . . .17
ABOUT GROUPWISE MIGRATOR FOR EXCHANGE . . . . . . . . . . . . .18
PRODUCT COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . .19
SYSTEM REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . .20
Network Security Considerations and Options . . . . . . . . 20
How To Set the "Receive As" Privilege in Exchange. . . . . 20
Requirement Specifications . . . . . . . . . . . . . . . . . . . . . 21
PRE-MIGRATION PLANNING AND TESTING . . . . . . . . . . . . . . . .23

DEVELOP A WRITTEN MIGRATION PLAN . . . . . . . . . . . . . . .23
STRATEGIC PLANNING ISSUES . . . . . . . . . . . . . . . . . . . .24
Batch vs. Per-Desktop Migration. . . . . . . . . . . . . . . . . . 24
Migration Scale and Duration . . . . . . . . . . . . . . . . . . . . 25
Before-and-After Site Configurations. . . . . . . . . . . . . . . 27
Coexistence and Synchronization . . . . . . . . . . . . . . . . . 28
Provisioning in Active Directory . . . . . . . . . . . . . . . . . . 30
Method of Access to GroupWise
User Data by Password or by Proxy. . . . . . . . . . . . . . 31
Desktop Considerations . . . . . . . . . . . . . . . . . . . . . . . . 32
Multi-Workstation Considerations . . . . . . . . . . . . . . . . . 32
Phased Migration Strategy . . . . . . . . . . . . . . . . . . . . . . 33
Strategies for Migrating Resources . . . . . . . . . . . . . . . . 34
Strategies for Migrating Groups (Distribution Lists). . . . . 35
Accommodating Known Limitations of the
Migration Process and Other Special Circumstances . . . . 36
Migrating from an Older Version of GroupWise . . . . . . . . 36
End User Communications . . . . . . . . . . . . . . . . . . . . . . 36
TEST AND PILOT MIGRATIONS . . . . . . . . . . . . . . . . . . . .37

v
CHAPTER 2: MIGRATION PROCESS INSTRUCTIONS . . . . . . . . . . . .39

PROCESS INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . .40
NECESSARY PRE-MIGRATION PREPARATIONS . . . . . . . . . . . . . . .40
Step 1:
Verify that All System Requirements Are Satisfied . . . . . 41
Step 2: Prepare the
Addproxy Program to Establish User Proxies . . . . . . . . . 41
Step 3:
Create a Temporary Subdomain for the Migration. . . . . . 41
Step 4: Create a
Recipient Policy for the Temporary Subdomain. . . . . . . . 41
Step 5:
Provision Active Directory with NDS Users and Groups . . 42
Step 6: Run Quest's Directory Exporter . . . . . . . . . . . . . 42
Step 7:
Review and Modify (If Necessary) the Data Files . . . . . . 42
Step 8: Mail-Enable All Users AD Accounts . . . . . . . . . . 42
Step 9: Provision Public Distribution Lists in Exchange . . 43
Step 10: Modify the MX Record . . . . . . . . . . . . . . . . . . 43
Step 11: Set RemoveSrcAddresses=1 in gwmigapp.ini . . 43
Step 12 (If Necessary): Move Users Archives
and PABs to a Centralized, Accessible Location. . . . . . . . 43
BATCH MIGRATION PROCESS (PER USER GROUP) . . . . . . . . . . .44

Step 1: Accommodate Any Recent Staff Changes . . . . . . 44
Step 2: Prepare a Migration Group User-List .csv File . . . 45
Step 3: Run Quest's Administrator-Driven
Batch Migrator to Perform Administrative Functions . . . . 47
Step 4: Synchronize the Two Directories . . . . . . . . . . . . 48
Step 5: Run Quest's Administrator-Driven
Batch Migrator to Migrate User Data . . . . . . . . . . . . . . . 48
Step 6: Distribute .pst Files (If Any) . . . . . . . . . . . . . . . 48
MIGRATION PER DESKTOP . . . . . . . . . . . . . . . . . . . . . . . . . .48

Customizing the Self-Service Desktop Migrator . . . . . . . 49
Before Running the Self-Service Desktop Migrator . . . . . 49
Distribution of Self-Service Desktop Migrator Program . . 49
Notifications to End Users . . . . . . . . . . . . . . . . . . . . . . 50
vi
User Guide
Command-Line Switches for

Running the Desktop Migrator in Silent Mode . . . . . . . . . 50
If a User Does Not Appear To Be Migrated
(After Running the Self-Service Desktop Migrator) . . . . . 51
POST-MIGRATION CLEAN-UP . . . . . . . . . . . . . . . . . . . . . . . .52

CHAPTER 3: DIRECTORY EXPORTER . . . . . . . . . . . . . . . . . . . . . .53
ABOUT DIRECTORY EXPORTER . . . . . . . . . . . . . . . . . . . . . . .54
OPERATING INSTRUCTIONS . . . . . . . . . . . . . . . . . . . . . . . . .55
REVIEW AND MODIFY (IF NECESSARY) THE DATA FILES . . . . . . . .57
CHAPTER 4: ADMINISTRATOR-DRIVEN BATCH MIGRATOR . . . . . . .59
OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
PER-SCREEN INSTRUCTIONS AND APPLICATION NOTES . . . . . . . .61
1: WELCOME SCREEN . . . . . . . . . . . . . . . . . . . . . . . . .61
2: SELECT OPERATIONS . . . . . . . . . . . . . . . . . . . . . . . .62
3: SPECIFY USERS FOR UPDATE . . . . . . . . . . . . . . . . . . .63
4: SELECT GROUPWISE ADMINISTRATIVE OPERATIONS . . . . .64
5: GROUPWISE FORWARDING OPTIONS . . . . . . . . . . . . . .65
6: SPECIFY SOURCE-TO-TARGET MAIL FOWARDING DOMAIN . .66
API Gateway vs. SMTP . . . . . . . . . . . . . . . . . . . . . . . . 67
7: SPECIFY GROUPWISE PASSWORDS . . . . . . . . . . . . . . .68

8: SELECT GROUPWISE VISIBILITY . . . . . . . . . . . . . . . . .69
9: SELECT EXCHANGE ADMINISTRATIVE OPERATIONS . . . . . .69
10: SPECIFY ACTIVE DIRECTORY INFORMATION . . . . . . . . . .70
11: SPECIFY EXCHANGE MAILBOX INFORMATION . . . . . . . . .72
12: SPECIFY TARGET-TO-SOURCE
MAIL FORWARDING DOMAIN . . . . . . . . . . . . . . . . . . . . .72
13: SPECIFY DATA FOR MIGRATION . . . . . . . . . . . . . . . . .73
14: SELECT DATE AND SIZE FILTERS . . . . . . . . . . . . . . . .75
15: SPECIFY GROUPWISE INFORMATION . . . . . . . . . . . . . .76
16: SPECIFY GROUPWISE LOGIN INFORMATION . . . . . . . . .76
17: SPECIFY DESTINATIONS FOR MIGRATED DATA . . . . . . . .78
18: SPECIFY HOW TO MIGRATE SHARED INFORMATION . . . . .79
19: SELECT DESTINATION EXCHANGE SERVER . . . . . . . . . .81
vii
20: SPECIFY PST OUTPUT ROOT DIRECTORY . . . . . . . . . . .82

21: SPECIFY GROUPWISE DOMAIN PATH . . . . . . . . . . . . .84
22: SPECIFY RUN INFORMATION . . . . . . . . . . . . . . . . . . .85
23: MIGRATION SETTINGS SUMMARY . . . . . . . . . . . . . . . .86
24: PROGRESS SCREEN . . . . . . . . . . . . . . . . . . . . . . . .87
25: RESULTS SCREEN . . . . . . . . . . . . . . . . . . . . . . . . .88
REMEMBER TO DISTRIBUTE ANY USER .PST FILES . . . . . . . . . . .89
APPENDIX A: ADDPROXY UTILITY . . . . . . . . . . . . . . . . . . . . . . .91
ADDPROXY PREREQUISITES . . . . . . . . . . . . . . . . . . . . . . . . .91
INSTALLING ADDPROXY . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Uninstalling the AddProxy Program . . . . . . . . . . . . . . . . 93
ADDPROXY.INI SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . .93

addproxy.ini Required Parameters . . . . . . . . . . . . . . . . 93
addproxy.ini Optional Parameters . . . . . . . . . . . . . . . . . 95
APPENDIX B: AD OBJECT MERGE TOOL . . . . . . . . . . . . . . . . . . .97

BEFORE YOU BEGIN ... . . . . . . . . . . . . . . . . . . . . . . . .97
OPERATING INSTRUCTIONS . . . . . . . . . . . . . . . . . . . . . .98
APPENDIX C: LOG FILE VIEWER . . . . . . . . . . . . . . . . . . . . . . . 103
TO CHANGE THE SORT ORDER
LOG FILE NAVIGATOR. . . . . . . . . . . . . . . . . . . . 105
OF THE
TO GENERATE A USER-LIST .CSV FILE

"ERROR USERS" (IN THE LOG FILE). . . . . . . . . . . . . . 105
OF
TO GENERATE A REPORT OF THE LOG FILE . . . . . . . . . . . . 106

APPENDIX D: CUSTOMIZING THE
SELF-SERVICE DESKTOP MIGRATOR PROGRAM . . . . . . . . . . . . . . 107
PROVIDING PROGRAM ENTRY VALUES IN GWDTAPP.INI . . . . . . . . 108
Migration Choices in
the Specify Data for Migration Screen . . . . . . . . . . . . . 108
Outlook Profile in the Select Profile Screen . . . . . . . . . 109
Archive Destination Folder in
the Specify Directory for Migrated Archive Screen . . . . 110
viii
User Guide
Filter Conditions in the

Select Date and Size Filters Screen. . . . . . . . . . . . . . . 110
HIDING ENTIRE SCREENS FROM THE USER . . . . . . . . . . . . . . . 111

HIDING CERTAIN USER CHOICES ON
THE SPECIFY DATA FOR MIGRATION SCREEN. . . . . . . . . . . . . . 112
FOR EXAMPLE: TO MIGRATE ARCHIVES ONLY . . . . . . . . . . . . . 113
APPENDIX E: HOW GROUPWISE MIGRATOR
FOR EXCHANGE MAPS SHARED FOLDERS TO OUTLOOK . . . . . . . . . 115
APPENDIX F: KNOWN LIMITATIONS OF THE MIGRATION PROCESS . 117
GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
ix
About This Guide

Overview
How To Use the Product Documentation
Documentation Conventions
About Quest Software
Contacting Quest Software
Contacting Customer Support
Overview
This document has been prepared to explain the intended uses and operating
instructions for Quest Softwares GroupWise Migrator for Exchange, and to
explain how GroupWise Migrator tools are most typically used within the broader
context of an overall migration project.
How To Use the Product Documentation

The documentation for Quest GroupWise Migrator for Exchange includes three
printable PDF documents:
Quick-Start Guide: An orientation to the product's basic purposes

and features, and to how its component tools are most typically used
within the broader context of an overall migration project. The
Quick-Start Guide also includes instructions for downloading and
installing the software, and a procedure to help you assess the
product's suitability for your own needs and circumstances.
GroupWise Migrator for Exchange User Guide: The document

you are now reading, with operating instructions and application
notes for the components of GroupWise Migrator for Exchange that
are used by administrators, an in-depth look at pre-migration
planning, and recommended approaches for the most common
migration scenarios and strategies.
Self-Service Desktop Migrator User Guide: Operating instructions

and application notes for the Self-Service Desktop Migrator
component of GroupWise Migrator for Exchange. The Self-Service
Desktop Migrator User Guide is provided as a separate document so
that an administrator can distribute it to any end users who will run
the per-desktop program.
The Quick-Start Guide and GroupWise Migrator for Exchange User Guide are
intended for network administrators, consultants, analysts, and any other IT
professionals who will install the product, use its administrative tools, or
contribute to migration project planning. The Desktop Migrator User Guide is
intended for end users or administrators who will use the Self-Service Desktop
Migrator component.
This GroupWise Migrator for Exchange User Guide is organized into four chapters
and six appendixes. The first two chapters provide orientation and planning
information, with broad-context process instructions for how to accomplish a
variety of migration strategies, while chapters 3 and 4 provide operating
instructions for the two product components that are used in virtually all
migration scenarios:
12
User Guide
1.
Introduction and Planning: An orientation to the products

purpose and capabilities, and a checklist of topics and issues that
should be considered in pre-migration planning.
2.
Migration Process Instructions: Step-by-step instructions for how

to accomplish particular migration strategies and scenarios with
Quests tools. This chapter explains the contexts in which Quest tools
are used. Wherever these procedures call for the application of Quest
tools, the scenario-oriented instructions refer to tool-specific
operational details in chapters 3 and 4, and in the appendixes.
3.
Directory Exporter: Operating instructions and application notes

for the Directory Exporter component of GroupWise Migrator for
Exchange.
4.
Administrator-Driven Batch Migrator: Operating instructions and

application notes for the Administrator-Driven Batch Migrator
component of GroupWise Migrator for Exchange.
The appendixes provide operating instructions and application notes for the
less-routinely used "accessory" components of the product, and other
supplemental information you may find useful for particular migration
strategies:
A.
Addproxy Utility: Operating instructions and application notes.
B.
AD Object Merge Tool: Operating instructions and application

notes.
C.
Log File Viewer: Operating instructions and application notes.
D.
Customizing the Self-Service Desktop Migrator Program.
E.
How GroupWise Migrator for Exchange Maps Shared Folders

to Outlook.
F.
Known Limitations of the Migration Process.
We strongly recommend that all administrators read all of:
The Quick-Start Guides Product Overview and two Walkthrough

sections.
The first two chapters of this GroupWise Migrator for Exchange User
Guide.
These sections in particular are designed to familiarize you with how Quests
migration tools fit into the broader context of an overall migration process, and
to help you devise a migration strategy and a written Migration Plan that suits
the needs of your network configuration, your users, any institutional
imperatives of your organization, and of course your own preferences.
13
You may then follow the appropriate process instructions in chapter 2 to

implement your strategy(ies), and refer as needed to the product operational
details in chapters 3 and 4, and in the appendixes.
Documentation Conventions
In order to help you get the most out of this guide, we have used specific
formatting conventions. These conventions apply to procedures, icons,
keystrokes and cross-references.
ELEMENT
CONVENTION
Select
This word refers to actions such as choosing or highlighting

various interface elements, such as files and radio buttons.
Bolded text
Interface elements that appear in Quest products, such as

menus and commands.
Italic text
Used for comments.
Bold Italic text
Used for emphasis.
Blue text
Indicates a cross-reference. When viewed in Adobe

Reader, this format can be used as a hyperlink.
Used to highlight additional information pertinent to the
process being described.
Used to provide Best Practice information. A best practice
details the recommended course of action for the best
result.
Used to highlight processes that should be performed with
care.
14
Ctrl+C
A plus sign between two keystrokes means that you must

press them at the same time.
Edit | Copy
A pipe sign between elements means that you must select

the elements in that particular sequence.
User Guide
About Quest Software

Quest Software, Inc. delivers innovative products that help organizations get
more performance and productivity from their applications, databases and
infrastructure. Through a deep expertise in IT operations and a continued focus
on what works best, Quest helps more than 18,000 customers worldwide meet
higher expectations for enterprise IT. Quest Software, headquartered in Irvine,
California, can be found in offices around the globe and at www.quest.com.
Contacting Quest Software

Phone
949.754.8000 (United States and Canada)
Email
info@quest.com
Mail
Quest Software, Inc.

5 Polaris Way
Aliso Viejo, CA 92656
USA
Web site
www.quest.com
Please refer to our Web site for regional and international office information.
Contacting Customer Support

Quest Software's world-class support team is dedicated to ensuring successful
product installation and use for all Quest Software solutions.
SupportLink
http://www.quest.com/support
Email at
support@quest.com.
You can use SupportLink to do the following:
Create, update, or view support requests
Search the knowledge base
Access FAQs
Download patches
15
16
1
Introduction and Planning
About GroupWise Migrator for
Exchange
Product Components
System Requirements
Pre-Migration Planning and Testing
Develop a Written Migration Plan
Strategic Planning Issues
Test and Pilot Migrations
About GroupWise Migrator for

Exchange
Quest Softwares GroupWise Migrator for Exchange is a set of related 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 another Quest product, NDS Migrator, and Microsoft's Exchange
Connector for GroupWise and Outlook deployment tools, to 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 environment or Outlook Personal Folders
(.pst) files.
Migrate users' archives from GroupWise to either Outlook .pst files, or

the new server.
Copy each users 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 or even
hundreds 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.
Quests 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.
18
Product Components
GroupWise Migrator for Exchange contains several separate but related
applications, which may be used in various combinations to accomplish a wide
range of migration strategies:
Directory Exporter: Extracts user data from the GroupWise directory

to build four data files, which will provide necessary source data to other
Quest applications.
AD Object Merge Tool: Merges users GroupWise addresses into AD

security objects, to mail-enable the accounts. Also, if the program finds
Exchange Contacts for users who also have AD accounts, the program
merges some of the Contact attributes into the corresponding accounts,
and then deletes the Contacts, to merge the pair into a single
mail-enabled security object per user.
Addproxy: Automates the process of setting proxy rights for migrating

users. (Used only for administrator-driven migrations when resetting
users' GroupWise passwords is impractical or otherwise inadvisable.)
Administrator-Driven Batch Migrator: Used by an administrator to

provision GroupWise public distribution lists (PDLs) in Active Directory,
or to perform any or all of these tasks for the users identified in a
user-list .csv file:
Mailbox-enable Exchange accounts.

Change the GroupWise passwords for migrating users.
Extract users' GroupWise data and migrate it to Exchange.
Update mail-forwarding rules for groups of migrating users.
Specify users' visibility in the GroupWise directory.
Self-Service Desktop Migrator: Used by end users, or by

administrators on behalf of end users, to extract users GroupWise data
and migrate it to Exchange.
Log File Viewer: Simplifies the viewing and interpretation of Quest

program log files, which are generated by most Quest applications to
document process errors and warnings.
19
System Requirements
Network Security Considerations and Options
Different organizations have different network security standards that determine
the number and configuration of user accounts necessary to perform a
migration. The most straightforward approach is to configure a single migration
admin account in Active Directory with all the necessary rights in both AD and
Exchange to run a full migration:
In Active Directory, this account must be added to the Domain Admins

group. On each Exchange Mailbox Store to which the users are
migrating, the account must be added to the security access control list
with at least Receive As rights. This single account must then be used to
login to the migration workstation, and provide the Exchange Server
credentials and the Active Directory credentials as needed.
Many organizations, however, prefer not to concentrate so much administrative

authority in a single account. The alternative is to configure two separate
accounts, each with more restrictive access rights, to perform different portions
of the overall migration process. For example:
One account to login to the migration workstation: A domain user

account in Active Directory, with Read/Write delegate access on all OUs
where users and groups will be provisioned. On the Exchange server,
this account will need Exchange Administration delegate access to the
Administrative Group where the users mailboxes will be created. This
account must then be used to login to the migration workstation.
A separate account to provide Exchange Server credentials and

AD credentials: A user object in Active Directory, added to the Domain
Admins group. On every Exchange Mailbox Store, this account must be
added to the security access control list with at least Receive As rights.
How To Set the "Receive As" Privilege in Exchange

When migrating to Exchange, the admin account that will be used to provide
Exchange server credentials and AD credentials from the Quest programs must
be configured with Receive As rights to each mailbox store, as noted in the
Requirement Specifications below.
To set the Receive As privilege in Exchange 2007 (for all mail stores):
1.
Launch an Exchange Management Shell.
2.
Type (in one continuous line):

get-mailboxdatabase | add-adpermission
-user <migadmin> -extendedrights Receive-As
20
To set the Receive As privilege in Exchange 2003 (for each mail store):
1.
In Exchange System Manager, in the folder tree: Drill down through:

Administrative Groups
[Admin Group Name]
Servers
[Server Name]
[Storage Group Name]
Mailbox Store
2.
Right-click on Mailbox Store, and select Properties.
3.
In the Properties dialog box, click the Security tab.
4.
In the Group or user names list, select the name of the account you
want to endow with the privilege.
5.
In the Permissions for [Account Name] chart, click the Allow

checkboxes for Receive As and Send As.
6.
Click OK to save the settings and clear the Properties dialog box.
Requirement Specifications
The requirements for GroupWise Migrator for Exchange 3.5 include:
On the GroupWise server:
Must be running Novell GroupWise version 5.5.3 to 7.0.

An admin account must be defined with administrator rights to the
GroupWise server.
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.

An account must be defined with access to the Exchange environment. (A
new account with "Receive As" rights to each mailbox store, and not assigned
to any group, would be suitable for this purpose.)
For Exchange 2003 (only): Recipient Update Service must be set to
Always Run.
On the Active Directory server:
An account must be defined with administrator access to the Active Directory

environment. A new account with rights to add and delete users, and to
manipulate AD accounts, would be suitable for this purpose. An account
added to the DomainAdmins group would have sufficient rights, although
membership in that group also confers other rights that may compromise
some organizations security standards.
21
On each administrator workstation (running the GroupWise

Migrator for Exchange administrator applications):
To accelerate large-scale migrations, GroupWise Migrator can be run
on multiple migration workstations running in parallel.
Order of Installation: A migration requires an unusual combination
of tools, developed by different vendors, all installed on this single
admin workstation, and the combination can cause compatability
problems on some machines. To minimize these conflicts, Quest
recommends that you install the applications (per the specifications
noted below) in this particular order:
1.
2.
3.
4.
5.
6.
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 any Exchange 2007 administrative functions:
Exchange 2007 Management Tools, which in turn requires .Net

Framework 2.0, Microsoft Management Console (MMC), and Microsoft
Windows PowerShell.
Must have a directory with write/execute permissions for the Administrator
components of the Quest software, and must have a directory with
read/execute permissions for the user components of the software.
A profile must be defined with administrator access to the Exchange
environment ("Receive As" permission to each mail store).
22
Windows Messaging Subsystem

GroupWise client
Outlook client
Microsoft PowerShell (only if migrating to Exchange 2007)
ConsoleOne
Exchange Admin tools
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 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 (using code page 1252) and used to migrate a mailbox
containing Polish data (using code page 1250), data would be lost during the
migration.
The Novell NetWare Administrator program (NWAdmin or ConsoleOne) must
be installed. GroupWise Directory Exporter has the same prerequisites as the
NetWare Administrator program.
The Novell client for NetWare (client version 4.7 or higher, 4.91 SP2
recommended), and the GroupWise client must both be installed, and a
Novell GroupWise profile must be present. When migrating from GroupWise
7 running on a SUSE Linux server, the NetWare client must be logged into
eDirectory. Otherwise (if migrating from a Netware server), the NetWare
client must be logged into NetWare. For GroupWise 6.5 and earlier, the
Novell GroupWise profile must be set as the default profile.
Outlook 2000, 2002 or 2003 must be installed, and the Outlook profile must
be configured to always prompt for credentials. 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.)
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.
Pre-Migration Planning and Testing

Develop a Written Migration Plan
The migration of any enterprise is typically a complex process that requires
careful planning and project management. Even a high-level summary checklist
of necessary tasks can be quite long, and will expose a good number of details
that must be addressed for a successful migration. The "choreography" in the
sequence, timing, and coordination of tasks is also important.
The complexity of most migration projects makes planning, foresight and
communications critical to a smooth migration. Halfway through the migration
23
process is no time to discover that a neglected detail or invalid assumption will

cost the organization dozens or hundreds of hours of productivity, or cause
unnecessary aggravation for end users. Quest therefore recommends you
develop a comprehensive written Migration Plan before you begin any migration
process.
Developing a Migration Plan is a valuable exercise that will lead you to consider
and accommodate all of the factors likely to affect an organization's migration.
At a minimum your plan should address or consider all of the Strategic Planning
Issues described below.
Strategic Planning Issues

Batch vs. Per-Desktop Migration
The batch-migration program and the Self-Service Desktop Migrator both can
migrate the same types of data, so the overall migration will usually be more
efficient if an administrator can use the batch-migration program to migrate all
or most users in batches. A user batch typically numbers a hundred or so users,
all migrated together in a single program run. Your Migration Plan should specify
whether you will migrate users in batches, or one at a time, or by some
combination of the two.
Consider that Quests Administrator-Driven Batch Migrator program can migrate
users' archives only if they reside in a single centralized location, or if the archive
locations can be specified per user in the accompanying user-list .csv file. Batch
migration may therefore require that users copy their archives to a central
location if they are not currently stored on a network drive, or an admin may
have to manually add the per-user archive locations to the .csv file prior to
running the batch-migration program.
Alternatively, the Self-Service Desktop Migrator can be used to migrate archives,
one user at a time, after the batch-migration program has migrated the users
server-based data. If user archives are not centrally accessible, or if some other
circumstance or preference makes batch migration impractical or inadvisable,
the Self-Service Desktop Migrator is simple and intuitive enough that most end
users will be able to run it uneventfully.
Some administrators prefer to visit select desktops personally, running the
Self-Service Desktop Migrator on behalf of end users, to ensure a smooth
transition for executives, or for users who may be uncomfortable attempting the
tasks themselves.
If you intend to migrate any user data by batches, your Migration Plan should
note your requirements and preferences for these aspects of user grouping:
24
Grouping Method: Determine how you will group your users for
migration. It is often helpful to migrate users in logical groups, related
by business function or administrative entity, or by physical proximity,
so users can support one another through the transition.
Optimum Number of Users Per Batch: The optimum number of users

per migration batch depends primarily on the capacity of your
organization's Help desk, since you can assume that the transition will
stimulate increased demand for Help resources. Note also the per-user
data volume on the server, the data geography (physical distribution)
and bandwidth, and the capacities and configuration of the destination
servers. Consider that the programs log files will likely bloat to unwieldy
sizes for batches much greater than 100 users if you ever need to set
the logging to verbose mode.
Note: The first few batches should be smaller than your
expected optimum size, since these first groups will likely expose
any unforseen problems before a larger group would generate
correspondingly larger consequences.
Migration Scheduling: Determine how you will schedule batches for

migration. This is often just a matter of avoiding each groups critical
dates on the calendar. For example, finance and accounting staff should
not be disrupted at the beginning of the month when they are trying to
close the books. Likewise, sales staff would prefer no interruptions near
the end of a quarter when they are attempting to meet their quotas.
Many organizations migrate their IS or Help Desk staff first, since they
are typically the most technical users and will likely help to support other
users as the migration proceeds.
Migration Scale and Duration

A very small organization may be able to migrate all of its users together at one
time, but bandwidth, processing, and other limitations usually make it
impractical to migrate larger numbers of users (more than 100 to 150) in a
single run of the batch-migration program. Most mid-sized to large organizations
therefore must migrate their users in a series of subset migration groups. Each
such group is simply a subset of the universe of all users to be migrated.
The scale and expected duration of a migration project are critical planning
factors, because these things determine whether an organization will require
directory coexistence and directory synchronization during the transition period.
(Coexistence and Synchronization are explained in more detail in a separate
topic below.) The two most important factors that affect the duration of a
migration are data volume, and the number of migration workstations that will
be used to migrate the data. The Admin-Driven Batch Migrator can be run on
multiple migration servers running in parallel, applied to different user groups
simultaneously. In this way, you might employ a half dozen migration
25
workstations to migrate a particular data volume in a single weekend, whereas

you would need a half dozen weekends to migrate the same volume via a single
workstation.
Data "geography" and bandwidth are the most significant factors affecting the
rate of data migration, and migration workstation hardware (memory, number
and speed of CPUs, and disk speed) is also important. Actual throughput rates
for the batch-migration program vary widely with the interplay of all relevant
factors, but administrators typically report migration rates of one to three
gigabytes per hour. If the data to be migrated is distributed among servers in
dispersed geographic locations, and if the bandwidth among these servers is
problematic, then the throughput rate will likely be at the lower end of that
range. On the other hand, a migration rate of 3 GB per hour or faster is likely if
the source data is centralized and the bandwidth is very good. Rates as high as
20 GB/hour have been reported under optimal conditions with high-performance
workstation hardware.
The chart below can help you estimate the throughput rate for your migration
project, but remember that actual rates vary widely and you should not
rely on these values as definitive. The chart does not account for hardware
factors, and your assessment of your own bandwidth is subjective and arbitrary.
You cannot reliably predict your own throughput rate without experimenting in your own environment with your own data.
To estimate the duration (total processing hours) of a migration project, first
determine the estimated throughput rate:
Estimated Throughput Rates (GB/hr)
Data Distribution
(percent of total data volume that is centralized)
Bandwidth is ...
Very Good
0-25%
25-50%
50-75%
75-100%
1.2
1.8
2.4
3.0
Good
1.0
1.6
2.2
2.8
Fair
0.8
1.4
2.0
2.6
Poor
0.6
1.2
1.8
2.4
... and then plug the estimated rate value into this formula:
Est Total
Migration
Hours
Total Data
Volume (GB)
Est Throughput Rate
Number of Migration Workstations

Running in Parallel
This formula will help you estimate the number of processing hours required for
Quests batch migrator to migrate a particular volume of data under particular
26
conditions, but remember there is much more to a migration project than just
processing time. An administrator must also export directory data from
GroupWise sources, provision users and distribution groups into Active
Directory, define subset batches of users, and so forth. You should also allow
time to review the Quest programs log files, to verify that the programs run
parameters are appropriate and efficient, and to catch and correct any minor
problems before they become major problems.
Per-desktop tasks such as installation of the Outlook client, and sometimes the
migration of archives (separately, per-user) also must be figured into the plan,
and you should also expect an increased demand on the organizations Help
desk. You may find that a couple dozen instances of the batch-migration
program running on parallel workstations can migrate thousands of users over
a weekend, but youll face a support nightmare on Monday morning if you
havent ramped up your Help desk staff to accommodate all of the likely calls
from freshly migrated users.
For a longer-term migration that will span more than just a couple of weeks, you
can expect that these other associated admin tasks will get easier and take less
time as the project progresses. But these collateral admin tasks make it unwise
to attempt a single-weekend migration if the estimated migration time
(processing hours) exceeds 20 to 30 hours.
Before-and-After Site Configurations

Characterize the configuration of the organizations servers, both as they are
now and how they will be after the migration.
Draw a network map of the pre-migration GroupWise environment, showing:
The locations, domain names and operating systems of all servers.

The number of users and total data volume on each server.
The bandwidths among the various nodes.
The network map should be a graphical illustration, to help migration planners

visualize the relationships between the data volumes of the various servers and
the inter-node bandwidths that connect them.
For each server, note also (but not necessarily on the same network map):
How users were assigned to each serverby geographic location, or

administrative entity, or some other scheme.
The volume and locations of the various types of source data at each
serverthat is, the volume (mega/gigabytes) of user mail, user archives
and address books, and whether each type is located in a centrally
accessible (server) location, or will be copied or moved to a centrally
accessible location, or is located on user desktops.
27
Next, draw another graphical network map to show your post-migration

Exchange environment: the locations and domain names of all servers, and the
data capacity of each server. Then view the pre-migration and post-migration
configuration maps side-by-side, and determine which users from which
GroupWise servers will migrate to which Exchange servers. Make a table to
document these before-and-after server assignments for each group of users to
be migrated.
Coexistence and Synchronization

Coexistence is the state of two or more independent servers when both are
serving the same organization at the same timefor example, when some users
have already been migrated to a new server while others remain on the old
server, awaiting migration. A migration project small enough that all user data
can be migrated in a single weekend will be simpler than a longer-term migration
because the latter requires additional planning and several extra steps to
accommodate the coexistence and server synchronizations that will likely be
necessary throughout the transition period.
Coexistence requires dynamic mail routing throughout the transition period,
since forwarding rules must be updated upon the migration of each user batch.
Users must be able to send mail and schedule meetings with one another across
all active servers, throughout the transition period, without having to know the
migration status of other users.
Coexistence also is likely to require regular synchronizations of the source and
destination directories. Most mid-sized and large organizations will experience
staff additions, departures, transfers, and so forth during the transition period,
since their migrations extend over a period of at least several days, many for
several weeks or even months. Any staff changes that occur while the migration
is in-process will introduce data inconsistencies between the source and
destination servers, and these inconsistencies may need to be reconciled during
the migration process. Synchronization is the process of updating the contents
of one directory to match the contents of another.
Coexistence and directory synchronization introduce much more complexity to a
migration, and several more steps to the process. Its therefore important for an
organization to determine at the outset whether the scale of the project will
permit a single-weekend approach, or require coexistence and synchronization.
Synchronizing Directory Data and Updating Program Data Files

If synchronization of coexisting directories during the transition period is not a
high priority for the organization, the admin may simply add and delete users
and update user data in the Exchange environment (only), using Exchange
administration software. Otherwise, if it is important to keep the two directories
synchronized throughout the transition period:
28
Enter any staff changes within the GroupWise environment as they

occur, just as you always have.
If any already-migrated user leaves the organization: Delete the user

from the Exchange server, using Exchange administration software.
Prior to the migration of each user group:
Run Microsofts Exchange Connector for GroupWise to re-synchronize the

directories, from GroupWise to Exchange. (You need not perform this step
explicitly if the Connector is scheduled to automatically re-synch the
directories at regular intervals.)
Re-run Quest's Directory Exporter to generate new, updated .csv files that
will accurately reflect the current staff list. (Remember to review the new
.csv files and, if necessary, edit them, as explained in chapter 3.)
Email Routing and Free/Busy Lookups

Your Migration Plan should specify your method of email routing and free/busy
lookups (or lack thereof):
By SMTP addressing via subdomains, which can facilitate email routing

but not calendar free/busy lookups.
Note: SMTP forwarding from GroupWise will introduce reply-ability
issues for external recipients.
By the Microsoft Connector, with native GroupWise addressing, which

can facilitate both email routing and calendar free/busy lookups.
By a hybrid scheme, in which email is forwarded via SMTP addressing,

but the Microsoft Connector is used for free/busy lookups.
If any end users have Blackberry devices: Note that mail-forwarding via the
SMTP method will forward the original message as an attachment, which will be
unreadable on devices like the Blackberry that do not support opening email
attachments.
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 destination environment
contains multiple AD domains. In this case, your Migration Plan should note:
Server rights must be set to allow the Quest programs to access all of
the various domain controllers.
The AD Object Merge Tool and the Exchange administrative functions of

Quests Admin-Driven Batch Migrator should be run against the primary
AD domain controller, which is less likely to encounter latency errors
29
(delays in directory synchronization among the various domain

controllers and the Global Catalog).
Be sure to 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....
Unable to add group member....
... usually indicate latency problems, which can be resolved by simply
waiting a few minutes and running the program again.
Provisioning in Active Directory

Decide how accounts, groups and distribution lists will be provisioned in Active
Directory. Provisioning may be accomplished by a variety of methods, but for
most organizations the simplest and most complete will include running another
Quest product, NDS Migrator (not a part of GroupWise Migrator for Exchange),
to provision NDS users and groups as security objects and security groups,
respectively, in Active Directory. If you use the NDS Migrator to move NDS
objects into AD, you can then use two components of GroupWise Migrator for
Exchange to mail-enable and then mailbox-enable the AD objects. (A
"mail-enabled" object has no Exchange mailbox, but contains a pointer to an
external address, so mail can be routed to the external address. Mail-enabling is
necessary for external mail arriving via the Exchange server to be correctly
routed back to the GroupWise addresses of users who have not yet migrated.)
Quests NDS Migrator copies data from NDS to create security objects in AD, or
add NDS data to existing AD objects, but the AD objects are not mail-enabled by
this process. Quests AD Object Merge Tool then merges the GroupWise source
addresses into the AD accounts to mail-enable them. And finally, Quests
Administrator-Driven Batch Migrator mailbox-enables the accountseffectively
creating the users mailboxes in Active Directory.
The Administrator-Driven Batch Migrator can also provision Public Distribution
Lists in ADa straightforward process that occurs in a separate program run,
before the first users are migrated.
Quests AD Object Merge Tool can also be used to consolidate duplicate objects
in AD. For example, if migrating users already use Active Directory security
objects for network authentication, some provisioning tools may create
corresponding Contacts in AD. In this case, the AD Object Merge Tool can (and
should) be used prior to migration to consolidate such duplicates, to merge the
Contacts and existing security objects into a single mail-enabled object per user.
The AD Object Merge Tool is explained in more detail in Appendix B of this Guide.
30
Method of Access to GroupWise

User Data by Password or by Proxy
The Administrator-Driven Batch Migrator must have access to users' GroupWise
accounts to migrate user data to the new Exchange environment. If you are migrating from GroupWise version 6.5 or higher, the migration program will use
Novells Trusted Application API feature to automatically register itself as a trusted application, and will then be able to migrate GroupWise user data without
user passwords or proxy authorization. But if the source GroupWise version is
earlier than 6.5, the program will need to access users GroupWise data either
by password or by proxy, as described below.
The easiest way to provide access to GroupWise accounts (when necessary) is
to have the program reset all migrating users' passwords, and then use the new
known password values to login under each user's login identity. If you adopt
this migration-by-password method, the batch-migration program can reset
users' passwords before accessing their GroupWise accounts.
The program can reset all users' passwords to a single common value, or can set
each user's password to a value that was previously entered in the user-list .csv
file. Alternatively, you can set each user's password to a unique random string
of characters.
If resetting passwords is impractical or otherwise inadvisable, the program also
supports batch migrations by proxy (rather than by password). That is, the
program can login to each user's account using the credentials of an admin
account that has previously been authorized, by proxy, to access the user
account. GroupWise Migrator for Exchange includes a utility called Addproxy that
automates the process of establishing proxy rights for this purpose.
Your Migration Plan should specify which method will be used to access
GroupWise user data. While Quest applications support both methods, the
password-access method will almost always be more efficient. The proxy
method affects the timing and complexity of a migration project because users
cannot be migrated until they have granted the appropriate proxy rights to the
administrator. Quest's Addproxy program automates this process and can
execute automatically from users network login scripts, but the utility will run
only upon each user's next login which may not be a daily or even weekly
occurrence for some users. The Addproxy utility automatically logs the
successful procurement of proxy rights for each user, but the administrator must
then review the list of user proxies to determine whose proxy rights remain
outstanding, and then migrate those users separately at a later time.
Two other disadvantages of the proxy-access method are that resources cannot
be migrated and mail-forwarding rules cannot be set or removed by proxy
access.
31
While the password-access method is preferred in most circumstances, some

organizations will want to keep the GroupWise environment running and
accessible for some time after the migration. In this case it would be unwise to
standardize users' GroupWise passwords to a common, known value, which
would leave their accounts vulnerable to unauthorized access by other users.
The program's access to GroupWise accounts for the migration should therefore
be accomplished by one of the alternate methods described above.
Desktop Considerations
If user workstations will need Outlook installed or upgraded, you must determine
before the first users are migrated how you will accomplish the installations or
upgrades. Remember that installing Outlook requires administrator privileges on
end users' machines. There is a MAPI service that permits the use of Outlook to
access GroupWise, but users in most organizations will be using the native
GroupWise client. For these sites, use either the deployment capabilities within
Outlook 2003 or a configuration management program to distribute and install
Outlook. New profiles can be defined during or after the Outlook installation.
Multi-Workstation Considerations
The programs of GroupWise Migrator for Exchange can be run on multiple
migration workstations running in parallel. This approach opens several strategic
options that you should consider and document in your Migration Plan. One
simple option for the batch-migration program is simply to assign different user
batches to different migration workstations, and have each program run include
all necessary admin and migration functions for the users in the batch.
The tasks performed by different Quest component programs require access
privileges for different servers: GroupWise vs. Exchange vs. Active Directory.
Likewise, the different functions available within the batch-migration program
require different access privileges, depending on the scope of their activities. For
example, admin access to Exchange and AD would not be necessary to set
mail-forwarding rules in GroupWise, but of course admin access rights in
GroupWise would be required for that function. You might therefore consider
setting up multiple workstations with different access privileges to different
environments, and then define tasks and assign them to various workstations
accordingly.
Consider how you might define and distribute various tasks to an array of
differently configured migration workstations to maximize the efficiency of your
overall process, and then document your strategy in your Migration Plan.
32
Phased Migration Strategy

Some administrators opt for a phased-migration strategy, whereby users remain
on the GroupWise server(s) throughout most of the transition period, while their
oldest data (perhaps 90-95% or even more of the total) is migrated to the new
Exchange environment. After the older data has been migrated, the
proportionately smaller volumes of data remaining can be migrated relatively
quickly, so that larger numbers of users can be migrated together within a
shorter window. This phased-migration strategy is possible because Quests
Admin-Driven Batch Migrator lets you specify date limits and ranges for
messages to be migratedto migrate only messages timestamped on or after
(or before) a certain date, or within a particular range of dates.
Some organizations will need several days or weeks to move the older
GroupWise data to the target Exchange environment. But during this time all
users will continue to receive and send mail and manage their calendars in the
GroupWise environment.
For some organizations where the Migration Scale and Duration puts a
single-weekend migration just out of reach, a phased-migration approach can
bypass the need for server coexistence and synchronizations. For example, if
your total migration processing time is on the order of 50-100 hours, you might
migrate the oldest 80-90% of the data (40-90 hours) over two to four weekends
while all users remain in the GroupWise environment, and then migrate the
users with the last 10-20% of their data (5-20 hours) all together in one final
weekend.
If you adopt this strategy, the Exchange accounts and mailboxes must be
created to accept the migrated old data before the users actually start using
their Exchange mailboxes or calendars. You therefore must run the
Administrator-Driven Batch Migrator twice for each user group:
First Pass: to mailbox-enable user accounts on Exchange, set

mail-forwarding rules on Exchange (to forward mail back to GroupWise
until the users migrate), and migrate users' older data to the new
server; and then ...
Second Pass: to migrate the remaining (newer) data to Exchange,

reverse the mail-forwarding rules (to forward mail from GroupWise to
the new Exchange mailboxes), and migrate the users themselves to the
new server.
Note: The date filters that you define for a phased migration like this
are applied only to mail and calendar items, and not to users
contacts. If contacts are selected for migration in the second pass of a
phased migration, after they were already selected for migration in
the first pass, the second pass will create an entire duplicate set of
contacts in the Exchange environment. Quest therefore recommends
that contacts be migrated only in the final cutover migration.
33
Users in this scenario will require continued access to their GroupWise mailboxes
while the administrator migrates their older data, so they should keep their
unique, secure passwords through the transition period. The program's access
to GroupWise accounts should therefore be accomplished by some method other
than by a common-value password. For an overview of the other methods, see
the Method of Access topic above.
Strategies for Migrating Resources

When a resource (conference room, AV equipment, and so forth) is migrated to
Exchange, the resource also remains on the GroupWise serverthat is, the
GroupWise original is copied, not destroyed or altered. After migration the two
resources exist independently of each other, so users who have not yet migrated
to Exchange will interact only with the GroupWise resource, while migrated users
will interact only with the Exchange/AD resource. This coexistence introduces
the potential for "double-booking" resources, since users in Exchange have no
way of knowing whether the corresponding resources in GroupWise may have
been reserved by not-yet-migrated users, and vice-versa.
There is no easy or complete solution to this "double-booking" problem, but you
may want to consider some options to mitigate its effects, and your Migration
Plan should identify this strategy. If your organization can live without the
automatic resource reservation and coordination features for the duration of the
migration period, you may simply accept the temporary loss of these features.
Other options:
34
Defer the migration of all resources to the very end of the migration
project, with (or after) the last users, and tell all migrated users that
they may not request resources via Outlook until they are notified that
the resources have been migrated to the Exchange environment. In
the meantime, designate a not-yet-migrated user to serve as a
Resource Coordinator in GroupWiseto manually relay resource
requests from Exchange users to GroupWise resources, and manually
relay resources replies back to the Exchange users.
If your resources are ordinarily allocated to certain groups of users

(for example, a particular slide projector or a particular conference
room is used only by users in a particular department, or on a
particular floor), organize your user groups so that you migrate
resources in the same groups with the users who use them. Or, if your
resources are pooled to be available to larger groups of users, you
could impose temporary limits on resource allocation as described
abovedivvying up your resources among different user groups, for
the duration of the transition periodto make possible a coordinated
migration of users and their resources together.
Migrate all resources to Exchange at the beginning, with the first user
group, and tell all not-yet-migrated users that they may no longer
request resources via GroupWise. In the meantime, designate an

already-migrated user to serve as a Resource Coordinator in
Exchangeto manually relay resource requests from GroupWise
users to Exchange resources, and manually relay resources replies
back to the GroupWise users.
Strategies for Migrating Groups (Distribution Lists)

When a group is provisioned into AD, it also remains on the GroupWise server
(that is, the GroupWise original is copied, not destroyed or altered), and after its
migration the two groups exist independently of each other. This coexistence
introduces the potential for discrepancies between the two group membership
lists, as group members may be added and deleted during the transition period.
You can re-run the Directory Exporter and then the Admin-Driven Batch Migrator
to update the AD groups membership lists with any changes entered into the
GroupWise originals, but there is no practical mechanism for updating in the
opposite direction, from AD back to GroupWise.
Since the only practical update path for groups is one-way, most organizations
choose to defer provisioning their groups into AD until the very end of the
transitionafter all users have been migrated. This approach eliminates the
need for periodic updates, and already-migrated users can address emails to
groups defined in GroupWise the same (transparent) way they send emails to
not-yet-migrated users. This approach also is likely to generate more traffic
across the Microsoft Connector, which will increase as more and more group
members migrate to Exchange. Some admins may want to avoid that added
burden on the Connector, but the alternative is to provision the groups into AD
at the outset (or whenever), and then:
Run frequent synchronizing updates thereafter, throughout the

transition period: Re-run the Directory Exporter and then the
Admin-Driven Batch Migrator to update the AD groups membership
lists. (The more current the AD group definitions, the less traffic will
be passed through the Connector.)
Accept inconsistencies between the GroupWise and AD groups.
OR
It is also conceivable, depending on how groups are managed within a particular

organization, that groups could be primarily maintained in AD, which would
require a manual groups-updating procedure from AD back to GroupWise
throughout the transition period.
Your Migration Plan should identify which of these strategies is best suited to
your organizations needs and preferences.
35
Accommodating Known Limitations of the

Migration Process and Other Special Circumstances
Review the Known Limitations of the Migration Process (in Appendix F of this
Guide), and determine how you will accommodate any that apply to your
organization. Most or all may be insignificant to you, while some may require
more elaborate strategies or work-arounds to mitigate their effects.
Identify any other aspects of the configuration that will require variations or
extensions to the typical migration process described in chapter 2, and that are
not already discussed among these Strategic Planning Issues. Quest applications
offer operational options that permit considerable flexibility in devising and
implementing a suitable migration strategy wherever the circumstances of a
given site require a non-standard approach. For information and help with any
non-standard scenarios, please contact your Quest sales representative.
Migrating from an Older Version of GroupWise

GroupWise Migrator for Exchange supports GroupWise versions 5.5.3 to 7.0. If
you want to migrate to Exchange from an earlier version of GroupWise, you must
perform a two-step migration with an intermediate server running a later version
of GroupWise:
1.
Establish a GroupWise server of a supported version on a new machine.
2.
Use Novell GroupWise upgrade tools to migrate your users and their
data from the original pre-5.5.3 GroupWise server to the new,
supported-version GroupWise server.
3.
Decommission the original pre-5.5.3 GroupWise server.
4.
Establish a new Exchange server, either on a new machine or on the

computer that previously hosted the pre-5.5.3 GroupWise server.
5.
Migrate from the new, supported-version GroupWise server to the new

Exchange server.
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. The end users will need to know:
36
When and how they will be migrated.

How the migration will affect them.
What tasks will be required of them to complete the migration.
What their login credentials will be on the new Exchange server.
How to use Outlook and Exchange (end-user training).
Your Migration Plan should therefore explain how and when you will deliver this
information to your users. Many administrators compose a notification email to
include this 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 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 casea test or pilot migrationthe 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's Log File Viewer application
will help you view and interpret the program log file. See Appendix B, Log File
Viewer, 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 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."
37
38
2
Migration Process
Instructions
Process Introduction
Necessary Pre-Migration
Preparations
Batch Migration Process (Per User
Group)
Migration Per Desktop
Post-Migration Clean-Up
Process Introduction
This chapter provides instructions for how to accomplish the most common
migration strategies and scenarios, using GroupWise Migrator for Exchange
components in conjunction with Quests NDS Migrator, and Microsofts
Connector and Outlook deployment tools. These instructions assume that you
have already prepared a comprehensive written Migration Plan, as described in
chapter 1 (see Pre-Migration Planning and Testing).
The task checklists here explain the contexts in which the Quest applications are
used. Wherever these procedures call for components of GroupWise Migrator for
Exchange, the scenario-oriented instructions here refer to tool-specific
operational details in chapters 3 and 4, and in the appendixes.
The four remaining sections of this chapter correspond to the phases of a
migration process:
1.
Necessary Pre-Migration Preparations
2.
Batch Migration Process (Per User Group)
3.
4.
If your migration strategy does not include either a batch-migration process or

any per-desktop migrations, just skip the unnecessary section.
Necessary Pre-Migration
Preparations
This section explains how an administrator should prepare for a migration of
any type: administrator-driven batch migration, either by password or by proxy,
or per-desktop migrations either by end users or by administrators acting on
behalf of end users. These preparatory tasks are performed just once, before the
first user group or first single user is migrated.
Since these instructions cover a range of scenarios, not all steps will apply to all
migrations. These conditional steps are clearly identified here, and of course you
may simply skip any steps that dont apply to you.
The process begins with existing user accounts and mailboxes on a Novell
GroupWise server, version 5.5.3 to 7.0.
40
Migration Process Instructions
Step 1:
Verify that All System Requirements Are Satisfied
All of the system requirements documented in chapter 1 (see About GroupWise
Migrator for Exchange, System Requirements) must be satisfied before you
begin this process.
Also, if you havent yet installed the GroupWise Migrator for Exchange software,
run Quests Setup program to install it now. If necessary, see Installing
GroupWise Migrator for Exchange in your Quick-Start Guide for complete
instructions.
Step 2: Prepare the

Addproxy Program to Establish User Proxies
This step 2 applies only to administrator-driven batch migrations by proxy.
If the program will access GroupWise source data by password, or as a
Trusted App, skip ahead to step 3. If you arent sure, go back to chapter 1
and read the Pre-Migration Planning topic Method of Access to GroupWise
User Data by Password or by Proxy.
If you will use the proxy-access method: Prepare Quests Addproxy program to
establish proxy access to each users account, and modify the network login
script of your migrating users to run the Addproxy program when they next
login. For complete instructions see Appendix A: AddProxy Utility.
Step 3:
Create a Temporary Subdomain for the Migration
Create a temporary MX subdomain for the migration (e.g., migrate.domain.com)
and specify it in DNS. The subdomain should direct traffic to the new Exchange
environment. Mail from other GroupWise users arriving in the GroupWise
accounts of migrated users will be forwarded to the appropriate mailboxes in the
Exchange environment using the migrate.domain.com subdomain.
Step 4: Create a
Recipient Policy for the Temporary Subdomain
Create a recipient policy to generate a secondary SMTP address so all Exchange
users will be able to receive mail at the migrate.domain.com subdomain.
41
Step 5:
Provision Active Directory with NDS Users and Groups
Provision NDS users and groups as security objects and security groups,
respectively, in Active Directory. Quests NDS Migrator (a separate Quest
product, not part of GroupWise Migrator for Exchange) offers the most complete
migration capabilities for this task, but other methods are also possible.
In step 8 below you will run Quests AD Object Merge Tool to mail-enable these
accounts, but the AD Object Merge Tool cannot be run until after the Directory
Exporter has run.
Step 6: Run Quest's Directory Exporter

The Directory Exporter extracts user data from the GroupWise environment to
create the data files required by other Quest applications. Run the Directory
Exporter now, to generate the necessary data source files. For more information
and complete operating instructions for the Directory Exporter program, see
chapter 3: Directory Exporter.
Step 7:
Review and Modify (If Necessary) the Data Files
Since the data files generated by the Directory Exporter (in the preceding step)
are necessary input files for other Quest programs, it is important to verify that
the information is properly formatted. This step also provides an opportunity to
manually edit any addresses before initiating the migration. For example, the
files may be modified to facilitate the organization's consolidation on a new SMTP
domain as part of the migration process. See Review and Modify (If Necessary)
the Data Files at the end of chapter 3 for more information about verifying and
editing the contents of these files.
Step 8: Mail-Enable All Users AD Accounts

Run Quests AD Object Merge Tool to update and mail-enable the new Active
Directory accounts, which will facilitate Exchange-to-GroupWise mail-routing
throughout the transition period for not-yet-migrated users.
The AD Object Merge Tool will apply its functions to AD accounts identified in a
UsersToMerge.csv file that is specified during the program run. For each user
listed in the file, if an Exchange Contact address matches the GroupWise
SourceAddress in UsersToMerge.csv, the program merges the GWISE and SMTP
aliases from the Contact into the AD security object, and then deletes the
Contact, to consolidate the pair into a single mail-enabled security object. If no
such corresponding Contact exists, the program simply merges the
42
SourceAddress from UsersToMerge.csv into the AD security object, to

mail-enable the object. See Appendix B, AD Object Merge Tool, for more
information and operating instructions.
Step 9: Provision Public Distribution Lists in Exchange

Run the Administrator-Driven Batch Migrator to provision GroupWise public
distribution lists (PDLs) as Exchange distribution groups. The program reads a
data file generated by the Directory Exporter, GroupsToProvision.abk, to
provision PDLs in Exchange. PDLs are typically provisioned in Exchange
separately, before users are migrated in later runs of the same program, in
Batch Migration Process (Per User Group) below. For operating instructions and
application notes, see chapter 4, Administrator-Driven Batch Migrator.
Step 10: Modify the MX Record

Modify the MX record to direct external (Internet) mail to the Exchange server.
With the forwarding capabilities of GroupWise Migrator for Exchange, the DNS
modification actually can occur any time after the users AD accounts have been
mail-enabledbefore, during or after the actual migration. But since users AD
accounts are initially set to route mail back to the corresponding GroupWise
mailboxes, many organizations find it most appropriate to modify the DNS
before initiating user migrations.
Step 11: Set RemoveSrcAddresses=1 in gwmigapp.ini

Use a text editor to open and edit your gwmigapp.ini file, to set:
[ActiveDirectory]
RemoveSrcAddresses=1
The Batch Migration Process (Per User Group) process includes a directory
synchronization (via Microsofts Exchange Connector for GroupWise) that will
function properly only if the Quest program first removes all GroupWise source
addresses (gwise:proxy-Addresses), so that mailbox-enabled accounts in Active
Directory can be synchronized back to GroupWise as external users. If
RemoveSrcAddresses=0 (default), only the gwise:uid- address is removed.
Step 12 (If Necessary): Move Users Archives and

PABs to a Centralized, Accessible Location
The Administrator-Driven Batch Migrator can migrate users GroupWise archives
and personal address books (PABs) to Exchange, but only if the program can find
the source archives and PABs on the GroupWise server. The program can also
migrate archives and PABs from diverse, per-user locations, but only if you
43
specify the location for each user in your user-list .csv file as explained in step
2 of the Batch Migration Process (Per User Group) procedure below.
If your GroupWise network is not already configured for your users archives and
PABs to reside in centralized, accessible locations, and if you do not want to have
to specify their diverse locations per user in the user-list .csv file, you (or your
users) should move them now, before you run the Batch Migrator program.
Batch Migration Process

(Per User Group)
Remember that batch migrations and per-desktop migrations are performed
with different Quest tools. For the per-desktop migration procedure, see the
Migration Per Desktop section of this chapter below.
This section provides information and procedural instructions for a typical
migration scenario, in which an administrator performs the migrations for
multiple groups of users with no user interaction. These instructions for batch
migration scenarios describe the process for both methods of access to user data
by password or by proxy.
Do not begin this procedure until you have completed the Necessary
Pre-Migration Preparations listed in the preceding section of this chapter.
Repeat these steps for each group of users to be migrated:
Step 1: Accommodate Any Recent Staff Changes

Most migration projects extend over a period of at least several days, many for
several weeks or even months. It is entirely possible therefore that an
organization will experience staff additions and departures during the transition
period. Any staff changes that occur while the migration project is in-process
may introduce data inconsistencies between the old and new servers, but these
inconsistencies can be reconciled during the migration process.
If maintaining synchronization between the two directories during your
transition period is not a high priority for your organization, you may simply add
and delete users in the Exchange environment (only), using Exchange
administration software the same as you will for new hires and departures that
occur after the migration is completed.
Otherwise, if it is important to keep the two directories synchronized through the
transition, and if the organization has experienced any staff additions or changes
since the last run of the Directory Exporter:
44
Enter any such staff changes within the GroupWise environment as

they occur, just as you always have.
If any already-migrated user leaves the organization: Delete the user

from the Exchange server, using Exchange administration software.
Prior to the migration of each user group:
Run Microsofts Exchange Connector for GroupWise to re-synchronize

the directories, from GroupWise to Exchange. (You need not perform
this step explicitly if the Connector is scheduled to automatically
re-synch the directories at regular intervals.)
Re-run Quest's Directory Exporter to generate new, updated .csv files
that will accurately reflect the current staff list. (Remember to review
the new .csv files and, if necessary, edit them, as explained in chapter
3 of this Guide).
Step 2: Prepare a Migration Group User-List .csv File

Quests Administrator-Driven Batch Migrator uses a .csv file as input to specify
the subset of users who will migrate together in the current migration batch or
round. How you should prepare your user-list .csv file depends on whether the
program will access users GroupWise accounts by proxy, or by password (see
the chapter 1 Pre-Migration Planning topic Method of Access to GroupWise User
Data by Password or by Proxy). The next two subsections below explain how
to prepare the user-list .csv file for both methods.
Preparing a User-List .csv File for the Password-Access Method

If you will access users GroupWise accounts by password, you can copy and
adapt the user-list .csv file from the UsersToMigrate.csv that you created and
(optionally) edited in steps 6 and 7 of the Necessary Pre-Migration Preparations.
To prepare the user-list file, use Microsoft Excel to:
1.
Open UsersToMigrate.csv and Save As to a new .csv-format

filename (for example, migr01.csv for the first migration group, or
migrmktg.csv for the users in the Marketing Department). You must
save the file in .csv format, not as an Excel Workbook or any other
file type.
2.
Edit the copy by deleting all users except the ones you want to
include in this migration group.
3.
If you intend to access users GroupWise data by resetting

their passwords to values in the .csv file (see the chapter 1
Pre-Migration Planning topic Method of Access to GroupWise User
Data by Password or by Proxy): Add a Password column to the
.csv file, and enter each users password value into this column.
45
4.
See Other Modifications to the User-List .csv File below for a list of
special circumstances and optional features that may require further
modifications to the user-list .csv file.
5.
Save the modified .csv file in CSV format under its new name, and
exit Excel.
Preparing a User-List .csv File for the Proxy-Access Method

If your Administrator-Driven Batch Migrator program will access users
GroupWise data by proxy, you can use the .csv file generated by Quests
Addproxy program as your user-list file. Appendix A explains how each
successful run of the program, per user, generates a record of the user in a file,
designated in your addproxy.ini file as the SuccessLog. This file thus contains a
current list of all users who have granted the necessary proxy rights, and are
thereby eligible for migration by proxy. The Addproxy program is designed to
format the log as a .csv file that can be read by Quests Administrator-Driven
Batch Migrator.
Be sure to see Other Modifications to the User-List .csv File below for a list of
special circumstances and optional features that may require further
modifications to the user-list .csv file.
Quests Administrator-Driven Batch Migrator will prompt you for a user-list .csv
input file, and you may simply specify the Addproxy log file for this purpose. But
in migration-by-proxy you must also determine which (if any) users were
prepped to run Addproxy but never ran it that is, users who have not logged
out and back in again since the Addproxy line was added to their login scripts.
Any users who do not appear in the log file even though they were prepped to
run Addproxy will have to be migrated separately at a later time.
Provisioning Users to Multiple Exchange Mailstores

Some administrators may want to provision users in the same user-list .csv file
to two or more different Exchange mailstores. The Admin-Driven Batch Migrator
program can do that, but in this case will need to know the users individual
destination mailstores. The HomeMDB column of the user-list .csv file can be
used for that purpose.
The HomeMDB column specifies the home mailbox store in Exchange for each
migrating user, and is used when mailbox-enabling users in the Exchange
Administrative Operations of the Admin-Driven Batch Migrator. Example:
CN=Mailbox Store (MOBE),CN=First Storage Group,CN=InformationStore,
CN=MOBE, CN=Servers,CN=First Administrative Group,CN=Administrative
Groups,CN=User,CN=Microsoft Exchange,CN=Services,CN=Configuration,
DC=Example,DC=com
46
Note that the Exchange admin credentials for the Admin-Driven Batch Migrator
must have sufficient rights to create mailboxes on the Exchange server(s)
specified in this HomeMDB column. If the HomeMDB column is left blank, the
program will infer a suitable default value for all users from the admin's GUI
entries defining the destination Exchange server.
Other Modifications to the User-List .csv File

Some circumstances and optional features may require other additions to the
user-list .csv file. Contact Quest Technical Support (support@quest.com) for
more information if any of these circumstances apply to you:
User archives are on a central accessible server, but reside in diverse

directory subtrees such that the lowest common subtree root for all
archives contains a large volume of data. (In the user-list file you can
specify a lower-level root, per user, so the program will not have to
scan the entire common subtree repeatedly, for each users data.)
You want user PST files in Exchange to reside in different, separate

directories, per user (for example, in each users home directory).
You want to migrate forwarding addresses from the GroupWise

source.
You want the batch-migration program to change users GroupWise

passwords to a different value for each user, rather than to a single
common value for all users, or to random strings of characters.
Step 3: Run Quest's Administrator-Driven Batch

Migrator to Perform Administrative Functions
Run the Administrator-Driven Batch Migrator to perform these administrative
functions for the users identified in the .csv file:
Mailbox-enable Exchange accounts.
Change the GroupWise passwords for migrating users (if you are
using password access rather than proxy access for GroupWise data).
Set users' visibility to None in the GroupWise directory.
Update mail-forwarding rules for groups of migrating users.
Note: If you are migrating from GroupWise 6.5, or from GroupWise 5.5.3 or
higher with Outlook 2003 clients, you must run the Administrator-Driven Batch
Migrator twice for this step: first to mailbox-enable the Exchange accounts, and
then again for the other administrative functions listed above.
See chapter 4, Administrator-Driven Batch Migrator, for complete instructions
and application notes.
47
Step 4: Synchronize the Two Directories

Before you run Microsofts Connector, run RUS (Recipient Update Service) to
update the users AD records with their GroupWise addresses. The Connector
synchronization will not work properly until those AD records are updated.
When the AD records are updated, run Microsofts Exchange Connector for
GroupWise to perform a reverse synchronization of the two directories, from
Exchange back to GroupWise.
Step 5: Run Quest's Administrator-Driven Batch

Migrator to Migrate User Data
Run the Administrator-Driven Batch Migrator again, to migrate user data from
the GroupWise server to the Exchange environment, for the users identified in
the .csv file. See chapter 4, Administrator-Driven Batch Migrator, for complete
instructions and application notes.
Step 6: Distribute .pst Files (If Any)

If any data has been migrated to Outlook personal folder (.pst) files, then when
the migration is complete the administrator must either:
Notify users of the locations of their new.pst files (so each user can
specify the location within his or her own desktop copy of Outlook).
OR
Distribute the newly created .pst files to users desktops.
Quest's Administrator-Driven Batch Migrator program names any new .pst files
by their associated User IDs, with incrementing numbers appended to the
filename if more than one file is generated per User ID for example, Smith.pst,
Smith-1.pst, Smith-2.pst, and so forth.

Remember that batch migrations and per-desktop migrations are performed
with different Quest tools. For batch migration (multiple users at a time,
performed by an administrator), see the preceding section of this chapter: Batch
Migration Process (Per User Group).
Quests Self-Service Desktop Migrator is used by an end user, or by an
administrator on behalf of an end user, to extract a single users GroupWise data
48
and migrate it to Exchange. Depending on your circumstances and preferences,

you may choose to migrate some or all of your users one at a time, from each
users desktop, using the Desktop Migrator. For example, some administrators
prefer the per-desktop tool to migrate user archives when the archives reside on
users individual workstations, where that option seems easier than prepping the
user-list .csv file with per-user values for the locations of all the local archives.
The choice between an admin or end users running the per-desktop tool also
depends on local circumstances. Some administrators prefer running the
Self-Service Desktop Migrator themselves to ensure a smooth transtion for top
executives, or for less experienced end users who might be uncomfortable trying
to run the tool for themselves.
Customizing the Self-Service Desktop Migrator

Quests Self-Service Desktop Migrator is simple and intuitive enough that most
end users will be able to run it uneventfully. Some administrators simplify the
process even more by customizing the per-desktop program to enforce or
eliminate certain choices in accordance with a particular migration strategy. For
example, if an administrator intends to migrate users server mail and address
books in batches, and then use the Desktop Migrator to migrate only user
archives, the per-desktop program can be customized to migrate only archives,
and to not offer the options to migrate server mail or address books.
These program customizations are optional, accomplished by manipulating
certain parameters in the gwdtapp.ini file, as explained in Appendix D of this
Guide: Customizing the Self-Service Desktop Migrator Program. If you leave
those parameters at their default values, the Desktop Migrator simply runs in its
default mode, displaying all screens and all options.
Before Running the Self-Service Desktop Migrator

Be sure to complete all of the Necessary Pre-Migration Preparations (first section
of this chapter), before the first desktop migration is performed. These
preparatory tasks are performed just once for all usersnot once for each user.
Also, an update of the .csv data files may be necessary if any users have joined
or left the organization since the last run of the Directory Exporter. For more
information about updating these files, see Step 1 of the preceding Batch
Migration Process (Per User Group) section.
Distribution of Self-Service Desktop Migrator

Program
Your end users will need access to the Self-Service Desktop Migrator program.
The most common methods of distribution are:
49
Share out the end-user directory that was created during the
installation process.
Copy the contents of the end-user directory to another location and

share it. If the AddressTranslation.csv and AddressTranslation.bin
files have been updated, you must also update the new directory with
copies of the updated files.
Burn the contents of the end-user directory to a CD. Remember, if the

AddressTranslation.csv and AddressTranslation.bin files have been
updated, any such CD must be replaced with a new version containing
the updated versions of those files.
Notifications to End Users

If your users (rather than you) will run the Self-Service Desktop Migrator, you
will need to tell them where the program file is, and provide operating
instructions for how to run it. Typically, an administrator will send an email to
migrating users with a link to the Desktop Migrator programat some network
location accessible to all usersso each user can simply click the link in the email
to launch the program.
You should also include a copy of the Self-Service Desktop Migrator User Guide
(in PDF format), which explains how to operate the per-desktop program from
the end users point of view. The Desktop Migrator User Guide accompanies your
GroupWise Migrator for Exchange software. You may either copy the PDF file to
a public-access folder and link to it from the same email that announces the
Self-Service Desktop Migrator program to your users, or simply add it to the
email as an attachment.
Command-Line Switches for

Running the Desktop Migrator in Silent Mode
The Self-Service Desktop Migrator can be customized to skip certain screens, or
even to hide all screensto run in a true "silent mode," requiring no entries or
other intervention from the end user. Whenever the program is configured to
skip a screen display, the program must have some alternate method of
obtaining the information it would otherwise collect from fields on the screen.
The program can read and/or infer some entry values from the operating
environmentfrom the Windows Registry and Outlooks initialization files,
etc.and some values can be specified by parameters in the gwdtapp.ini file. But
some values can also be provided by command-line switches appended to the
program command when the Desktop Migrator is executed. For example:
gwdtapp /silent /userid AbeLincoln /pass 4score ....
50
In this list of all available switches for the gwdtapp command, note that the
/silent switch is the only one that does not carry an argument:
/silent: Enforces a true"silent" run of the programfor no screen

displays at all. The program will note errors in its log and may abort
if it requires input data that is not made available via other switches
(see below) or INI-file parameters, and that cannot be inferred from
the operating environment.
/userid <UserID>: The users GroupWise UserID.
/pass <GWPassword>: The password associated with the UserID

cited above.
/tgtprofile <ProfileName>: The Outlook profile that you want to

migrate the one into which your GroupWise server data, archive
and/or personal address books should be placed.
/tgtpass <OutlookPassword>: The password associated with the

target Outlook profile cited above.
/tgtdomain <DomainName>: The domain name of the target

Exchange mail server.
/tgtuser <ADUserName>: The AD user name associated with the

Outlook profile cited above.
For more information about using the gwdtapp.ini file to control screen displays
and provide necessary run-time information to the program, be sure to see
Appendix D: Customizing the Self-Service Desktop Migrator Program.
If a User Does Not Appear To Be Migrated

(After Running the Self-Service Desktop Migrator)
One of the customization options for the Self-Service Desktop Migrator program
is to make some of its screen displays "silent"that is, invisible to the end user.
In that case, ordinarily the gwdtapp.ini file is further modified to provide to the
program whatever information the "silent" screen would otherwise collect from
the user. But if the program cant find that information in the .ini file, and if the
screen that ordinarily collects it has been hidden, the function will fail and the
users data will not be fully migrated. This is a likely cause of any failed or
incomplete single-user migration if the gwdtapp.ini file has been modified to
make one or more screens "silent."
If necessary, see Appendix D for more information about Customizing the
Self-Service Desktop Migrator Program by setting parameters in the gwdtapp.ini
file.
51
To "clean up" after the last user has been migrated
52
1.
Verify the GroupWise server is inactive. Make sure that the

GroupWise server is no longer receiving or processing mail traffic.
2.
Delete the temporary "migrate.domain.com" MX domain. This

is the temporary MX subdomain you created in step 3 of the
Necessary Pre-Migration Preparations, to permit mail-forwarding
between the old and new servers during the migration. Now that all
users have been migrated to the Exchange server and new mail is
directed to the new Exchange mailboxes, the mail-forwarding rules
and temporary subdomain are obsolete.
3.
Decommission the GroupWise server. After you have verified

that the GroupWise server is no longer receiving or processing mail
traffic, you may decommission the environment.
3
Directory Exporter
About Directory Exporter
Operating Instructions
Review and Modify (If Necessary)
the Data Files
About Directory Exporter

Quests Directory Exporter gathers user information from the GroupWise server
to create four data files that will later provide critical input data to the Quest
migration and PDL-provisioning programs:
GroupsToProvision.abk: Contains the information about GroupWise

public distribution lists (PDLs) that the Administrator-Driven Batch
Migrator will read to provision the PDLs in Exchange as distribution
groups.
UsersToMerge.csv: Contains the information the AD Object Merge

Tool will need to merge Exchange Contacts into corresponding Active
Directory accounts, to create a single mail-enabled security object per
user in AD.
AddressTranslation.csv: Contains the display names, GroupWise

addresses, and primary Internet addresses of your GroupWise users.
Quests migration programs both the Administrator-Driven Batch
Migrator and the Self-Service Desktop Migrator use the information
in AddressTranslation.csv to convert addresses in messages, address
books, and frequent contacts to the appropriate Internet address for
each user.
UsersToMigrate.csv: A duplicate of AddressTranslation.csv, to serve

as a template for the creation of the user-list input files that identify
which users to migrate in a particular run of the Administrator-Driven
Batch Migrator. (The UsersToMigrate.csv is copied to another file
name, and the copy is then edited deleting all users except the ones
to be included in a particular migration group.)
The Directory Exporter program is therefore run before the first run of any Quest
migration program or the AD Object Merge Tool, because the Directory Exporter
generates the data files that these other programs require to perform their
functions. Then, throughout the transition period, the Directory Exporter is
re-run as necessary to update the programs data files, to accommodate any
staff changes that are recorded in GroupWise during the transition period.
54
Directory Exporter
Start the Directory Exporter program from your computers Start menu, in the
GroupWise Migrator for Exchange program group. To use Directory Exporter:
1.
Review the Welcome screen and click Next.
2.
Enter the requested GroupWise information and click Next.
Admin user ID: The name of the admins GroupWise account (not the
Novell account).
Admin password: The password for the admins GroupWise account
(not the Novell account).
GWIA TCP/IP hostname: The hostname of the GroupWise Internet
Agent LDAP server. This must match the Hostname/DNS A Record
55
name GWIA setting. You can find this path in the NetWare
Administrator program, NWAdmin or ConsoleOne: From the Tools
menu, select GroupWise View..., and then select the GWIA object
from the GroupWise Domain object. From the Object menu, select
Details ..., and then in the GWIA dialog box click SMTP/MIME
Settings. The displayed property page then shows the value for the
Hostname e.g., gwia.acme.com.
GWIA LDAP Context: This value is the same as the GroupWise
Internet Agent setting. If necessary you can find this path by using the
NetWare Administrator program, NWAdmin or ConsoleOne: From the
Tools menu, select GroupWise View..., and then select the GWIA
object from the GroupWise Domain object. From the Object menu,
select Details ..., and then click LDAP Settings. Use the value found
in LDAP context (Search Root or Search Base) for example:
o=acme,c=us.
Domain path: The file system path to your GroupWise domain file
wpdomain.db. If necessary you can find this path by using the
NetWare Administrator program, NWAdmin or ConsoleOne: From the
Tools menu, select GroupWise System Operations ..., and then in
the dialog box click System Connection. The System Connection dialog
box then displays a list of GroupWise domains; the one labeled as the
primary domain (format \\NWSERVER\SYS\MAIL\GWDOM) is the
value you need to enter for the Domain Path in this Directory
Exporter screen.
When you click Next, the Status screen reports the program's
progress while the export process is running, and the program
automatically advances to the next screen when the process is
finished.
56
Directory Exporter
3.
Note the location of the program files and click Exit.
This Finished screen may also offer an Error Log Report button (not
shown here) if the Directory Exporter encountered any errors during
the program run. If the Error Log Report button does appear, you
should click it to view the program log and assess the severity of the
errors. The Error Log Report button launches Quests Log File
Viewer utility (explained in Appendix D) to help you interpret and
resolve the errors or warnings.
Review and Modify (If Necessary)

the Data Files
Since the data files generated by Quests Directory Exporter are critical input
files for other Quest programs, it is important to verify that the information they
contain is properly formatted. GroupsToProvision.abk is a simple text file that
you can open with any text editor to see if it contains any obvious format or
translation errors. Examples include missing users, an empty column, exotic
characters, or inappropriate data forms in any fields. These would indicate that
the extraction process was somehow corrupted or otherwise unsuccessful.
All three .csv files contain essentially the same data, so you can open any one
.csv file to look for the same sorts of format or translation errors. A .csv
(comma-separated values format) file is also a text file that can be opened and
edited in a text editor, but you may prefer Microsoft Excel or some other
spreadsheet or database application that can display the contents of a .csv file
in an easy-to-read column format.
This post-export review is also a chance for you to manually edit any addresses
in the .csv files before performing the actual migration. For example, a particular
user name and address-composition format may produce an embarrassing or
57
unflattering address, but you can manually edit the address in the .csv files
before the files are used to define user addresses in the new Exchange
environment. If you do decide to edit any addresses in the .csv files, remember:
58
Before you edit any values, copy the entire TargetAddress column
contents into the TargetAlias column, and enter your changes only in
the TargetAddress column.
If you edit any of the .csv files, be sure to copy the new file to
the other two filenames. The three .csv files usually must have
identical contents (with one small exception, noted below). If you edit
one, you should replace the others with copies of the edited file. Then:
If you have copied either of the other two .csv files to

UsersToMerge.csv: Open UsersToMerge.csv and add a new column
titled SearchKey.
4
Administrator-Driven
Batch Migrator
Overview
Per-Screen Instructions and
Application Notes
Remember to Distribute Any User
.pst Files
Overview
The Administrator-Driven Batch Migrator is a multi-function application that lets
you perform various functions in various combinations in a single program run.
Certain screens in every program run ask you what you want to accomplish. The
program then proceeds through a linear sequence of screen displays, skipping
any screens that do not pertain to the functions you have selected. Available
program functions are grouped into four categories:
GroupWise Administrative Functions:
Remove forwarding
Set forwarding
Set user password
Set user visibility
Exchange Administrative Functions:
Set forwarding
Remove forwarding
Mailbox-enable existing Active Directory accounts
Migrate Users: Migrates user dataany combination of

server-based or archived mail, calendar data, or the trash folder, or
personal address booksfrom GroupWise to Exchange.
Provision Distribution Groups: Copies GroupWise public

distribution lists (PDLs) into Active Directory.
In a typical migration scenario the Administrator-Driven Batch Migrator is run

once to migrate public distribution lists (PDLs) before its first run to migrate the
first user group. Then, for each migration group, the program is run twice: first
to perform administrative functions, and then again to migrate the user data. In
the Migration Process Instructions (chapter 2), the migration of PDLs occurs at
step 9 of the Necessary Pre-Migration Preparations, while the administrative
tasks and user migrations occur at steps 3 and 5 of the Batch Migration Process
(Per User Group).
The instructions in this chapter cover all uses of the program, and begin with the
assumption that certain prerequisites have been satisfied, as described in the
Necessary Pre-Migration Preparations in chapter 2.
To start the Administrator-Driven Batch Migrator program
60
1.
Start Quests Administrator-Driven Batch Migrator program from the

GroupWise Migrator for Exchange Start menu.
2.
See the instructions and application notes below for the programs
Welcome screen (screen #1). Then refer to the instructions and
notes for other screens as they occur in the program sequence.
Administrator-Driven Batch Migrator
Per-Screen Instructions
and Application Notes
The numbers associated with the screens described here indicate the screens
relative positions within the overall program sequence. These are not step
numbers, as in a numbered-step procedure, because the program will skip
screens that do not pertain to functions you have chosen for the current program
run. We number the screens simply for convenient reference, but no single
program run would ever include all of the screens.
1: Welcome Screen
Review the Welcome screen and the displayed license information.
If you have obtained a more recent program license key than the one identified
here, you may click Update your license key to update that information and
upgrade or extend your use of this program. If you do choose to Update your
license key, the program will return you to this screen after you have entered
the new license information.
When you are ready to begin the substance of this program run, click Next.
61
2: Select Operations
Mark the categories of operations you want the program to perform during this
run, and click Next.
Technically you can Provision distribution groups (PDLs) in the same

program run with the other data-migration and administrative functions listed on
this screen. But PDL provisioning in the same run with these other features can
be an unnecessary complication of project planning and execution, and Quest
therefore recommends against it unless you have some compelling strategic
reason to use the program in this way. Our Batch Migration Process (Per User
Group) in chapter 2 suggests that you Provision distribution groups in a
separate program run, before you migrate the first user group.
Similarly, Quest recommends that GroupWise and Exchange administrative
functions not be performed in the same program run as the migration of user
data. Instead, Quest recommends that you run the Administrator-Driven Batch
Migrator twice for each user group: first to perform the administrative functions,
and then again to Migrate users.
Note that the Provision distribution groups option appears grayed-out
(unavailable) here if the program cannot find the GroupsToProvision.abk file it
needs to provision the PDLs. That file is generated by the Directory Exporter, so
if the program cannot find the file it is likely that the Directory Exporter has not
yet been run. See the Necessary Pre-Migration Preparations in chapter 2 for
more information.
Your four options here:
62
Select GroupWise administrative functions if you want to perform any or all

of these functions:
Set or remove GroupWise-to-Exchange mail-forwarding rules.
Change users GroupWise passwords. (In our typical scenario, this is

how the program will access user data in GroupWise.)
Specify the scope of users visibility in the GroupWise directory.
Select Exchange administrative functions if you want to perform either or

both of these functions:
Set or remove Exchange-to-GroupWise mail-forwarding rules.
Mailbox-enable users Exchange accounts. (In our typical scenario,

users Exchange accounts will have been created by Quests NDS
Migrator and mail-enabled by the AD Object Merge Tool.)
Select Migrate users if you want to migrate user dataserver-based data,

and/or archives, and/or personal address booksfrom GroupWise to Exchange.
Select Provision distribution groups if you want to provision GroupWise
public distribution lists (PDLs) in the Active Directory. If you mark only this
option, then when you click Next you can skip ahead to screen #10 (the
intervening screens do not apply to this operation and will not appear).
3: Specify Users for Update

This screen appears only if you have chosen, on screen #2: Select Operations,
to perform GroupWise or Exchange administrative functions, or to Migrate
users.
63
Use the Browse button to locate and specify the user-list .csv file for this
program run (or just type the path and filename into the text box), and click
Next. This is the .csv file that you prepared in step 2 of the Batch Migration
Process (Per User Group), in chapter 2.
4: Select GroupWise Administrative

Operations
This screen appears only if the GroupWise administrative functions option
was marked on screen #2: Select Operations.
If that option was not marked, this screen (and several others) will not appear
and you may skip ahead to screen #9: Select Exchange Administrative
Operations. Otherwise:
Use this screen to specify which GroupWise administrative functions you want
the program to perform, for users in the associated user-list .csv file:
Set forwarding: Sets mail-forwarding rules in the users GroupWise mailboxes
to forward mail to their Exchange mailboxes, and disables any existing rules in
user mailboxes. The program will prompt you, in a later screen, for the server
information it needs to set these mail-forwarding rules, and another screen will
prompt you to specify any additional forwarding-related features you may want
to apply.
64
Remove forwarding: Deletes any migration-associated mail-forwarding rules

in the users GroupWise mailboxes. (This is a selective operation, to delete only
those rules associated with the migration, but not any other rules that may be
set for a given mailbox.)
Set user password: Tells the program to change users GroupWise passwords
to new values (to be specified in a later screen in this program). Select this
option only if you will use passwords to access user data for the migration.
(Leave this option unmarked if you will use the proxy-access method.)
Set user visibility: Lets you specify (in a later screen) the scope of users
visibility in the GroupWise directory. User visibility determines whether the MS
Connector will synchronize the GroupWise account into AD.
5: GroupWise Forwarding Options

This screen appears only if the Set forwarding option was marked on screen
#4: Select GroupWise Administrative Operations. Specify any of the additional
forwarding-related options listed on this screen that you want to apply to the
current group of users, and click Next.
Your selection of the Set forwarding option on screen #4 tells the program to
set GroupWise-to-Exchange mail-forwarding rules for all users in the user-list
.csv file you have specified for this program run. In addition to those
mail-forwarding rules, you may also apply one or more of these related features:
65
Set forwarding rule to auto-decline/delete forwarded messages: Tells

the forwarding server to automatically delete forwarded messages (and decline
meeting requests) as they are forwarded to the alternate address. (The
forwarded copies of messages and meeting requests are still sent to the
alternate address, but the originals are deleted from the server that forwards
them.)
Set forwarding rule to purge messages: Tells the forwarding server to
permanently delete all forwarded messages and meeting requests (rather than
leave them in the Trash where they may be recovered).
Add autoreply rule with forwarding rules: Tells the forwarding server to
automatically generate a standard reply to every message and meeting request
received and forwarded. The Subject line and message body of the autoreply will
be, respectively, the Autoreply Subject and Autoreply text specified below.
6: Specify Source-to-Target Mail

Fowarding Domain
This screen appears only if the Set forwarding option was marked on screen
#4: Select GroupWise Administrative Operations. Enter the information the
program needs to set forwarding rules in GroupWise mailboxes, and click Next.
66
Use the CSV field for forwarding: Use the drop-down list box to specify the
column in your user-list .csv file that contains the preferred form for users
target addresses. The program will form target-mailbox forwarding addresses by
combining the names in this column with the target domain as defined in the
API Gateway or SMTP settings below.
Quests Directory Exporter automatically generates columns and data in the
.csv file for three options in the drop-down list: TargetAddress, the
GroupWise Userid, and the Novell NdsUserName. If you want to use some
other addressing scheme, you must manually add a ForwardingAddress
column and appropriate per-user values to the .csv file before this program
run. The ForwardingAddress option will not appear in the list if no
ForwardingAddress column occurs in the .csv file.
API Gateway vs. SMTP

If you are using Microsofts Connector, you may choose to have mail forwarded
via the Connector (and API Gateway) rather than through a GWIA:
Use API Gateway for forwarding (Microsoft GroupWise Connector): Tells
the program to use API Gateway format addresses to direct forwarded mail from
GroupWise to Exchange. If you choose this option, you must also specify the
external Domain and Post Office that are linked to the Microsoft Connector.
Use SMTP for forwarding (GWIA):
SMTP Domain: The domain name assigned to the Exchange server

for the transition period of this migration. If you have assigned a
temporary MX subdomain to the Exchange server for this purpose (in
the Necessary Pre-Migration Preparations in chapter 2), enter that
subdomain here. Otherwise, if you have assigned a new domain name
to the Exchange server, enter the new domain name here.
Internet Addressing for the GroupWise server is either Enabled or

Disabled. If Disabled, you must also specify the GWIA Prefix in the
accompanying text box.
67
7: Specify GroupWise Passwords

This screen appears only if the Set user password option was marked on
screen #4: Select GroupWise Administrative Operations. Specify how you want
to change users GroupWise passwords, and click Next.
Set a single common password value for all users: Changes the users
GroupWise passwords to the common New password value specified below
(for all users listed in the associated user-list .csv file). The program will copy
this value to the Password column of the user-list.csv file, to facilitate the
migration process.
Set each users password to the corresponding value in the user-list
(.csv) file: Tells the program to use the password designated for each user in
the Password column of the associated user-list .csv file.
Set random passwords for all users: Tells the program to change each users
GroupWise password to a random string of 12 alphanumeric characters (random
and unique for each user), and to copy these new passwords to the Password
column of the user-list.csv file, to facilitate the migration process and document
the passwords for future reference.
68
8: Select GroupWise Visibility

This screen appears only if the Set user visibility option was marked on screen
#4: Select GroupWise Administrative Operations. Select one of the available
options here to specify the preferred scope of user visibility in the GroupWise
directory, and click Next.
GroupWise visibility options are:
None: User is not visible anywhere, and the user account will not get
synched to AD by the MS Connector.
System: User is visible to everyone.
Domain: User is visible only to other users in the same domain.
PostOffice: User is visible only to other users in the same PostOffice.
9: Select Exchange Administrative

Operations
This screen (sample on next page) appears only if the Exchange
administrative functions option was marked on screen #2: Select Operations.
Specify which Exchange admin functions you want the program to perform, and
click Next.
Set forwarding: Sets mail-forwarding rules in the users Exchange mailboxes,
to forward mail back to the corresponding GroupWise mailboxes. The program
will prompt you, in a later screen, for the server information it will need to set
these mail-forwarding rules.
69
Remove forwarding: Deletes any mail-forwarding rules in the users Exchange

mailboxes. If an earlier run of this program created Exchange mailboxes for
these same users, but did not fully migrate them, then their Exchange mailboxes
probably contain forwarding rules that this option will remove whenever you
migrate the rest of their data to Exchange.
Mailbox-enable existing Active Directory accounts: Creates a new
Exchange mailbox for every user in the associated user-list .csv file whose
Exchange account has already been mail-enabled, and for every security object
found in Active Directory. (This option will not, however, create a duplicate
mailbox for any user who already has a mailbox in any mail store.) In our typical
scenario, AD security principals are created by Quests NDS Migrator and
mail-enabled by the AD Object Merge Tool.
10: Specify Active Directory Information

This screen (sample on next page) appears only if the Exchange
administrative functions or Provision distribution groups option was
marked on screen #2: Select Operations. Identify the Active Directory server,
and provide the administrator credentials and other information the program will
need to manipulate Active Directory accounts, and click Next.
The last two fields may or may not appear grayed out (unavailable), depending
on whether you are migrating users or PDLs in this program run:
70
How users were loaded into Active Directory (only if you are
migrating users, not PDLs, in this program run): Use the drop-down
list box to specify the method by which user data was loaded into
Active Directory. In a typical migration scenario (as explained in
chapter 3), user data is loaded into Active Directory by Quest NDS
Migrator + Object Merge. If you are following that typical scenario,

select that option from the drop-down list box. Otherwise, use the list
box to specify the alternate method by which user data was loaded
into Active Directory.
Path to an existing organizational unit for distribution groups

(only if you are migrating PDLs, not users, in this program run): Type
the groups' OU path into the text box. Then, when you click Next, if
you are migrating only PDLs you may skip ahead to screen #21:
Specify GroupWise Domain Path (the intervening screens do not apply
and will not appear).
When you click Next from this screen, the program scans the associated
user-list .csv file and compares that information to your program entries to see
if it can identify any conflicts or other issues.
If no such problems are
apparent, the program
simply advances to the next
screen (skip ahead to the
next screen below). But if it
does find a problem, it
notifies you in the dialog
box shown at right.
71
Click the View button to see a .csv file listing of errors and warnings. The
program will save the .csv file to your Quest admin directory by appending
"-error" to the same filename as your current user list.
Review the list, and decide whether you want to continue or abort the program
run:
To continue the program run: In the User-list error dialog box,

click OK to dismiss the dialog box and advance to the next screen.
To abort the program run: In the User-list error dialog box, click
Cancel to dismiss the dialog box and return to the previous program
screen. Then click the Cancel button to abort the program run.
11: Specify Exchange Mailbox Information

This screen appears only if the Mailbox-enable ... accounts option was
marked in screen #9: Select Exchange Administrative Operations.
From the drop-down list boxes, select the locations of the Exchange mail Server
and of the Exchange Mailbox store, and click Next.
12: Specify Target-to-Source Mail

Forwarding Domain
This screen (sample on next page) appears only if the Set forwarding or
Remove forwarding option was marked in screen #9: Select Exchange
Administrative Operations. Enter the name of the domain or subdomain that is
assigned to your GroupWise server through the transition period of this
migration, and click Next.
72
This is the domain by which mail arriving in Exchange mailboxes can be

forwarded back to users GroupWise mailboxes. If you have assigned a
temporary MX subdomain to the Exchange server (as in our typical
scenariosee step 3 of the Necessary Pre-Migration Preparations in chapter 2),
then your GroupWise server probably still carries your original domain name,
and you should enter that original domain name here. If, on the other hand, you
have assigned a temporary subdomain to the GroupWise server for this purpose,
then enter that temporary subdomain here.
13: Specify Data for Migration

The Specify Data for Migration screen (sample on next page) appears only if the
Migrate users option was marked on screen #2: Select Operations. Specify the
data you want to migrate in this program run, and click Next.
This screen is designed to let you migrate email messages and calendar data
independently, from the server and/or from the archives:
Migrate server based data: Users' mail, appointments, and tasks located on
the GroupWise server will be migrated. For the migration of this sever-based
data, you may specify one or more of: Migrate e-mail messages, Migrate
calendar data, Migrate trash folder and/or Migrate Document
References.
Migrate archives: User archives that are located on a central file server will be
migrated. For the migration of archived data, you may specify one or more of:
Migrate e-mail messages, Migrate calendar data and/or Migrate trash
folder.
73
Migrate personal address books: Users' personal address books located on

the GroupWise server will be migrated.
File contacts as: Determines how the contacts are displayed in the
Contacts folder. The File As attribute is also used by Outlook to
alphabetize your Contacts. The three available options are:
74
Use Current Display Name: Use the Display Name attribute of the
address book entry.
First Last: Create the File As using the first name and last name
attributes separated by a space.
Last, First: Create the File As using the last name and first name
attributes separated by a comma.
Include Frequent Contacts with PABs: Tells the program to

migrate GroupWise Frequent Contacts from the GroupWise server into
a Frequent Contacts folder.
14: Select Date and Size Filters

This screen appears only if you have selected, on the preceding Specify Data for
Migration screen, to migrate server-based data and/or archive data. Select the
desired date and attachment size filter settings (if any), and click Next.
Mail dates: You may use date-based filtering to limit the amount of data that is
moved, or move all data.
Any date filters defined are applied only to mail and calendar items, and
not to users contacts. For example, if you use this feature to migrate
different date ranges of mail and calendar data in two or more successive
runs of the program, and if you have selected Frequent Contacts for
migration in two or more of the runs, the program will create an entire
duplicate set of contacts in the Exchange environment.
Attachment sizes: You may use size-based filtering to limit the amount of data
that is moved, or move all data. Migrating only attachments smaller than a
specified size will reduce the amount of disk space needed to create the new .pst
files or server database.
Even if you filter attachments based on size, all messages are migrated.
The filter excludes only attachments that exceed the size limit, but the
messages to which oversized attachments were attached are still migrated.
75
15: Specify GroupWise Information

This screen appears only if the Migrate archives option was marked in screen
#13: Specify Data for Migration. Use the Browse button to locate and specify
the root directory for your users' GroupWise archive files (or just type the value
into the text box), and click Next.
Archive root directory: The top-level directory where user archives reside.
Any archives to be migrated must be in this directory or its subdirectories. If
other locations (e.g., a different disk drive) also contain archives, you must
either rerun this program for each archive location, or run the Self-Service
Desktop Migrator program from each users desktop (or have your users run it).
16: Specify GroupWise Login Information

This screen (sample on next page) appears only if the Migrate users option was
marked on screen #2: Select Operations, or if the Set forwarding or Remove
forwarding option was marked in screen #4: Select GroupWise Administrative
Operations.
Specify the Login method (if necessary), and the GroupWise PostOffice Path
(if you want to access the GroupWise server via direct modesee below), and
click Next.
If the GroupWise source is version 6.5 or higher and you are not setting or
removing GroupWise mail-forwarding in this program run, the Login method
will not apply and will appear grayed-out. For more information about this
circumstance, see the Pre-Migration Planning topic Method of Access to
GroupWise User Data by Password or by Proxy, in chapter 1.
76
Login method (if offered): Select the appropriate option to indicate how the
program should access users GroupWise accounts:
Use proxy account: Tells the program to rely on proxy rights for access to users' accounts.
When the GroupWise source is 6.5 or higher: This option is available

only if the program will set or remove GroupWise mail-forwarding in
this program run. Enter the GroupWise user ID, Password, and the
associated Email address in either GroupWise or SMTP format, for
example:
User.GroupWisePO.GroupWiseDom
User@groupwise.com
These values pertain to whatever account will be used to set or remove
forwarding. You need not establish any proxy rights prior to the
program run.
When the GroupWise source is 5.5 or 6.0: Enter the GroupWise user
ID and Password of the admin account that has been granted proxy
rights for these migrating users' accounts. The Email address field
does not apply and therefore does not appear. The proxy rights must
already be established before this program run; the AddProxy Utility
(see Appendix A), can automate the process of obtaining proxy rights.
77
Use user passwords: This option is available only when the GroupWise source is version 5.5 or 6.0, and will be grayed-out when the
source is version 6.5 or higher. It tells the program to access users
GroupWise data by logging into their accounts individually. If you opted to Set user password (in screen #4: Select GroupWise Administrative Operations), the program will use the passwords specified in
screen #7: Specify GroupWise Passwords. If you did not opt to Set
user password, the program will use the passwords in the Password
column of the user-list .csv file.
Note that this option will appear grayed-out (unavailable) if you have
not told the program to reset user passwords, or if the program finds
no Password column in your user-list .csv file. (In this case, the
program would have no way of knowing user passwords, and
therefore would be unable to access accounts by passwords.)
Direct Connection (optional) / GroupWise PostOffice Path: This option lets

you tell the program to access the GroupWise server via direct mode rather than
via client-server mode, since direct mode is usually faster. If you leave this text
box blank, the program will default to whichever mode was last used to connect
to the GroupWise server. Otherwise, to require direct-mode access: Type your
GroupWise PostOffice Path into the text box, or use the Browse button to
locate and specify your GroupWise PostOffice Path.
If necessary you can use the NetWare Administrator program, NWAdmin or
ConsoleOne, to find the GroupWise PostOffice Path (above): From the
Tools menu, select GroupWise View ..., and then in the folder tree
expand the branch for the GroupWise domain name. Right-click on the
PostOffice name, and select Details. The displayed value for UNC Path is
your GroupWise PostOffice Path.
17: Specify Destinations for Migrated Data

This screen (sample on next page) appears only if the Migrate users option was
marked in screen #2: Select Operations. Specify the desired target location for
each category of migrated data, and click Next.
Archives: Archive data can be migrated to a personal folder (.pst) file or a
server-based mailbox. The default is to a .pst file.
Address books: Address book data can be migrated to a personal folder (.pst)
file or a server-based mailbox. The default is to a server-based mailbox.
Server-based data: Server-based data can be migrated to a personal folder
(.pst file) or a server-based mailbox. The default is to a server-based mailbox.
78
18: Specify How To Migrate Shared

Information
This screen (sample on next page) appears only if your entries on earlier screens
indicate that you intend to migrate shared folders and/or shared address books:
Enter the requested information to indicate your preferences for the migration
of shared items, and click Next.
A shared folder or PAB in GroupWise can be migrated either to its owner (only)
in Exchange, or to all of the users to whom the item was shared in GroupWise.
For each of Shared Folders and Shared Address Books, these two options
are mutually exclusive:
Migrate a separate copy ... for each user that has access
rights: Tells the program to migrate a separate copy of the shared
item for every user who had access to it in GroupWise. Note: If you
choose to migrate to each user that has access rights, the
program will migrate a complete copy for each user, and the multiple
copies will become independent of one another upon migration. That
is, any changes made to such a copy by User A will apply only to User
A's copy, and not to User B's or any other user's independent copy.
Migrate ... only for the owner: Tells the program to migrate only a
single copy of the item, to the user who owned it in GroupWise. If you
do choose to migrate only for the owner, you may also choose
either, both, or neither of these options:
79
Define Access Control Lists (ACLs) on the Exchange Server to

grant shared rights: Tells the program to read the GroupWise ACL
for each shared item, and recreate it in Exchange, so that the migrated
item will be re-shared with the same users who had access to it in
GroupWise.
Post a message that tells users how to open their shared
folders: Tells the program to post a message in the folder that was
shared, explaining how to open the shared item in Exchange. You can
modify the message template if you like:
Edit the message body: Opens the associated RTF template file for
editing, using whatever application is associated on your desktop with
RTF files (usually Microsoft Word). The template filenames are
SharedFolderNotificationTemplate.rtf and SharedPabNotificationTemplate.rtf. If you edit the template, be sure to save it as an RTF file
not as a Word doc file or any other file type.
Appendix E of this Guide explains How GroupWise Migrator for Exchange Maps
Shared Folders to Outlook.
80
19: Select Destination Exchange Server

This screen appears only if the Migrate users option was marked on screen #2:
Select Operations. Enter the information that will authorize (or forgo) the
programs connection to the Exchange server, and click Next.
Do not connect to an Exchange server: This feature makes possible the

migration of data to Outlook personal folder (.pst) files prior to the setup of your
Exchange server, but the checkbox will be available only if none of your entries
on earlier screens will require a connection to an Exchange server. (For example,
if you have told the program to create Exchange mailboxes, or to migrate any
data to server-based mailboxes, etc., this checkbox will appear grayed-out and
unavailable.) If you do forgo a connection to an Exchange server, attendees
free/busy information will be unavailable in migrated calendar appointments.
Profile name: If the program will connect to an Exchange server, use this
drop-down list box to specify the Admin profile created for the target Exchange
environment. The designated profile must have "Receive As" rights.
When you click Next, Microsofts
messaging subsystem prompts you for
your access credentials (as shown at
right). This is a Microsoft prompt, not a
Quest prompt. Enter your User Name,
Password, and the Domain Name for
your Exchange mail server, and click OK.
After you provide your Exchange access credentials, the program scans the
associated user-list .csv file and compares that information to your program
81
entries to see if it can identify any conflicts or other issues. If no problems are
apparent, the program simply advances to the next screen (skip ahead to the
next screen). But if it does find a problem, it notifies you in a dialog box:
Click the View button to see a
.csv file listing of errors and
warnings. The program will
save the .csv file to your
Quest admin directory by
appending "-error" to the
same filename as your current
user list.
Review the list, and decide whether you want to continue or abort the program
run:
To continue the program run: In the User-list error dialog box,

click OK to dismiss the dialog box and advance to the next screen.
To abort the program run: In the User-list error dialog box, click
Cancel to dismiss the dialog box and return to the previous program
screen. Then click the Cancel button to abort the program run.
20: Specify PST Output Root Directory

This screen (sample on next page) appears only if you have selected, in screen
#17: Specify Destinations for Migrated Data, to migrate one or more types of
data to Outlook personal folders (.pst) files.
Select the preferred method and location for delivering any Outlook Personal
Folders (.pst) files generated during the migration, and click Next.
82
Home directory of NetWare account: Places new.pst files in the

home directories of users' accounts.
Directory specified in .csv file: Places new.pst files in the directory

specified for each user in the .csv file, in the pstdir column. The pstdir
column values must be in the user-list (.csv) file prior to this program
run. (This option will appear grayed-out, as unavailable, if the
user-list file does not contain a pstdir column.)
Subdirectories of root directory specified below: Places .pst files

in subdirectories under this directory. This option creates a directory
structure that matches the user's GroupWise post office hierarchy. For
example, the location of the .pst file for a GroupWise user in the
GWDOM domain and the MAILPO post office, with a userid of

GWUSER, would be: GWDOM\MAILPO\GWUSER.pst.
Select a .pst file format, by Outlook version:
Use Outlook 97-2002 Personal Folders File (.pst): Tells the

program to format the .pst files in this format, which supports up to
2GB of data.
Use Office Outlook Personal Folders file (.pst): Tells the program
to format the .pst files in this format, which supports up to 20GB of
data. This option requires that Outlook 2003 be installed on the
migration machine. (The option will appear grayed-out, as an
unavailable choice, if Outlook 2003 is not installed.)
83
21: Specify GroupWise Domain Path

This screen appears only if one or more of your choices on earlier screens will
require an administrative login session to your GroupWise server.
Type your GroupWise Domain Path into the text box, or use the Browse
button to locate and specify your GroupWise Domain Path, and click Next.
The GroupWise Domain Path is the file system path to your GroupWise
domain file wpdomain.db. If necessary you can find this path by using the
NetWare Administrator program, NWAdmin or ConsoleOne: From the Tools
menu, select GroupWise System Operations ..., and then in the dialog box
click System Connection. The System Connection dialog box then displays a list
of GroupWise domains; the one labeled as the primary domain (format
\\NWSERVER\SYS\MAIL\GWDOM) is the value you need to enter for the
GroupWise Domain Path in this screen.
84
22: Specify Run Information

On the Specify Run Information screen: Enter the information to define how and
where the program should document its run in a log file, and set the desired
number of migration threads. Then click Next.
Directory for reports and log files: The directory where all reports and log
files for the migration run are written.
Run name: Enter a name for this migration run. The program verifies that the
run name is unique by scanning the log file directory for other run names.
Log level: Tells the program how much detail to include in its run logs. Select
Normal for a routine production run, or Verbose if you are having trouble and
want to diagnose a problem.
Number of migration threads (simultaneous user migrations): The
number of simultaneous processes the program will use to perform migrations.
The optimum number of threads depends on several factors such as processor
speed and bandwidth. Most administrators report optimum performance from
settings of 8 to 12 concurrent processes. You may want to experiment with
different values to determine the optimum setting for your network
configuration and processing capacity. (The program also lets you change this
value on a later screen, while the processes are running.)
85
23: Migration Settings Summary

Review the settings you have specified for this migration.
If any settings are incorrect, use the Back button to correct the choices and
values on previous screens. Then return to this screen to review and confirm
them. When this summary of settings accurately defines what you want to
accomplish, click Next to begin the run.
86
24: Progress Screen

Quest's Administrator-Driven Batch Migrator provides a progress bar and
migration statistics as it runs, and offers you the option of changing the number
of migration threads (simultaneous migration processes) while the program
runs. (The Maximum threads control here is the same as the Number of
migration threads option you set in screen #22: Specify Run Information.)
Whether or not you change the Maximum threads value, the program
automatically advances to its Results screen when the process is complete.
87
25: Results Screen

Review the migration results, and click on Migration Report to view a .csv file of
the results, or click Exit.
The Migration Report button is an optional feature that lets you view a
.csv-format file of the migration results. The feature will launch whatever
application you have associated with the .csv file type, and will work only if you
have defined (in Windows) that association.
This Results screen may also offer an Error Log Report button (not shown here)
if the program encountered any errors during its run. If the Error Log Report
button does appear, you should click it to view the program log and assess the
severity of the errors. The Error Log Report button launches Quests Log File
Viewer utility (see Appendix C) to help you interpret and resolve the errors.
88
Remember to Distribute Any User

.pst Files
If the batch migrator program has migrated any data to Outlook Personal Folder
(.pst) files, then when the migration is complete you must either:
notify users of the locations of their new.pst files (so each user can
specify the location within his or her own desktop copy of Outlook); or
distribute the newly created .pst files to users desktops.
Quest's Administrator-Driven Batch Migrator program names any new .pst files
by their associated User IDs, with incrementing numbers appended to the
filename if more than one file is generated per User IDfor example, Smith.pst,
Smith-1.pst, Smith-2.pst, and so forth.
89
90
Appendix A
AddProxy Utility
Quest's Administrator-Driven Batch Migrator must have access to users'
GroupWise accounts to migrate user data to the new Exchange environment. If
you are migrating from GroupWise version 6.5 or later, the migration program
will use Novells Trusted Application API feature to automatically register itself
as a trusted application, and will then be able to migrate GroupWise user data
without user passwords or proxy authorization. But if the GroupWise source is
version 5.5 or 6.0, the program will need user consent either by password or
by proxy to access users GroupWise data.
In many cases, the easiest way to provide access to pre-6.5 GroupWise accounts
is to have the program reset all migrating users' passwords, and then use the
new known password values to login under each user's login identity. But if a
common password is impractical or otherwise unsuited to your circumstances,
the Administrator-Driven Batch Migrator can be configured to instead access
users GroupWise accounts by proxy. That is, the program can login to each
users account using the credentials of an admin account that has previously
been authorized, by proxy, to access the users account.
Quests Addproxy utility was designed to automate the process of establishing
proxies for this purpose. The Addproxy program can be executed automatically
from a network login script, and can therefore be virtually transparent to end
users. As each user logs in to GroupWise, the Addproxy utility automatically logs
the successful procurement of proxy rights for his or her account, in a .csv
(comma-separated-values) log file. The .csv log file can then serve as the
user-list input file for Quests Administrator-Driven Batch Migrator program.
AddProxy Prerequisites
You may use the Addproxy program if any of these three conditions is met:
Your users are running a supported version of the GroupWise client:
GroupWise without Enhancement Pak: GW 5.5.1 or earlier, the latest

GW 5.5.4 update, or GW 5.5.5; or
GroupWise with Enhancement Pak: latest GW EP 5.5.4.1 update, or
GW EP 5.5.5.1, or GroupWise 6.
91
(A bug in the Novell Object API for GroupWise prevents the use of
Addproxy to add new proxy rights under certain versions of
GroupWise unless one of the other two conditions below is met.)
Your organization does not use Internet addressing.
All migrating users have previously granted other proxy rights to the
migration (proxy) administrator account. (Even if Addproxy cannot
create new proxy rights due to a failure to meet either of the other
two conditions listed above, the program can still modify existing
proxy rights to include the rights needed for the migration.)
If users have already granted other proxy rights to the migration
admin account: Use a text editor to edit the addproxy.ini file, to
change the AllowAdd=1 parameter to AllowAdd=0. Then save the
change and close the file.
Installing AddProxy
To use Quests Addproxy utility:
1.
2.
Create a folder (or note the name and location of an existing folder)
that is readable and writeable by all users who will run the Addproxy
program, to contain the Addproxy program and log files. For
example:
\\XYZSRV\SYS\PUBLIC\ADDPROXY
Copy addproxy.ini from your Quest programs folder to the above
folder (keeping the same addproxy.ini name), and edit the copy to
accommodate your circumstances and preferences. (See
Addproxy.ini Specifications below for item definitions and
specifications for the addproxy.ini file.)
3.
Copy addproxy.exe, _addproxy.exe and mfc42.dll to the above folder.
4.
Modify the network system login script (or the login scripts of
selected users) to run addproxy.exe. For example, if the program
were installed to the above folder, you would add this line to your
network system login script:
\\XYZSRV\SYS\PUBLIC\ADDPROXY\ADDPROXY
Note: If you are using a Netware login script, be sure to add an @
symbol to precede the name of the executable you want to run. For
example:
@\\XYZSRV\SYS\PUBLIC\ADDPROXY\ADDPROXY
As each user logs into the network and thereby activates the system login script,
the Addproxy program will automatically run on his or her machine. If the
program succeeds in authorizing proxy rights, it will note the success in the log
92
User Guide
file for successes (designated by the SuccessLog= parameter in addproxy.ini).

If the program fails, it will generate an error entry in the log file for failures
(designated by the FailureLog= parameter in addproxy.ini).
A successful run of Addproxy generates an item in the users Windows registry,
so Addproxy will not run more than once for any single user unless the
configuration settings have changed.
Uninstalling the AddProxy Program

After all of your users have run the Addproxy program, remove the line that runs
Addproxy from your network login script(s) the line that you added in step 4
of the installation instructions in the preceding section. You may then remove
the files addproxy.ini, addproxy.exe, _addproxy.exe and mfc42.dll from your
server.
Addproxy.ini Specifications
The addproxy.ini file is a text file containing parameters that govern how the
Addproxy program will run. Use a text editor to edit the parameters in this file
to suit your circumstances and preferences. The file contents format is:
[AddProxy]
Provider=quest
MigrationID=xyzcorp
LicenseKey=KAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
User=proxyuser@xyzcorp.com
UserGroupWiseAddr=proxyuser.gwpo.gwdom
Force=1
AllowSearch=0
SuccessLog=\\SERVER\VOLUME\PUBLIC\ADDPROXY\addproxy.csv
FailureLog=\\SERVER\VOLUME\PUBLIC\ADDPROXY\addproxyerr.csv
AllowAdd=1
addproxy.ini Required Parameters
Provider: The name of the provider of the license key. This

parameter is set for you during installation.
MigrationID: The customer ID provided by Quest Software. This

parameter is set for you during installation.
LicenseKey: This is the license key you received from Quest

Software. This parameter is set for you during installation.
93
User: Internet address of the administrative user who will be

authorized (by proxy) to access users archives and/or mailboxes
during migration.
UserGroupWiseAddr: The GroupWise address of the User specified

above. The format is userid.postoffice.domain. This parameter is
required if AllowSearch=0 (below).
Force: Determines whether the Addproxy program will attempt to

update a users proxy settings more than once. If set to "0" (the
default), the program will update a users proxy settings only once. If
set to "1," the program will update a user's proxy settings every time
it runs. The default setting "0" will normally be appropriate.
AllowSearch: Determines whether the Addproxy program will search

the system address book for addresses. In some situations, system
address book searches do not work correctly. In such cases, this
parameter can be set to "0" and UserGroupWiseAddr can be specified
to allow the addproxy program to function without system address
book searches. The default value for this parameter is "1."
SuccessLog: Specifies the name and location of a .csv file to which

successful proxy updates will be logged. The value must be specified
as a full UNC path, including the file name, that is valid and writeable
from every desktop where Addproxy will run. If this parameter is
omitted or not specified, no success log will be written.
The first line of the file contains the column headers. Subsequent lines
represent successful proxy update attempts:
Date,DisplayName,SourceAddress,TargetAddress,Status
8/4/2003 7:56:14,Joe Blow,JBLOW.GWPO.GWDOM, Joe.Blow@company.com,OK
FailureLog: Specifies the name and location of a .csv file to which

failed proxy updates will be logged. The value must be specified as a
full UNC path, including the file name, that is valid and writeable from
every desktop where Addproxy will run. If this parameter is omitted
or not specified, no failure log will be written.
The first line of the file contains the column headers. Subsequent lines
represent unsuccessful proxy update attempts:
Date,DisplayName,SourceAddress,TargetAddress,ErrorText
8/4/2003 7:51:44,Joe Blow,JBLOW.GWPO.GWDOM,Joe.Blow@company.com,
Cant find user...
94
AllowAdd=1: Do not edit this parameter unless you are manually

granting proxy rights to the administrator and using Addproxy to
modify the proxy rights for migration. (This is explained above under
AddProxy Prerequisites.)
User Guide
addproxy.ini Optional Parameters
PiggyBack: Specifies whether the program should wait for the user
to login to GroupWise or immediately prompt the user for a userid and
password. The two valid values are:
PiggyBack=0: Prompt immediately for userid and password if the

user is not already logged into GroupWise.
PiggyBack=1 (default): Do not prompt for userid and password.
(Wait for the user to log into GroupWise.)
PiggyBackRetry: Specifies how long (in seconds) to wait between

checks if Addproxy is waiting for the user to log into GroupWise
(parameter is ignored if PiggyBack=0). The default value is 15.
PiggyBackTimeout: Specifies the total time (in seconds) to wait for

the user to login to GroupWise before exiting (parameter is ignored if
PiggyBack=0). The value "0" tells the program to wait indefinitely.
The default value is 7200.
Rights: Specifies the list of rights to grant to the administrative user.

You may specify two or more rights by listing them with a space
between each pair, as in:
Rights=archive read private settings
The default is Rights=all. Other valid values are:
all: All rights.

read: Includes readAppointments, readMailAndPhone, readNotes, and
readTasks.
write: Includes writeAppointments, writeMailAndPhone, writeNotes,
writeTasks.
alarms: Allows access to alarms.
archive: Allows access to the archive.
notifs: Allows access to notifications.
private: Allows access to items marked as private.
settings: Allows access to Preferences, Rules, and Groups.
readAppointments: Allows read access to appointments.
readMailAndPhone: Allows read access to mail messages and phone
messages.
readNotes: Allows read access to reminder notes.
readTasks: Allows read access to tasks.
writeAppointments: Allows write access to appointments.
writeMailAndPhone: Allows write access to mail messages and
phone messages.
writeNotes: Allows write access to reminder notes.
writeTasks: Allows write access to tasks.
none: No rights.
95
96
Appendix B
AD Object Merge Tool
The AD Object Merge Tool updates and mail-enables Active Directory accounts
identified in a UsersToMerge.csv file that is specified during the program run.
For each user listed in the file, if an Exchange Contact address matches the
GroupWise SourceAddress in UsersToMerge.csv, the program merges the
GWISE and SMTP aliases from the Contact into the AD security object, and then
deletes the Contact, to consolidate the pair into a single mail-enabled security
object. If no such corresponding Contact exists, the program simply merges the
SourceAddress from UsersToMerge.csv into the AD security object, to
mail-enable the object.
Before You Begin ...

The AD Object Merge Tool should be run before you attempt to migrate any
users, but must be run after the Directory Exporter, since the Directory Exporter
generates the necessary UsersToMerge.csv input file.
If you want the program to identify users in AD by an Active Directory attribute,
you must prepare the UsersToMerge.csv file before the program run. (The
program can be told to identify users in AD by any of three methods, which you
will specify in step 4 of the procedure below.) If you choose to identify users by
attribute, then the UsersToMerge.csv file must contain a SearchKey column to
specify, per user, the attribute values by which users can be identified in Active
Directory. The AD Object Merge Tool will prompt you for the name of the AD
Attribute that the program should read to identify users, so the per-user values
for that attribute must be specified in the SearchKey column of
UsersToMerge.csv prior to the program run.
Also, if you will run the AD Object Merge Tool for Exchange 2003, the RUS will
remove users GWISE proxy addresses if it doesnt find a GWISE type address in
the Default Recipient Policy. To prevent this, be sure that the Default Recipient
Policy contains a GWISE type address before you run the AD Object Merge Tool,
although the GWISE type address need not be enabled. (This precaution is not
necessary for Exchange 2007.)
97
1.
Start the AD Object Merge Tool from your computers Start menu, in
the GroupWise Migrator for Exchange program group. When you
start the program, it briefly displays an introductory "splash" screen,
and then its Welcome screen.
2.
Review the Welcome screen, and click Next when you are ready to
begin entering the values that will define this merge process.
3.
Use the Browse button to locate and specify the user-list .csv file for
this program run (or just type the path and filename into the text
box), and click Next.
Quests Directory Exporter automatically generated a

UsersToMerge.csv file that you may use for this purpose.
4.
98
On the Specify AD Information screen (sample on next page):

Identify the Active Directory server and provide the administrator
credentials and information Exchange will need to perform the
selected administrative functions, and click Next.
User Guide
Host name: The name of the AD server.

User Name: The user name of the administrator by whose authority
the program will perform its functions.
Password: The password of the administrator named above.
How do you want to find users in Active Directory: This is the
method by which the program will identify users within the Active
Directory. Select any of the listed options:
Find users from the Quest NDS Migrator database: The output
database file created by Quests NDS Migrator (a separate Quest
product, not a part of GroupWise Migrator for Exchange). If this option
is selected, you must also specify SQL server information:
Server: The name of the SQL server.
Authenticate by: Method of authentication to the SQL server.

Choose either Current Windows login or SQL user ID and
password. If you choose the SQL method, you must also provide
the associated SQL User ID and SQL Password in the text boxes
below.
Find users by pre-Win2K user name: The users pre-Win2K logon

names, as defined in AD. (The SQL server fields do not apply.)
99
5.
Find users by attribute: Find users by the AD Attribute named in

the accompanying text box (below). If you select this option, the
associated user-list .csv file must contain a SearchKey column,
containing the corresponding Attribute values for all users in the
table. (The SQL server fields do not apply.)
Specify a directory for storing program reports and logs, and enter a
process run name, and click Next.
Directory for reports and log files: The directory where all reports
and log files for this merge run will be written.
Run name: Enter a name for this merge process. The program
verifies that the run name is unique by scanning the log file directory
for other run names.
6.
On the Settings Summary screen (sample on next page): Review the

settings you have specified for this merge process.
If any settings are incorrect, use the Back button to correct the
choices and values on previous screens. Then return to this screen to
review and confirm them. When this summary of settings accurately
defines what you want to accomplish, click Next to begin the run.
When you click Next from the Settings Summary, a status screen
(sample also on next page) reports the program's progress while the
merge process is running, and the program automatically advances to
the last screen when the process is finished.
100
User Guide
101
7.
Review the process results. Click on Merge Report to view a .csv file
of the results, or just click Exit.
This Results screen may also offer an Error Log Report button (not
shown here) if the AD Object Merge Tool encounters any errors or
warnings during the program run. If the Error Log Report button
does appear, you should click it to view the program log and assess
the severity of the errors or warnings. The Error Log Report button
launches Quests Log File Viewer utility (see Appendix C) to help you
interpret and resolve the errors or warnings.
102
Appendix C
Log File Viewer
Quests GroupWise Migrator for Exchange includes a Log File Viewer utility that
simplifies the viewing and interpretation of Quest program log files, which are
generated by most Quest applications to document errors and warnings as the
processes run.
The Log File Viewer is launched automatically by appropriately named buttons
on the last screens of Quests Directory Exporter, AD Object Merge Tool,
Administrator-Driven Batch Migrator, and Self-Service Desktop Migrator
applications. (The button appears on the screen only if the program has
generated at least one error.) You may also start the Log File Viewer manually
from your computers Start menu, in the GroupWise Migrator for Exchange
program group.
The Log File Viewer is a resizeable window divided into three panes:
Log File Navigator: A scrollable summary list of all errors and

warnings in the log file. The program lets you sort and organize this
list in several different waysby user, by error message, and by
103
solution to the problemso you can seek and find particular errors
and warnings quickly. When you click on any single line item in this
Navigator list, the program instantly displays and highlights the
corresponding log lines in the adjacent File Contents pane.
Log File Contents: A scrollable display of the entire contents of the

log file.
Likely Solution(s): A suggested solution to the problem. If the

detected problem corresponds to a known issue with one or more
suggested solutions in Quests on-line database, the Solution topic for
the selected error or warning will appear in this pane. (Since this
feature retrieves information from Quests on-line database, it will
work only if you are connected to the Internet.)
When you are finished reviewing the log file, click the [X] Close box (top-right
corner of the window) to close the Viewer and return to your previous screen.
104
User Guide
To Change the Sort Order

of the Log File Navigator
Each error or warning in a log file consists of three elements: the error
Message, the User whose data or configuration generated the error or warning,
and a suggested Solution to the problem. The Log File Navigator pane lists
errors and warnings within a hierarchical outline organized by these three
elements, as shown in the sample screen above.
You can change the sorting criteria of the Log File Navigator to reorganize the
list, to look up particular error or warning instances in different ways. The sort
order can be changed with the Group By option, on the View menu:
To Generate a User-List .csv File

of "Error Users" (in the Log File)
After you resolve the errors and warnings reported in a Quest log file, you may
want to re-run the Quest application for those users whose data and/or
configurations generated the errors. The Directory Exporter, AD Object Merge
Tool, and Administrator-Driven Batch Migrator all require user-list .csv files to
run, and the Log File Viewer can generate a .csv file to define a user list of "error
users" only.
To generate a user-list
.csv file of all users who
appear in the log file:
Select File menu option
Export, and then select
the User List (.csv)...
option.
105
To Generate a Report of the Log File

Select File menu option Export, and then select either the Summary Report
of Solutions/Users... or Detailed Report of Solutions/Users... option.
Both the Summary Report and Detailed Report options generate printable
files that document the contents of the log file, sorted by the suggested Solutions
for found problems, and listing (for each Solution) the Users who were found to
have errors or warnings that would likely be resolved by the Solution. The
Summary Report option generates a simple text file of only the Solution titles
and Users. The Detailed Report option generates an RTF file that adds the full
HTML renderings of the suggested Solutions, as they appear in the Likely
Solution(s) pane of the viewer window.
106
Appendix D
Customizing the
Self-Service Desktop
Migrator Program
Quests Self-Service Desktop Migrator is simple and intuitive enough that most
end users will be able to run it uneventfully. Some administrators simplify the
process even more by customizing the per-desktop program to enforce or
eliminate certain choices in accordance with a particular migration strategy. For
example, if an administrator wants to migrate users server mail and address
books in batches, and then use the Self-Service Desktop Migrator to migrate
user archives (only), the per-desktop program can be customized to migrate
only archives, and to not offer the option to migrate server mail or address
books.
These program customizations are accomplished by manipulating certain
parameters in the gwdtapp.ini file, as described in the topics below:
Providing Program Entry Values in gwdtapp.ini
Hiding Entire Screens from the User
Hiding Certain User Choices on the Specify Data for Migration Screen
The Self-Service Desktop Migrator can also be controlled by several switches on

the command line, appended to the program command when the Desktop
Migrator is executed. These command-line switches, and how they interact with
pertinent INI-file parameters, are described in chapter 2 see Command-Line
Switches for Running the Desktop Migrator in Silent Mode.
107
Providing Program Entry Values in

gwdtapp.ini
If the Self-Service Desktop Migrator is configured to skip certain screen displays,
the program must have some alternate method of obtaining the information that
would otherwise be collected from fields on those screens. The program can read
and/or infer some entry values from the operating environmentfrom the
Windows Registry and Outlooks initialization files, etc.and some values can be
specified by command-line switches (see Command-Line Switches for Running
the Desktop Migrator in Silent Mode in chapter 2). But some values can also be
provided by parameters in the gwdtapp.ini file.
When an entry value is specified in the INI file, the value will appear as the
default if the corresponding screen and option appear in the program run, or will
simply be the prevailing value if the screen and option do not appear.
Migration Choices in
the Specify Data for Migration Screen
Any or all of the migration choices in the Specify Data for Migration screen can
be specified in gwdtapp.ini by these parameters:
[General]
MigrateArchives=1
MigrateServerMail=1
MigratePAB=1
MigrateFreqContacts=1
[ArchiveData]
MigrateTrashFolder=1
[ServerData]
A parameter value of 1 sets the option to "yes" (the data type will be migrated
if the screen does not appear), or sets the associated checkbox to be marked by
default. A value of 0 sets the option to "no," or sets the associated checkbox to
be unmarked by default.
If a feature is disabled by AppDoesXxxx=0 (see Hiding Certain User Choices on
the Specify Data for Migration Screen below), the corresponding MigrateXxxxx=
parameter will be ignored. On the other hand, if AppDoesXxxx=1 in silent mode
(MigrateWhat=silent), the program will automatically set the corresponding
MigrateXxxx= parameter to 1. (Although if MigrateWhat=show or =skip, the
AppDoesXxxx= setting has no effect on the MigrateXxxx= parameter.)
The most common use of these parameters is to provide the necessary entry
values when the program is configured to skip the Specify Data screen by
MigrateWhat=skip or MigrateWhat=silent (see Hiding Entire Screens from the
User below).
108
User Guide
Outlook Profile in the Select Profile Screen

If the program finds more than one eligible Outlook profile on the users
computer, or doesnt find any, the program displays a Select Profile screen to
prompt the user to designate the profile to be converted. If one and only one
eligible Outlook profile is found on the users computer, the program will simply
assume it is the correct profile to convert, and the Select Profile screen will not
appear.
The per-desktop program can be configured to skip the Select Profile screen, but
in that case the program must be able to determine the correct Outlook profile
to convert. The users Outlook profile can be specified in the [General] section
of gwdtapp.ini by:
[General]
SelectedProfile=<ProfileName>
Alternatively, the users Outlook profile can be specified by appending the
/TGTPROFILE switch to the Desktop Migrator on the command line, when the
program is executed. (See Command-Line Switches for Running the Desktop
Migrator in Silent Mode in chapter 2 for more information about this and other
command-line switches.)
Specifying the users Outlook profile in the INI file will be useful only if:
all users who will run the program with that INI file will have the same
profile name (e.g., some generic name like "My Profile," although
each users profile resides on the users own local workstation and is
independent of other users profiles); or
a different INI file is prepared for each individual users run of the
per-desktop program, so that individual profile names can be
specified.
Remember too that the program will not need this ProfileName value if one and
only one eligible profile will be found on each users workstation.
109
Archive Destination Folder in

the Specify Directory for Migrated Archive Screen
The destination folder (path) for the users migrated archive can be specified in
the [General] section of gwdtapp.ini by:
[General]
SelectedPstDir=<path>
... where <path> is the full UNC or mapped-drive path (without filename)
relative to the users computer.
This value, if necessary in a particular program run, would otherwise be specified
in the Specify Directory screen.
The default for this parameter is the Outlook Default Directory, which the
program can determine from its operating environment. This parameter is
therefore necessary only if you want users migrated archives to go somewhere
other than the Outlook Default Directory.
Filter Conditions in the

Select Date and Size Filters Screen
The Self-Service Desktop Migrator lets you specify date limits and ranges for
messages to be migratedto migrate only messages timestamped on or after
(or before) a certain date, or within a particular range of dates. You can also
specify a maximum size limit for attachments. These date and size filters can be
specified during a program run on the Select Date and Size Filters screen, but
that screen is hidden by default (see the Filter= parameter in the next section
below) and the filters may instead be defined by these parameter settings in the
[Filter] section of notesdtapp.ini:
[Filter]
AttachSize=<####>
FirstDate=<mm/dd/yyyy>
LastDate=<mm/dd/yyyy>
The AttachSize= value is numeric, in kilobytes. The two date parameter values
must be entered in the eight-digit, slash-separated form shown above, with a
zero preceding any single-digit month or day. The defaults for all three
parameters are null, so no filtering will occur.
110
User Guide
Hiding Entire Screens from the User

The Self-Service Desktop Migrator program can be customized to make some of
its screen displays "silent"that is, invisible to the end useror to skip a screen
conditionally, making it visible only if the program cannot find the information it
needs either from the operating environment or elsewhere in the gwdtapp.ini
file. The display option for each screen can be set to one of these three
parameter values in the [Screens] section of the gwdtapp.ini file:
show: The screen will appear in every program run.
skip: The screen will appear only if the program cannot read or infer
the associated information either from the operating environment, or
from other parameters within the gwdtapp.ini file.
silent: The screen will not appear in any program run. The
information that would otherwise be collected by the screen can
instead be provided by other parameters in gwdtapp.ini, and/or can
be read or inferred from the operating environment. But if the
program cannot determine the necessary information, the function
will fail and the users data will not be fully migrated. (This is a likely
cause of any failed or incomplete single-user migration if the INI file
has been modified to make one or more screens "silent.")
The show, skip or silent mode can be applied to each of the program screens by
setting parameter values in the [Screens] section of gwdtapp.ini for:
Parameter
Welcome=
MigrateWhat=
Filter=
Profile=
PstDir=
Summary=
Progress=
Finished=
Screen Name (in Title Bar)

Welcome ................................................
Specify Data for Migration ........................
Select Date and Size Filters ......................
Select Profile ..........................................
Specify Directory for Migrated Archive ........
Selection Summary .................................
Migrating Data ........................................
Migration Report .....................................
Default
show
show
no-op*
skip
show
show
show
show
*no-op: Functionally equivalent to "silent," but actually signifies that the

parameter value is unassignedin which case the screen will not appear in
a program run.
The visibility of two other screens cannot be set or changed in gwdtapp.ini:
Login to Your GroupWise Account (occurs between the Specify

Data and Select Profile screens): The GroupWise Login screen cannot
be skipped or silent, because no migration is possible without the
users login credentials.
Enter Password (occurs between the Selection Summary and

Migrating Data screens): This Microsoft prompt for the users
111
Exchange login credentials may appear if the Outlook profile is

configured to require login credentials.
Both of these values can, however, be specified by command-line switches when
the Desktop Migrator program is executed. See Command-Line Switches for
Running the Desktop Migrator in Silent Mode in chapter 2 for more information
about these and other command-line switches.
Hiding Certain User Choices on the

Specify Data for Migration Screen
The default display of the Specify Data for Migration screen lets the user migrate
any combination of three types of user data: server mail, archives and personal
address books (PABs). But some administrators prefer to offer only one or two
of these options. Three boolean (1-or-0) parameters in gwdtapp.ini, in the
[General] section, can control whether these options will appear in the screen:
AppDoesArch=
AppDoesMail=
AppDoesPabs=
For each parameter, the default value 1:
Makes the corresponding option visible to the user on the Specify Data
for Migration screen.
Sets the corresponding MigrateXxxx= parameter to 1 (see Migration

Choices in the Specify Data for Migration Screen above) when in silent
modethat is, if MigrateWhat=silent. Although if MigrateWhat=show
or =skip, the AppDoesXxxx= setting has no effect on the
corresponding MigrateXxxx= parameter.
A setting of AppDoesXxxx=0:
Makes the option invisible (unavailable to the user) on the screen.
Masks the portions of the Welcome and Migration Report screens that
pertain to the hidden option.
Disallows the migration of that data type regardless of other

parameter settings elsewhere in the INI file (i.e., would override
MigrateXxxx=1).
If a parameter is left unspecified in the INI file, the corresponding option will
appear on the screen.
112
User Guide
Note that these parameters do not set the marked-vs-unmarked status of the
corresponding checkboxes, although those status settings can be controlled by
other parameters (see Providing Program Entry Values in gwdtapp.ini above).
When the program is configured to display only one of the three options in the
Specify Data for Migration screen, the lone option will appear without a
checkbox, so a user cannot turn off the associated function by deselecting the
checkbox.
For Example:
To Migrate Archives Only
In the introduction to this appendix we mentioned the example of an
administrator who wants to migrate users server mail and address books in
batches, and then use the Self-Service Desktop Migrator to migrate user
archives (only). Since the per-desktop program will be used to migrate archives
only, the admin wants to hide the other migration options (server mail and PABs)
from the user, and moreover wants to streamline the rest of the user interface
to minimize its demands on the users attention.
To accomplish this in the gwdtapp.ini file:
[General]
AppDoesMail=0
AppDoesPabs=0
MigrateArchives=1
[ArchiveData]
[Screens]
Welcome=skip
MigrateWhat=skip
Profile=skip
PstDir=skip
Summary=skip
Progress=skip
Finished=show
These parameters will configure the Desktop Migrator to run like this:
1.
Welcome screen: Will not appear, because Welcome=skip and no

user entires are requested on this screen.
2.
Specify Data for Migration: Will not appear, because

MigrateWhat=skip, and AppDoesMail=0 and AppDoesPabs=0, and
113
the program will obtain its necessary archive-migration orders from

MigrateArchives=1 and MigrateTrashFolder=1.
3.
Login to Your GroupWise Account: Will appear in every program

run.
4.
Select Profile: Will not appear if the program finds one and only one
eligible Outlook profile on the users workstation. Otherwise, will be
necessary to prompt the user to designate the profile.
5.
Specify Directory for Migrated Archive: Will not appear,

assuming the Outlook Default Directory is the preferred archive
destination folder for every user. (If not, then specify a valid path for
SelectedPstDir= under [General], or change PstDir=skip to
PstDir=show.)
6.
Selection Summary: Will not appear, because Summary=skip and

no user entires are requested on this screen.
7.
Enter Password (for Exchange): May or may not appear, per user,
depending on whether the users profile is configured to require
these credentials.
8.
Migrating Data: Will not appear, because Progress=skip and no

user entires are requested on this screen.
9.
Migration Report: Will appear in every program run, since

Finished=show.
So, omitting the skipped screens, and assuming that each user will have one and
only one Outlook profile, and that we want user archives migrated to their
Outlook Default Directories, the programs screen sequence will be:
114
1.
Login to Your GroupWise Account: Will appear in every program

run.
2.
Enter Password (for Exchange): May or may not appear, per user,
depending on whether the users profile is configured to require
these credentials.
3.
Migration Report: Will appear in every program run, since

Finished=show.
Appendix E
How GroupWise Migrator
for Exchange Maps Shared
Folders to Outlook
Shared folders in GroupWise can have Read, Add, Edit and Delete rights. Shared
PABs can be set to either of two modes: Read or All. The All rights in GroupWise
are Read, Add, Edit and Delete. GroupWise rights are migrated to Outlook ACLs
like this:
GroupWise Rights
Outlook ACLs:
Read
Create Items
Read Items
Add
Edit
Delete
X
X
Create subfolders
Folder owner
Folder visible*
Edit All
Edit Own
Delete Own
Delete All
* Folder visible =
Set for all parent folders of the shared folder.
If a user has proxy rights for a GroupWise account, the proxy rights are
combined with the Minimum User Access rights and applied to the appropriate
Outlook folder(s).
The Minimum User Access rights from GroupWise are mapped to the Default user
ACL in Outlook, while the Anonymous user ACL is set to None.
115
The following rights are migrated:

Read Mail/Phone
Read Appointments
Read Tasks
Write Mail/Phone
Write Appointments
Write Tasks
The Read rights will create a Read Items privilege on the appropriate folder (see
table below). The Write rights will apply these privileges to the appropriate
folder:
Edit All
Edit Own
Create Items
Delete All
Delete Own
Read or Write
Mail/Phone
Inbox
Read or Write
Tasks
Read or Write
Appointments
Calendar
Cabinet
Drafts
Sent Items
Tasks
User Folders*
Deleted Items
* User Folders = any folders created by the user.
Proxy rights and folder rights are combined during migration. When a user is
migrated the proxy rights for the folders are combined with the folder-sharing
rights for a specific folder.
116
Appendix F
Known Limitations of the
Migration Process
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 different enough that the migration may be impractical.
Known limitations of the migration process facilitated by Quests GroupWise
Migrator for Exchange 3.5 are:
Contact Attributes: For Contacts in personal address books, the

following attributes are not migrated:
multiple e-mail addresses

multiple IM names
Categories
Birthday
GroupWise UIDs in Exchange ACLs: In Exchange ACLs, users who

have not yet been mailbox-enabled in Exchange are identified (in
ACLs) by their cryptic GroupWise UIDs instead of by their
recognizable displayNames. This phenomenon is temporary; after a
user is migrated, he/she is identified by displayName.
Mail Links in Plain Text Messages: GroupWise will automatically

create a mail link for SMTP addresses found in plain text messages.
When the message is migrated to Exchange, the maillink is lost.
Accepted Appointment Status: The attendees' accepted state of an

appointment is not retained.
Document references do not migrate from a GroupWise 6.5.4

client source. This limitation seems to apply only to version 6.5.4.
117
118
Glossary
Access Control List (ACL)
A list that identifies the owner(s) of a particular file, and
that defines which users have which privileges (viewing,
editing, deleting) for the file.
ACL
Archives
See Access Control List.

Files that contain users personal mail and calendar data,
stored in per-user files. A user can conserve server space
and remain within his/her quota for server storage by
transferring data from the server to personal archives,
typically stored on each users own local workstation.
(Compare to Server-based data.)
Batch migration
A process of migrating data from one server/client
environment to another, for multiple users (a "batch") in a
single program run. (Compare to Per-desktop migration.)
GroupWise Migrator contains an Administrator-Driven
Batch Migrator component that lets an administrator
perform batch migrations.
CN
See Common name.
Coexistence
The state of two independent mail or directory servers
when both are serving the same organization at the same
time. This is a common temporary condition during the
transition period of a migration, when some users have
already been migrated to a new server while other users
remain on the old server, awaiting migration.
Common name (CN)
The identifying name assigned to a directory object. A
common name must be unique within a context.
(Compare to Distinguished name.)
Contact
An Active Directory object that represents a user outside

the Exchange organization. For example, a contact may
represent a not-yet-migrated user who still receives and
sends email via the source server, or someone in another
119
company with whom an Exchange user correspondsa

customer or a vendor, for example. A contact is associated
only with an address, and has no Active Directory account.
csv files
Text data files, stored in a structured

comma-separated-values (csv) format that uses commas
as field delimeters for data tables.
Destination
The server or environment to which data is migrated. In
GroupWise Migrator, Microsoft Exchange and Active
Directory are the destinations of the migration process.
(Synonymous with Target in this context.)
Distinguished name (DN)
A name that uniquely identifies a directory object by
defining the entire path between the object and the
directory root. The DN includes the relative distinguished
name for the object, plus the names of container objects
and domains that contain the object, to specify both the
object and its location in a tree. (Compare to Common
name.)
Distribution group, Distribution list
See Public distribution group.
DN
DNS
See Distinguished Name.

See Domain Name System.
Domain Name System (DNS)

A hierarchical, distributed database that maps domain
names to various types of data, including IP addresses.
Every node on the Internet is identified by a unique,
numerical IP address of the form 255.255.255.255, and
every IP address is associated with a single domain name.
The DNS defines the associations of domain names to
their corresponding IP addresses.
Mail-enabled
Trait of an Active Directory object whereby the objects
mail-address attributes (for an address outside the
Exchange domain) reside in AD, so AD can forward the
objects mail to its other address. Note that no Exchange
mailbox is associated with a merely mail-enabled object.
(Compare to Mailbox-enabled.)
120
User Guide
Mailbox-enabled
Trait of an Active Directory object whereby an Exchange
mailbox exists for the object, and the objects incoming
mail is routed to its Exchange mailbox. (Compare to
Mail-enabled.)
Migration machine
The computer that will run the Quest migration software
applications.
MX record
Owner
Short for Mail eXchange record, an entry in a domain

name database that identifies the mail server responsible
for handling emails for that domain name. More than one
MX record can be entered for a single domain name using
more than one mail server, so the MX records can be
prioritized with numbers to indicate the order in which the
mail servers should be used. This makes possible the
designation of primary and backup mail servers.
For any particular file, a user who has the most complete
authority to view, modify and delete the file.
Per-desktop migration
A process of migrating data, from one server/client
environment to another, for a single user per program run.
(Compare to Batch migration.) GroupWise Migrator
contains a Self-Service Desktop Migrator component that
performs per-desktop migrations.
Phased migration
A migration strategy in which date filters are used to
migrate all but the most recent data first, while users
continue to receive and send email from the source server,
so that all users can then be migrated together, quickly,
with the comparatively small volume of data that remains
to be migrated.
Pilot migration
A partial migration with a portion of real data, in the real,
live production environment, to assess the suitability of a
Migration Plan before the first full production migration
run.
Provisioning
Populating a directory with objects (users, resources, and
so forth), and the information that characterizes objects.
121
pst files
The files in Microsoft Outlook, with a .pst extension, that

contain users personal storage datatypically the form to
which GroupWise archives are migrated.
Public distribution group, distribution list

A set of directory objectsusers and/or resourcescollectively defined as a group of message recipients. A single
message can be "broadcast" to all members of a distribution group by specifying the single group as the recipient.
Server-based data
Email and calendar data that is stored on a central server.
(Compare to Archives.)
Simple Mail Transfer Protocol (SMTP)
The standard TCP/IP protocol that governs message
transmission over the Internet, by addresses in the form
name@domain.com. SMTP is the default transport protocol
for Microsoft Exchange.
SMTP
Source
See Simple Mail Transfer Protocol.

The server or environment from which data is migrated. In
GroupWise Migrator, NDS and GroupWise client archives
are the sources of the migration process.
Synchronization
Process of updating the contents of one directory to match
the contents of another, comparable directory. If, for
example, the source and target server directories of a
migration will coexist for more than a day or two, most
organizations will want to regularly synchronize the two.
Target
The server or environment to which data is migrated. In

GroupWise Migrator, Microsoft Exchange and the Active
Directory are the targets of the migration process.
(Synonymous with Destination in this context.)
Test migration
A partial migrationeither with a copy of real data in a
separate test environment, or with dummy data in the
real, live production environmentto assess the suitability
of a Migration Plan before the first full production
migration run.
122
User Guide
UNC Path
A notation (UNC = Universal Naming Convention) to

specify the absolute location of a domain directory, in this
syntax: \\server\volume\dir\dir\...\domain directory.
User-list .csv file

A comma-separated-values (csv) format data file
containing the names of users to whom the features of
Quests Administrator-Driven Batch Migrator program will
be applied in a particular program run. In each run, the
program prompts for the name and location of the
associated user-list .csv file. Most administrators create
the user-list .csv files by copying and editing the
UsersToMigrate.csv file that is automatically generated by
Quests Directory Exporter.
123
124
INDEX
A
Access Control List 20, 119
access rights to source and target
environments 20, 29, 32
AD Object Merge Tool 13, 19, 30, 42, 54,
63, 70, 97
Addproxy entry in Windows registry 93

Addproxy prerequisites 91
Addproxy, uninstalling 93
Addproxy utility 13, 19, 31, 41, 46, 77,
91
addproxy.ini file 92, 93

AddressTranslation.csv 54
administrator-driven batch migration by
password: see batch migration by
password
administrator-driven batch migration by
proxy: see batch migration by proxy
Administrator-Driven Batch Migrator 13,
19, 44, 46, 47, 48, 54, 60, 91
API Gateway 67
archives, location of in GroupWise
environment 24, 43, 47, 49, 76
archives, migration of 27, 43
attachment size filtering 75
auto-decline/delete forwarded
messages 66
autoreply 66
B
bandwidth, implications of 25, 27
batch migration 18, 19, 24, 44
batch migration by password 31, 34, 44,
45, 47, 63, 65, 68, 78, 91

batch migration by proxy 31, 44, 46
batch migrator program: see

batch vs. per-desktop migration 18, 24,
119, 121
batches, grouping method 25

batches, scheduling for migration 25
batches, size of 25
C
changing GroupWise passwords: see
batch migration by password
coexistence of directories during
transition 25, 28, 119
command-line switches: see Self-Service
Desktop Migrator, command-line
switches for
common name (CN), defined 119
Contact (in AD), defined 119
conventions 14
creating Exchange mail-enabled accounts:
see mail enabling
creating Exchange mailboxes: see mailbox
enabling
csv files 29, 42, 45, 54, 57
csv files, editing 24, 29, 42, 45, 46, 47,
49, 54, 57, 67
D
data migration rate 26
data volume 25, 26, 27
date filter: see date limits for messages to
be migrated
date limits for messages to be
migrated 75
decommissioning GroupWise server: see
GroupWise server, decommissioning
desktop migration: see Self-Service
Desktop Migrator
direct mode access to GroupWise
server 78
Directory Exporter 13, 19, 42, 45, 54
directory synchronization: see
synchronization of directories
distinguished name (DN), defined 120
distribution groups: see public distribution
lists
documentation: see product
documentation
domain name system (DNS), defined 120
double-booking resources 34
E
email routing method 29
end user migration: see Self-Service
Desktop Migrator
end user training and
communications 36, 50
Error Log Report feature 57, 88, 102
Exchange 2003 21
Exchange 2007 21
Exchange Connector for GroupWise 29,
35, 48
Exchange mail-enabled accounts: see mail

enabling
Exchange mailboxes, creating: see
mailbox enabling
F
FailureLog file for Addproxy utility 93, 94
filtering options 110
free/busy lookups 29
125
G
geographic distribution of data 26, 27
group membership lists, duplicates during
coexistence 35
GroupsToProvision.abk 43, 54, 57, 62
GroupWise Directory Exporter: see
Directory Exporter
GroupWise, earlier versions 36
GroupWise Migrator for Exchange,
installing 41
requirements 21, 41
GroupWise server, decommissioning 52
GroupWise, versions supported 21, 36,
91
gwdtapp.ini file 49, 50, 51, 107
H
Help desk, anticipating demand for 27
HomeMDB column in user-list .csv file 46
I
installing GroupWise Migrator for
Exchange: see GroupWise Migrator
for Exchange, installing
K
known limitations of the migration
process 13, 36
L
license key 61
Limitations of the Migration Process 13
Log File Viewer 13, 19, 103
login script, network: see network login
script
M
mail enabling 30, 63, 70, 120
mail-forwarding domain, source to
target 66
mail-forwarding domain, target to
source 72
mail-forwarding rules 31, 52, 63, 64, 66,
69
mail routing during migration 19, 47, 52,
66
mailbox enabling 19, 47, 63, 70, 121

mailboxes, creating in Exchange: see
mailbox enabling
manuals: see product documentation
merging contacts and security objects in
AD 19, 30, 42, 97
126
Microsoft Exchange Connector for

GroupWise: see Exchange Connector
for GroupWise
migration per desktop: see Self-Service
Desktop Migrator
Migration Plan, developing 23
Migration Report feature 88
migration scale and duration 25
multiple AD domains 29
multiple Exchange Mailstores, migrating
to 46
MX (Mail eXchange) record 43, 121
N
NDS Migrator: see Quest NDS Migrator
network login script 41, 91, 92
network security 20
O
Outlook, installation on user desktops 27,
32
P
PABs, location of in GroupWise
environment 43
PABs, migration of 43
parallel migration workstations 22, 25,
27, 32
password method of migration: see batch

migration by password
password vs. proxy method of access to
GroupWise user data 31, 45, 76
passwords, GroupWise: see batch
migration by password
per-desktop migration 18, 19, 24, 48
personal address books: see PABs
Personal Folders files, Outlook: see pst
files
phased migration strategy 33, 121
pilot migration 37, 121
post-migration clean-up 52
pre-migration preparations 40
product documentation 12
program connection to Exchange
server 81
program license key: see license key
provisioning on Active Directory 30, 70
proxy method of migration: see batch
migration by proxy
proxy vs. password method of access to
GroupWise user data: see password
vs. proxy method ...
pst files 48, 81, 82, 89
pst files, defined 122
User Guide
pst files, location of in destination
environment 82
public distribution lists, defined 122
public distribution lists, migrating 19, 30,
43, 60, 62
purge messages after forwarding 66
U
UNC path, defined 123
user-list .csv file 24, 44, 45, 46, 47, 48,
54, 64, 67, 68, 71, 78, 81, 82, 91, 98
user visibility (in GroupWise) 63, 69

UsersToMerge.csv 54, 58, 97, 98
UsersToMigrate.csv 45, 54
Quest NDS Migrator 30, 42, 63, 70, 99
visibility, user: see user visibility (in

GroupWise)
Receive As rights 20, 21

recipient policy for temporary
subdomain 41
Recipient Update Service 21, 48
RemoveSrcAddresses= parameter 43
resources, migration of 31, 34
routing of mail during migration: see mail
routing during migration
S
Self-Service Desktop Migrator 13, 19, 24,
48, 54, 107
Self-Service Desktop Migrator, commandline switches for 50

Self-Service Desktop Migrator,
customizing 13, 49, 50, 107
Self-Service Desktop Migrator, distribution
of 49
Self-Service Desktop Migrator, silent
mode: see silent mode operation ...
Self-Service Desktop Migrator User
Guide 50
Setup.exe, to install Quest software: see
installing
shared address books, migration of 79
shared folders, migration of 13, 79, 115
silent mode operation of Self-Service
Desktop Migrator 50, 51
staff changes during migration 44
SuccessLog file for Addproxy utility 46,
92, 94
synchronization of directories 25, 28, 43,
44, 45, 48, 122
system requirements: see GroupWise

Migrator for Exchange, requirements
T
temporary subdomain for migration 41,
52, 67, 73
test migration 37, 122
127
128

GMEUser Guide

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

GMEUser Guide

Enviado por

Direitos autorais:

Formatos disponíveis

User Guide

Quest GroupWise Migrator for Exchange

2007 Quest Software, Inc.

PRE-MIGRATION PLANNING AND TESTING . . . . . . . . . . . . . . . .23

TEST AND PILOT MIGRATIONS . . . . . . . . . . . . . . . . . . . .37

Quest GroupWise Migrator for Exchange

CHAPTER 2: MIGRATION PROCESS INSTRUCTIONS . . . . . . . . . . . .39

BATCH MIGRATION PROCESS (PER USER GROUP) . . . . . . . . . . .44

MIGRATION PER DESKTOP . . . . . . . . . . . . . . . . . . . . . . . . . .48

Command-Line Switches for

POST-MIGRATION CLEAN-UP . . . . . . . . . . . . . . . . . . . . . . . .52

7: SPECIFY GROUPWISE PASSWORDS . . . . . . . . . . . . . . .68

Quest GroupWise Migrator for Exchange

20: SPECIFY PST OUTPUT ROOT DIRECTORY . . . . . . . . . . .82

ADDPROXY.INI SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . .93

APPENDIX B: AD OBJECT MERGE TOOL . . . . . . . . . . . . . . . . . . .97

TO GENERATE A USER-LIST .CSV FILE

TO GENERATE A REPORT OF THE LOG FILE . . . . . . . . . . . . 106

Filter Conditions in the

HIDING ENTIRE SCREENS FROM THE USER . . . . . . . . . . . . . . . 111

Quest GroupWise Migrator for Exchange

About This Guide

How To Use the Product Documentation

About Quest Software

Contacting Quest Software

Contacting Customer Support

Quest GroupWise Migrator for Exchange

How To Use the Product Documentation

Quick-Start Guide: An orientation to the product's basic purposes

GroupWise Migrator for Exchange User Guide: The document

Self-Service Desktop Migrator User Guide: Operating instructions

Introduction and Planning: An orientation to the products

Migration Process Instructions: Step-by-step instructions for how

Directory Exporter: Operating instructions and application notes

Administrator-Driven Batch Migrator: Operating instructions and

Addproxy Utility: Operating instructions and application notes.

AD Object Merge Tool: Operating instructions and application

Log File Viewer: Operating instructions and application notes.

Customizing the Self-Service Desktop Migrator Program.

How GroupWise Migrator for Exchange Maps Shared Folders

Known Limitations of the Migration Process.

We strongly recommend that all administrators read all of:

The Quick-Start Guides Product Overview and two Walkthrough

Quest GroupWise Migrator for Exchange

You may then follow the appropriate process instructions in chapter 2 to

This word refers to actions such as choosing or highlighting

Interface elements that appear in Quest products, such as

Used for comments.

Bold Italic text

Used for emphasis.

Indicates a cross-reference. When viewed in Adobe

A plus sign between two keystrokes means that you must

A pipe sign between elements means that you must select

About Quest Software

Contacting Quest Software

949.754.8000 (United States and Canada)

Quest Software, Inc.

Contacting Customer Support

You can use SupportLink to do the following:

Create, update, or view support requests

Search the knowledge base

Quest GroupWise Migrator for Exchange

Pre-Migration Planning and Testing