GroupWise Migrator for Exchange - NDM Technologies · 2011. 6. 9. · Quest GroupWise Migrator for...

3.7GroupWise Migrator forExchange

Administration Guide

Quest GroupWise Migrator for Exchange

GME Administration GuideUpdated - June 2010 (Doc ID 154)Software Version - 3.7

© 2010 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 Email: [email protected] Dept Website: www.quest.com5 Polaris WayAliso Viejo, CA 92656 USA

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

TRADEMARKS

Quest, Quest Software, and the Quest Software logo are trademarks and registered trademarks of Quest Software, Inc. in the United States of America and other countries. For a complete list of Quest Software’s trademarks, please see http://www.quest.com/legal/trademark-information.aspx. Other trademarks and registered trademarks are property of their respective owners.

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.

mailto:[email protected]

http://www.quest.com/

http://www.quest.com/legal/trademark-information.aspx

CONTENTS

ABOUT THIS GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .VII

OTHER GME DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . VIII

CHAPTER 1THE MIGRATION PROCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

NECESSARY PRE-MIGRATION PREPARATIONS . . . . . . . . . . . . . . .10BATCH MIGRATION (PER USER GROUP) . . . . . . . . . . . . . . . . . .15PER-DESKTOP MIGRATIONS . . . . . . . . . . . . . . . . . . . . . . . . .21POST-MIGRATION CLEAN-UP . . . . . . . . . . . . . . . . . . . . . . . .24

CHAPTER 2ADDPROXY UTILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

WHY AND WHEN TO USE ADDPROXY . . . . . . . . . . . . . . . . . . .26ADDPROXY PREREQUISITES . . . . . . . . . . . . . . . . . . . . . . . . .26INSTALLING ADDPROXY . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

DID IT WORK? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

UNINSTALLING THE ADDPROXY PROGRAM . . . . . . . . . . . . . . .28

ADDPROXY.INI SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . .28

CHAPTER 3DIRECTORY EXPORTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

WHY AND WHEN TO USE THE DIRECTORY EXPORTER . . . . . . . . . .32OPERATING INSTRUCTIONS. . . . . . . . . . . . . . . . . . . . . . . . . .33DID IT WORK?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34MODIFY (IF NECESSARY) THE DATA FILES . . . . . . . . . . . . . . . .34

CHAPTER 4AD OBJECT MERGE TOOL. . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

WHY AND WHEN TO USE THE AD OBJECT MERGE TOOL . . . . . . . .36BEFORE YOU BEGIN ... . . . . . . . . . . . . . . . . . . . . . . . . . . . .36OPERATING INSTRUCTIONS. . . . . . . . . . . . . . . . . . . . . . . . . .37DID IT WORK?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

iii


CHAPTER 5ADMINISTRATOR-DRIVEN BATCH MIGRATOR . . . . . . . . . . . . . . . .41

WHY AND WHEN TO USE THE ADMIN-DRIVEN BATCH MIGRATOR. . .42PER-SCREEN INSTRUCTIONS AND APPLICATION NOTES . . . . . . . . .43

1: WELCOME SCREEN . . . . . . . . . . . . . . . . . . . . . . . . . . .43

2: SELECT OPERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . .43

3: SPECIFY USERS FOR UPDATE . . . . . . . . . . . . . . . . . . . . .45

4: SELECT GROUPWISE ADMINISTRATIVE OPERATIONS . . . . . . .45

5: GROUPWISE FORWARDING OPTIONS . . . . . . . . . . . . . . . .46

6: SPECIFY SOURCE-TO-TARGET MAIL FOWARDING DOMAIN . . . .47

7: SPECIFY GROUPWISE PASSWORDS . . . . . . . . . . . . . . . . .48

8: SELECT GROUPWISE VISIBILITY . . . . . . . . . . . . . . . . . . .49

9: SELECT EXCHANGE ADMINISTRATIVE OPERATIONS . . . . . . . .49

10: SPECIFY ACTIVE DIRECTORY INFORMATION. . . . . . . . . . . .50

11: SPECIFY EXCHANGE MAILBOX INFORMATION . . . . . . . . . . .51

12: SPECIFY TARGET-TO-SOURCE MAIL FORWARDING DOMAIN . .51

13: SPECIFY DATA FOR MIGRATION. . . . . . . . . . . . . . . . . . .52

14: SELECT DATE AND SIZE FILTERS. . . . . . . . . . . . . . . . . .53

15: SPECIFY GROUPWISE INFORMATION . . . . . . . . . . . . . . . .54

16: SPECIFY GROUPWISE LOGIN INFORMATION . . . . . . . . . . .54

17: SPECIFY DESTINATIONS FOR MIGRATED DATA . . . . . . . . . .56

18: SPECIFY HOW TO MIGRATE SHARED INFORMATION . . . . . . .56

19: SELECT DESTINATION EXCHANGE SERVER . . . . . . . . . . . .58

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

21: SPECIFY GROUPWISE DOMAIN PATH . . . . . . . . . . . . . . .60

22: SPECIFY RUN INFORMATION. . . . . . . . . . . . . . . . . . . . .61

23: MIGRATION SETTINGS SUMMARY . . . . . . . . . . . . . . . . . .61

24: PROGRESS SCREEN . . . . . . . . . . . . . . . . . . . . . . . . . .62

25: RESULTS SCREEN . . . . . . . . . . . . . . . . . . . . . . . . . . .62

DID IT WORK?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62REMEMBER TO DISTRIBUTE ANY USER .PST FILES . . . . . . . . . . . .63

iv

CHAPTER 6LOG FILE VIEWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

WHY AND WHEN TO USE THE LOG FILE VIEWER. . . . . . . . . . . . .66TO CHANGE THE SORT ORDER OF THE LOG FILE NAVIGATOR . . . . .68TO GENERATE A USER-LIST .CSV FILEOF "ERROR USERS" (IN THE LOG FILE) . . . . . . . . . . . . . . . . . .68TO GENERATE A REPORT OF THE LOG FILE . . . . . . . . . . . . . . . .69

CHAPTER 7SELF-SERVICE DESKTOP MIGRATOR PROGRAM . . . . . . . . . . . . . . .71

WHY AND WHEN TO USE THE SSDM . . . . . . . . . . . . . . . . . . .72CUSTOMIZING THE SSDM . . . . . . . . . . . . . . . . . . . . . . . . . .72

PROVIDING PROGRAM ENTRY VALUES IN GWDTAPP.INI. . . . . . . .73

HIDING ENTIRE SCREENS FROM THE USER . . . . . . . . . . . . . . .75

HIDING CERTAIN USER CHOICES ONTHE SPECIFY DATA FOR MIGRATION SCREEN. . . . . . . . . . . . . .77

FOR EXAMPLE: TO MIGRATE ARCHIVES ONLY . . . . . . . . . . . . .78

COMMAND-LINE SWITCHES FOR RUNNING SSDM IN SILENT MODE .79DID IT WORK?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

ABOUT QUEST SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

CONTACTING QUEST SOFTWARE. . . . . . . . . . . . . . . . . . . . . . .87QUEST SUPPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87VISIT OUR ONLINE COMMUNITY. . . . . . . . . . . . . . . . . . . . . . .88

v


vi

About This Guide

This Administration Guide was developed to provide:

• Operating instructions and application notes for all of the administrator component applications of Quest’s GroupWise Migrator for Exchange (GME).

• The process instructions for a typical migration project, showing how GME’s component applications are typically used within the broader context of a migration project.

The process instructions appear in chapter 1, with ordered task checklists of all the necessary steps for the three most common migration scenarios: coexis-tence by Microsoft Connectors, coexistence by SMTP mail routing, and migration without coexistence. Some of the steps in these procedures are conditional, depending on your organization’s migration scenario. If you don’t know your migration scenario, be sure to read the GME Pre-Migration Planning Guide to learn about coexistence options and other important planning factors before you begin the process documented in chapter 1.

Chapters 2 through 7 of this guide provide the operating instructions and application notes for GME’s component applications:

• Chapter 2: AddProxy Utility

• Chapter 3: Directory Exporter

• Chapter 4: AD Object Merge Tool

• Chapter 5: Administrator-Driven Batch Migrator

• Chapter 6: Log File Viewer

• Chapter 7: Self-Service Desktop Migrator

This guide is intended for network administrators, consultants, analysts, and any other IT professionals who will use the product or participate in planning for a migration project.

vii


Other GME DocumentationThis Administration Guide is one of several documents that explain various aspects of Quest’s GroupWise Migrator for Exchange product. The complete documentation suite also includes:

• 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. Also includes instructions for downloading and installing the software.

• Pre-Migration Planning Guide: Explanations of critical considerations and other strategic and tactical issues that an organization must consid-er and accommodate before beginning a migration project.

• Self-Service Desktop Migrator User Guide: Operating instructions and application notes for the Self-Service Desktop Migrator component of GroupWise Migrator for Exchange. This SSDM 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.

• Online Help: Context-sensitive field definitions and application notes for all of GME’s component applications.

• GME Program Parameters Reference: Complete reference lists of all program parameters available for all GME component applications.

viii

1

The Migration Process

• Necessary Pre-Migration Preparations• Batch Migration (Per User Group)• Per-Desktop Migrations• Post-Migration Clean-Up


This chapter provides process instructions for what an organization must do to migrate users from GroupWise to Exchange using Quest’s GroupWise Migrator for Exchange—in conjunction with Quest’s NDS Migrator, and Microsoft’s Con-nector and Outlook deployment tools.

The four primary sections of this chapter correspond to the four phases of a migration process:

1. Necessary Pre-Migration Preparations

2. Batch Migration (Per User Group)

3. Per-Desktop Migrations

4. Post-Migration Clean-Up

If your migration strategy does not include either a batch-migration process or any per-desktop migrations, just skip the irrelevant section.

The procedures documented here explain the contexts in which the Quest appli-cations are used, and refer to other chapters of this Administration Guide for component operating instructions and pertinent application notes.

These procedures assume that you have already read the GME Pre-Migration Planning Guide and prepared a comprehensive written Migration Plan, as described in chapter 2 of that guide.

Necessary Pre-Migration PreparationsThis section explains what an organization must do to 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.

The flow chart below summarizes the procedure, and the step numbers in the chart correspond to the step numbers in the more detailed process instructions that follow.

The process begins with existing user accounts and mailboxes on a Novell GroupWise server.

IMPORTANT: If you intend to migrate offline, or to Microsoft’s BPOS-S, or if you intend to use a phased migration strategy, be sure to see the pertinent Variations topic in chapter 4 of the GME Pre-Migration Planning Guide before you begin the standard process instructions documented here.

10


11


Step 1: Install and ConfigureYour Exchange Destination Environment

If you have not yet installed and configured your Exchange destination environ-ment, do it now.

Step 2:Verify that All System Requirements Are Satisfied

All of the system requirements, including the necessary admin accounts and access privileges (see the System Requirements topic in chapter 1 of the Pre-Migration Planning Guide) must be satisfied before you begin this process.

Step 3 (for Proxy Access Only): Prepare the AddProxy Program to Establish User Proxies

Prepare Quest’s AddProxy program to establish proxy access to each user’s account, and modify the network login script of your migrating users to run the AddProxy program when they next login. For complete instructions see the AddProxy Utility chapter below.

Step 4 (for Coexistence Only):Configure Your Coexistence Strategy

Coinfigure your coexistence strategy by doing one (not both) of the following:

• For coexistence by the Microsoft Connectors: Refer to Microsoft’s documentation to install and configure the Microsoft Connectors.

• For coexistence by SMTP mail-routing: Create a temporary MX sub-domain for the migration (e.g., migrate.domain.com) and specify it in DNS. The subdomain should direct traffic to the new Exchange environment. Mail

Important: If you intend to use the Microsoft Connectors for email and calen-dar coexistence, you must migrate either to an Exchange 2003 destination, or to a mixed Exchange 2003-2007 environment with an Exchange 2003 bridge-head server—as described in chapter 2 of the Pre-Migration Planning Guide.

Important: Remember that the GME migration profile on the admin work-station cannot be in cached mode or the migration will fail.

Conditional Step: This step applies only if the Admin-Driven Batch Migrator will access user source data by proxy. If the program will access source data by password, or as a Trusted App, skip ahead to the next step.

Conditional Step: This step applies only if you will use the MS Connectors or SMTP mail routing for coexistence. If you will migrate without coexistence, skip ahead to the next step.

12


from other GroupWise users arriving in the GroupWise accounts of migrat-ed users will be forwarded to the appropriate mailboxes in the Exchange environment using the migrate.domain.com subdomain. After you create the new subdomain, be sure to 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.

Step 5:Provision Active Directory with NDS Users and Groups

Provision NDS users and groups as security objects and security groups, respec-tively, in Active Directory. Quest’s 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 a later step below you will run Quest’s AD Object Merge Tool to mail-enable these accounts, but the AD Object Merge Tool cannot be run until after the Direc-tory Exporter has run (next step below).

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 the Directory Exporter chapter below.

Since the data files generated by the Directory Exporter are necessary input files for other Quest programs, it is important to verify that their information is prop-erly formatted. This verification 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. For more information about verifying and editing the contents of these files, see in the Directory Exporter chapter: Did It Work? and Modify (If Necessary) the Data Files.

Step 7: Mail-Enable All Users’ AD Accounts

Run Quest’s AD Object Merge Tool to update and mail-enable the new Active Directory accounts, which will facilitate Exchange-to-GroupWise mail-routing for not-yet-migrated users throughout the transition period.

The AD Object Merge Tool applies its functions to AD accounts identified in a UsersToMerge.csv file that you specify during the program run. (A suitable UsersToMerge.csv file is generated by the Directory Exporter.) For each user listed in the file: If an Exchange Contact address matches the GroupWise

13


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 SourceAd-dress from UsersToMerge.csv into the AD security object, to mail-enable the object. See the AD Object Merge Tool chapter below for more information and operating instructions.

Step 8: Provision Public Distribution Lists in Exchange

Run the Administrator-Driven Batch Migrator to provision GroupWise public dis-tribution lists (PDLs) as Exchange distribution groups. The program reads a data file generated by the Directory Exporter, GroupsToProvision.txt, 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 (Per User Group) below. For operating instructions and application notes, see the Administrator-Driven Batch Migrator chapter below.

Step 9: 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-enabled—before, during or after the actual migration. But since each "hop" in the forwarding route adds either complexity to the message header or a greater burden on the Connector (depending on the routing method), many admins try to minimize the hops by modifying the DNS about halfway through the migration process.

Step 10: 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 includes a directory synchronization (via Microsoft’s Connector) that will function properly only if the Quest program first removes all GroupWise source addresses (gwise:proxy-Addresses), so that mailbox-enabled accounts in AD can be synchronized back to GroupWise as external users. If RemoveSrcAddresses=0 (default), only the gwise:uid- address is removed.

14


Step 11 (If Necessary): Move Users’Archives to a Centralized, Accessible Location

The Admin-Driven Batch Migrator can migrate users’ GroupWise archives to Exchange, but only if the program can find the source archives on the GroupWise server. The program can also migrate archives from diverse, per-user locations, but only if you specify the location for each user in your user-list .csv file—as explained in the Batch Migration (Per User Group) procedure below.

If your GroupWise network is not already configured for your users’ archives 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 (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 Per-Desktop Migrations section of this chapter below.

This section provides process instructions for a typical migration, in which an administrator performs the migrations for multiple groups (batches) of users with no user interaction. These instructions describe the process for either method of access to user data—by password or by proxy—and apply to all three migration scenarios: coexistence by Microsoft Connector, coexistence by SMTP mail routing, and migration without coexistence.

The flow chart on the next page summarizes the procedure, and the step num-bers in the chart correspond to the step numbers in the more detailed process instructions that follow. Remember that the procedure must be repeated for each group of users to be migrated.

Do not begin this procedure until you have completed the Necessary Pre-Migra-tion Preparations listed in the preceding section of this chapter.

15


16


Step 1 (for Connector Coexistence Only): DirSync and Update Exported Data for Recent Staff Changes

Many migration projects extend over a period of at least several days, some for several weeks or even months. It is entirely possible therefore that an organi-zation will experience staff additions and departures during the transition period. Any staff changes that occur while the migration project is in-process may intro-duce data inconsistencies between the old and new servers, but these inconsis-tencies can be reconciled during a period of directory coexistence.

If your transition period will be brief enough that you don’t require coexistence, 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 depar-tures that occur after the migration is completed. (If this is the case, you may skip this step.)

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:

1. Make sure that any staff changes since the last dirsync have been entered into the GroupWise NDS. (Someone can simply enter these changes into NDS as they occur, just as you always have.)

2. Make sure that any already-migrated users who have left the organization since the last dirsync are deleted from Active Directory. (Again, someone can simply record these departures as they occur, using Exchange admin software.)

3. Run Microsoft’s Connector for GroupWise to re-synchronize the directories, from GroupWise to Exchange (only).

4. Re-run Quest's Directory Exporter to generate new, updated .csv data files that will accurately reflect the current staff list. (For more details, see the Directory Exporter chapter below.) Remember to review the new data files and, if necessary, edit them.

Conditional Step: This step applies only if you will use the MS Connectors for coexistence. If you will use the SMTP mail-routing method, or will migrate without coexistence, skip ahead to the next step.

Note: The Microsoft Connector can be configured to automati-cally run dirsyncs at scheduled intervals—for example, every night at midnight local time, or at 2am. If your Connector is configured for regular dirsyncs, then you need not perform another dirsync in this step for every migrating batch.

17


Step 2: Prepare a Migration Group User-List .csv File

Quest’s 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. The way you prepare your user-list .csv file depends on whether the program will access users’ GroupWise accounts by proxy, or by password. (This choice is explained in chapter 3 of the GME Pre-Migration Planning Guide—see Method of Access to GroupWise User Data.)

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 in the Directory Exporter step 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 filename (for example, migr01.csv for your first migration group, or migmktg.csv for 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 Method of Access to GroupWise User Data in chapter 3 of the GME Pre-Migration Planning Guide): Add a Password column to the .csv file, and enter each user’s password value into this column.

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.

Preparing a User-List .csv File for the Proxy-Access Method

If your Admin-Driven Batch Migrator program will access users’ GroupWise data by proxy, you can use the .csv file generated by Quest’s AddProxy program as your user-list file. The AddProxy Utility chapter 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 Quest’s Administrator-Driven Batch Migrator.

18


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 modifica-tions to the user-list .csv file.

Quest’s 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

This information applies to both GroupWise-access methods: by password or by proxy. 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’ indi-vidual 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=AdministrativeGroups,CN=User,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Example,DC=com

Note that the Exchange admin credentials for the Admin-Driven Batch Migrator must have sufficient rights to create mailboxes on the Exchange server(s) spec-ified in this HomeMDB column. If the HomeMDB column is left blank, the pro-gram 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

This information applies to both GroupWise-access methods: by password or by proxy. Some circumstances and optional features may require other additions to the user-list .csv file. Contact Quest Technical Support ([email protected]) 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 user’s data.)

19



• You want user PST files in Exchange to reside in different, separate directories, per user (for example, in each user’s 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 Admin-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 the Administrator-Driven Batch Migrator chapter for complete instructions and application notes.

Step 4 (for Connector Coexistence Only): Reverse-Sync AD Back to NDS

Before you run Microsoft’s 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 Microsoft’s Exchange Connector for GroupWise to perform a reverse synchronization of the two directories, from Exchange back to GroupWise.

Conditional Step: This step applies only if you will use the MS Connectors for coexistence. If you will use the SMTP mail-routing method, or will migrate without coexistence, skip ahead to the next step.

20


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 the Administrator-Driven Batch Migrator chapter 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 file-name if more than one file is generated per User ID — for example, Smith.pst, Smith-1.pst, Smith-2.pst, and so forth.

Per-Desktop MigrationsRemember that batch migrations and per-desktop migrations are performed with different Quest tools. For batch migration (multiple users at a time, per-formed by an administrator), see the preceding section of this chapter: Batch Migration (Per User Group).

Quest’s Self-Service Desktop Migrator (SSDM) is used by an end user, or by an administrator on behalf of an end user, to extract a single user’s GroupWise data 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 user’s 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 SSDM themselves to ensure a smooth transtion for top executives, or for less experi-enced end users who might be uncomfortable running the tool for themselves.

21


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 prepara-tory tasks are performed just once for all users—not 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 informa-tion about updating these files, see step 1 of the preceding Batch Migration (Per User Group) section.

Customizing the Self-Service Desktop Migrator

Quest’s 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 a later chapter of this guide: 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.

Distribution of SSDM Program and Notifications to End Users

If your users (rather than you) will run the Self-Service Desktop Migrator, they will need access to the program. The most common methods of distribution are:

• 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.

The SSDM requires access to the AddressTranslation.csv and AddressTransla-tion.bin files, generated by the GME Directory Exporter, to convert addresses in messages, address books, and frequent contacts to the appropriate Internet address for each user. Make sure that all users have access to the share that contains those files, in your Quest programs folder.

These files are generated by the GME Directory Exporter, so if they do not exist you will have to run the Directory Exporter to create them.

22


• 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.

You will need to tell your users where the SSDM 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 program—at some network location accessible to all users—so 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 user’s point of view. The SSDM 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 SSDM program to your users, or simply add it to the email as an attachment.

Command-Line Switches forRunning the Desktop Migrator in Silent Mode

The Self-Service Desktop Migrator can be customized to skip certain screens, or even to hide all screens—to 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 obtain-ing the information it would otherwise collect from fields on the screen.

The program can read and/or infer some entry values from the operating envi-ronment—from the Windows Registry and Outlook’s initialization files—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. A complete list of all available command-line switches for the gwdtapp command appears in the Self-Service Desktop Migrator Program chapter of this guide.

If a User Does Not Appear To Be Migrated(After Running the SSDM)

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 (see preceding section). 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 can’t find that infor-mation in the .ini file, and if the screen that ordinarily collects it has been hidden, the function will fail and the user’s data will not be fully migrated. This is a likely

23


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 the Self-Service Desktop Migrator Program chapter for more information about customizing the SSDM by setting parameters in the gwdtapp.ini file.

Post-Migration Clean-UpTo "clean up" after the last user has been migrated

1. Verify the GroupWise server is inactive. Make sure that the GroupWise server is no longer receiving or processing mail traffic.

2. If you were using SMTP mail coexistence: Delete the tempo-rary "migrate.domain.com" MX domain. This is the temporary subdomain you created in the Necessary Pre-Migration Preparations, to permit mail-forwarding between the old and new servers during the transition. 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. If you no longer need the GroupWise environment: Decom-mission the GroupWise server. After you have verified that the GroupWise server is no longer receiving or processing mail traffic, you may decommission the environment.

24

2

AddProxy Utility

• Why and When To Use AddProxy

• AddProxy Prerequisites

• Installing AddProxy• Did It Work?

• Uninstalling the AddProxy Program

• Addproxy.ini Specifications


Why and When To Use AddProxyUse the AddProxy utility if you have determined that this is the best way for the other GME applications to access your users’ GroupWise source data. This choice, and other options, are explained in chapter 3 of the GME Pre-Migration Planning Guide—see the topic Method of Access to GroupWise User Data.

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 log file. The .csv log file can then serve as the user-list input file for Quest’s Administrator-Driven Batch Migrator program.

The AddProxy utility should be installed and configured to run early in the pre-migration process, as documented in chapter 1 of this Administration Guide—see Necessary Pre-Migration Preparations. AddProxy will run only upon each user's next login, but that may not be a daily or even weekly occurrence for some users. Quest therefore recommends that you install and configure AddProxy at step 3 of the Pre-Migration Preparations. The process instructions then call for several other administration tasks in the Pre-Migration Preparations and Batch Migration Process instructions before the first migration program run, which should allow enough time for most users to log off and back on again.

AddProxy PrerequisitesYou 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.

(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.)

26

AddProxy Utility

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 AddProxyTo install and configure Quest’s AddProxy utility:

1. 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. Example:

\\xyzsrv\sys\public\addproxy

2. 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 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 user’s Windows’ registry at HKEY_CURRENT_USER\Software\Wingra Technologies\GroupWise Migrator\AddedProxies, in the form of a new DWORD Value of the user and the proxy user, like this:

[email protected]:[email protected]

27


AddProxy will not run more than once for any single user unless the configuration settings, such as a new proxy user, have changed. The parameter setting Force=1 in the addproxy.ini file will override this and always force AddProxy to run, regardless of the registry setting.

Did It Work?

To determine whether the AddProxy utility is working, check the SuccessLog file to see whether user runs of the program are being recorded there. The AddProxy program automatically logs each successful run in its log file for successes— designated by the SuccessLog= parameter in addproxy.ini.

Uninstalling the AddProxy Program

After all users have run the AddProxy program, remove the line that runs AddProxy from your network login script(s) — the line 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 SpecificationsThe 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=questMigrationID=xyzcorpLicenseKey=KAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxUser=proxyuser@xyzcorp.comUserGroupWiseAddr=proxyuser.gwpo.gwdomForce=1AllowSearch=0SuccessLog=\\SERVER\VOLUME\PUBLIC\ADDPROXY\addproxy.csvFailureLog=\\SERVER\VOLUME\PUBLIC\ADDPROXY\addproxyerr.csvAllowAdd=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.

28

AddProxy Utility

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

• 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 user’s proxy settings more than once. If set to "0" (the default), the program will update a user’s 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,Status8/4/2003 7:56:14,Joe Blow,JBLOW.GWPO.GWDOM, [email protected],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,ErrorText8/4/2003 7:51:44,Joe Blow,JBLOW.GWPO.GWDOM,[email protected],Can’tfind user...

• 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.)

29


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 settingsThe 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.

30

3

Directory Exporter

• Why and When To Use the Directory Exporter• Operating Instructions• Did It Work?• Modify (If Necessary) the Data Files


Why and When To Use the Directory ExporterQuest’s 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.txt: 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. Quest’s 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.)

Since other GME components require these data files as inputs, the Directory Exporter must be run before the first run of any Quest migration program or the AD Object Merge Tool. In our Migration Process instructions (chapter 1), the first Directory Exporter run occurs in step 6 of the Necessary Pre-Migration Preparations.

Then, throughout the transition period, the Directory Exporter may be re-run as necessary to update the program’s data files, following each directory synchronization (to accommodate staff changes recorded in GroupWise during the transition period). If you are using the Microsoft Connector for coexistence, these dirsync and Directory Exporter re-runs occur as the first step of each Batch Migration (Per User Group).

32

Directory Exporter

Operating InstructionsStart the Directory Exporter from your computer’s Start menu, in the Group-Wise Migrator for Exchange program group. To use the Directory Exporter:

1. Review the Welcome screen and click Next.

2. Enter the requested GroupWise System Information and click Next.• Admin user ID: The name of the admin’s GroupWise account (not the

Novell account).• Admin password: The password for the admin’s 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’ 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 progress while the export process is running, and the program automatically advances to the next screen (Finished) when the process is finished.

3. On the Finished screen: Note the location of the program files and click Exit.

This Finished screen may also offer an Error Log Report button 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 Quest’s Log File Viewer utility (see the Log File Viewer chapter) to help you interpret and resolve the errors or warnings.

33


Did It Work?The first and simplest way to verify that Quest’s Directory Exporter has done its job is to see whether it has generated its four output data files in your Quest programs folder:

• GroupsToProvision.txt AddressTranslation.csv• UsersToMerge.csv UsersToMigrate.csv

Since these files contain critical input data for other GME applications, it is important to verify that the information they contain is properly formatted.

All three .csv files contain essentially the same data, so you can open any one .csv file to look for 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. A .csv (comma-separated values format) file is a simple 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.

GroupsToProvision.txt is also a simple text file that you can open with any text editor to verify that it is free of the same sorts of format or translation errors.

Modify (If Necessary) the Data FilesThe 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 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 environ-ment. If you do decide to edit any addresses in the .csv files, remember:

• 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.

34

4

AD Object Merge Tool

• Why and When To Use the AD Object Merge Tool

• Before You Begin ...

• Operating Instructions

• Did It Work?


Why and When To Use the AD Object Merge ToolThe AD Object Merge Tool is used for either or both of two purposes:

• To mail-enable existing AD objects. Quest’s NDS Migrator copies data from NDS to create security objects in AD, or to add NDS data to existing AD objects, but the AD objects are not mail-enabled by this process. Or you may already have AD up and running, and populated with security objects, for network authentication. In either case, we use the AD Object Merge Tool to merge GroupWise source addresses into the AD accounts.

• To consolidate duplicate objects in AD. 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.

We list the AD Object Merge Tool as our tool of choice for mail-enabling in step 7 of the Necessary Pre-Migration Preparations. The AD Object Merge Tool updates and mail-enables Active Directory accounts identified in a UsersTo-Merge.csv file specified during the program run. Since that data file is generated by the GME Directory Exporter, the AD Object Merge Tool cannot be run until after the Directory Exporter (Necessary Pre-Migration Preparations step 6).

For each user, if an Exchange Contact address matches the GroupWise Source-Address 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 corre-sponding Contact exists, the program simply merges the SourceAddress from UsersToMerge.csv into the AD security object, to mail-enable the object.

Before You Begin ...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 Operating Instructions 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.

36


Also, if you will run the AD Object Merge Tool for Exchange 2003, the RUS will remove users’ GWISE proxy addresses if it doesn’t 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 2010 or 2007.)

Operating Instructions1. Start the AD Object Merge Tool from your computer’s 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. On the Specify Users for Update screen: Enter the requested infor-mation and click Next.• Input user list (.csv) file: Use the Browse button to locate and specify

the user-list .csv file for this program run, or just type the path and file-name into the text box. The Directory Exporter automatically generates a UsersToMerge.csv file that you may use for this purpose.

• Target Exchange System: Specify your migration destination environ-ment from the drop-down list.

• Provision users if not found: Mark or unmark the checkbox to indicate whether you want the program to create a new mail-enabled object in AD if none is found to correspond with a user in the user list. A checkmark here tells the program to display another screen, on which you will specify where and how you want any such new objects provisioned.

4. On the Specify AD Information screen: Specify the Active Directory information and provide the administrator credentials and other information Exchange will need to perform the selected administra-tive functions, and click Next.

• Domain Controller: Specify the PowerShell Domain Controller that the program will call to perform operations in Exchange 2010 or 2007. (Re-quired if migrating to Exchange 2010 or 2007, but ignored if migrating to Exchange 2003.)

• Global Catalog: Type the name of the AD Global Catalog server—for example, servername.mydomain.com.

• 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: Specify the method by which you want the program to identify users within the Active Directory. Select any of the listed options:

37


• Find users from the Quest NDS Migrator database: The output data file created by the NDS Migrator (a separate Quest product). For this option, you must also specify SQL server information (see 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.)

• 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.)

• SQL server, mandatory if you have selected (above) Find users from the Quest NDS Migrator database:

• 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.

5. The Specify Provisioning Information screen appears here only if you told the program (in step 3 above) to Provision users if not found. If you left that option unmarked, skip ahead to the next step below. Otherwise, enter this necessary information on the Specify Provision-ing Information screen and click Next.

• Users Container: Specify the relative domain name of the container where any such program-provisioned users should be created. For example: UserContainer=OU=Migrations. The designated container must already exist.

• Enable Users: Mark or unmark this checkbox to indicate whether you want the program to logon-enable any such program-provisioned users.

6. 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.

7. On the Settings Summary screen: 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 reports the program's progress while the process is running, and the program then automatically advances to the last screen (Results).

38


8. 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 Quest’s Log File Viewer utility (see the Log File Viewer chapter) to help you interpret and resolve the errors or warnings.

Did It Work?A successful run of the AD Object Merge Tool will yield a single mail-enabled security object for each migrating user. Any Contacts that had been duplicates corresponding to existing AD security objects should now be deleted, and the surviving security objects should be mail-enabled with GroupWise addresses.

39


40

5

Administrator-Driven Batch Migrator

• Why and When To Use the Admin-Driven Batch Migrator

• Per-Screen Instructions and Application Notes• Did It Work?• Remember to Distribute Any User .pst Files


Why and When To Use the Admin-Driven Batch MigratorThe 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 each 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 data—any combination of server-based or archived mail, calendar data, or the trash folder, or personal address books—from 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 (chapter 1), the migration of PDLs occurs as step 8 within the Necessary Pre-Migration Preparations, while the administrative tasks and user migrations occur as steps 3 and 5 of the Batch Migration (Per User Group).

The instructions in this chapter cover all uses of the program.

42


Per-Screen Instructionsand Application NotesTo start the Administrator-Driven Batch Migrator program

1. Start Quest’s Administrator-Driven Batch Migrator program from the 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. See the instructions and application notes below for the program’s Welcome screen (screen #1). Then refer to the instructions and notes for other screens as they occur in the program sequence.

1: Welcome ScreenReview 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.

2: Select OperationsThis screen lets you tell the program which of its features you want to use in this program run. Enter the requested information, and click Next.

Four checkboxes let you mark the categories of operations (one or more) you want the program to perform:

• GroupWise administrative functions: Select 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.

Note: 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 pertain only to functions you have not chosen for the current program run. We number the screens here simply for convenient reference, but no single program run would ever include all of the screens.

43


• Exchange administrative functions: Select 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 Quest’s NDS Migrator and mail-enabled by the AD Object Merge Tool.)

• Migrate users: Select if you want to migrate users’ server-based data, and/or archives, and/or personal address books from GroupWise to Exchange.

• Provision distribution groups: Select if you want to provision Group-Wise public distribution lists (PDLs) in 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 and will not appear).

Target Exchange System: Select the migration destination environment from the drop-down list.

Note: 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, and Quest therefore recommends against it unless you have some compelling strategic reason to use the program in this way. Our Batch Migration (Per User Group) process in chapter 1 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: The Provision distribution groups option appears grayed-out (unavailable) here if the program cannot find the GroupsToProvision.txt 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 1 for more information.

44


3: Specify Users for UpdateThis screen appears only if you have chosen, on screen #2: Select Operations, to perform GroupWise or Exchange administrative functions, or to Migrate users.

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 (Per User Group) process, in chapter 1.

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.

• 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.

45


5: GroupWise Forwarding OptionsThis 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:

• 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.

46


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.

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.

Quest’s 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.

47


API Gateway vs. SMTP

If you are using Microsoft’s 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 1), 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.

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.

• Set each user’s 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 user’s 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.

48


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 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.

• 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 Quest’s NDS Migrator and mail-enabled by the AD Object Merge Tool.

49


10: Specify Active Directory Information

This screen appears only if the Exchange administrative functions or Provision distribution groups option was marked on screen #2: Select Operations. Specify the Active Directory server, and provide the administrator credentials and other information the program will need to manipulate Active Directory accounts, and click Next.

• Domain Controller: Specify the PowerShell Domain Controller that the program will call to perform operations in Exchange 2010 or 2007. (Required if migrating to Exchange 2010 or 2007, but ignored if migrating to Exchange 2003.)

• Global Catalog: Type the name of the AD Global Catalog server—for example, servername.mydomain.com.

• 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.

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:

• How users were loaded into Active Directory (only if 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 AD. In a typical migration scenario (documented in chapter 1), user data is loaded into AD 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 AD.

• 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.

50


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 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 InformationThis 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 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.

This is the domain by which mail arriving in Exchange mailboxes can be forward-ed back to users’ GroupWise mailboxes. If you have assigned a temporary MX subdomain to the Exchange server (as in our scenario for SMTP coexis-tence—see step 4 of the Necessary Pre-Migration Preparations), 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.

51


13: Specify Data for Migration

The Specify Data for Migration screen 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 server-based data, you may specify one or more of: Migrate e-mail messages, Migrate calendar data, Migrate trash folder 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 or Migrate trash folder.

• 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:

• 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.

An Organization Object in GroupWise is like a business card associated with one or more users in a personal address book. An Organization Object contains business-wide or similar "entity" information such as the organization name, address, phone and fax number—information that could be shared by several or many users associated with the same organization. When you create a contact, you can enter his/her organization information, and then later link other contacts to that same Organization Object. Or you can create an Organization Object without associating any other contacts with it. GME treats an Organiza-tion Object as another address book entry and migrates it as a contact.

52


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.

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.

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.

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.

53


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 user’s desktop (or have your users run it).

16: Specify GroupWise Login Information

This screen 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 GroupWise PostOffice Path (if you want to access GroupWise via direct mode—see 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 topic Method of Access to GroupWise User Data, in chapter 3 of the GME Pre-Migration Planning Guide.

54


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.

• For GroupWise 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:

[email protected]

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.

• For GroupWise 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 chapter 2), can automate the process of obtaining proxy rights.

• Use user passwords: Option 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: 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.

55


17: Specify Destinations for Migrated Data

This screen 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: a .pst file.

• Address books: Address book data can be migrated to a personal folder (.pst) file or a server-based mailbox. The default: 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: server-based mailbox.

18: Specify How To Migrate Shared Information

This screen 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.

56


A shared folder or address book 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. The GME Pre-Migration Planning Guide (see the Migrating Shared Folders topic in chapter 3) explains how GME maps shared folders to Outlook.

For Shared Folders, choose to migrated shared folders either for each user or only for the owner (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.

• 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 to:

Define Access Control Lists (ACL’s) on the Exchange Server to grant shared rights: Choose either, both, or neither of these options to define ACLs on the Exchange server:

• Use the permissions property of the shared folder: 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.

• Use GroupWise proxy rights: Tells the program to use the GroupWise proxy rights to define the Exchange ACLs.

Also, if you choose to migrate only for the owner, you may:

• 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: This button opens the associated RTF template file for editing, using whatever application is associated with RTF files (usually Microsoft Word) on your desktop. The template filenames are SharedFolderNotificationTemplate.rtf and SharedPabNotification-Template.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.

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.

Note: The program will ignore a checkmark in this field if Migrate-EmptyFolders=0 (in the [GroupWise] section of gwmigapp.ini), and [General] ACLRootVisibleOnly=0.

57


For Shared Address Books, choose to migrated shared address books either for each user or only for the owner (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.

• 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:

• Define Access Control Lists (ACL’s) 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 PABs: Tells the program to post a message in the folder that was shared, explaining how to open the shared item in Exchange.

And if you choose to Post a message, you may also:

• Edit the message body: This button opens the associated RTF template file for editing, using whatever application is associated with RTF files (usually Microsoft Word) on your desktop. The template filenames are SharedFolderNotificationTemplate.rtf and SharedPabNotification-Template.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.

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 program’s 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

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.

Note: The program will ignore a checkmark in this field if Migrate-EmptyFolders=0 (in the [GroupWise] section of gwmigapp.ini), and [General] ACLRootVisibleOnly=0.

58


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.

After you provide your Exchange access credentials, 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 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:

Review the list, and decide whether 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.

When you click Next, Microsoft’s 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.

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.

59


20: Specify PST Output Root Directory

This screen 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.

• 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.)

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

60


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.

22: Specify Run InformationOn 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.)

23: Migration Settings SummaryReview 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.

61


24: Progress ScreenQuest'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.

25: Results ScreenReview 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 Quest’s Log File Viewer utility (see the Log File Viewer chapter) to help you interpret and resolve the errors.

Did It Work?Verifying the outcome of an Admin-Driven Batch Migrator run will require different checks depending on what you have asked the program to do.

• If you used Admin Batch Migrator to provision PDLs: Check Active Directory to see if AD now contains the PDLs.

• If you used Admin Batch Migrator for admin functions: Check NDS and/or AD and/or Exchange to verify that the admin task(s) have been correctly applied.

• If you used Admin Batch Migrator to migrate users: Check Exchange to verify that migrated users are mailbox-enabled, and check with the users to make sure they are receiving mail.

62


Remember to Distribute Any User .pst FilesIf 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 ID—for example, Smith.pst, Smith-1.pst, Smith-2.pst, and so forth.

63


64

6

Log File Viewer

• Why and When To Use the Log File Viewer

• To Change the Sort Order of the Log File Navigator

• To Generate a User-List .csv File of "Error Users" (in the Log File)

• To Generate a Report of the Log File


Why and When To Use the Log File ViewerQuest’s 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 Quest’s Directory Exporter, AD Object Merge Tool, Admin-istrator-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 com-puter’s 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 ways—by user, by error message, and by solution to the problem—so 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.

66

Log File Viewer

• 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 Quest’s on-line database, the Solution topic for the selected error or warning will appear in this pane. (Since this feature retrieves information from Quest’s 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.

67


To Change the Sort Order of the Log File NavigatorEach 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.

68

Log File Viewer

To Generate a Report of the Log FileSelect 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.

69


70

7

Self-Service Desktop Migrator Program

• Why and When To Use the SSDM

• Customizing the SSDM• Providing Program Entry Values in gwdtapp.ini• Hiding Entire Screens from the User• Hiding Certain User Choices on the Specify Data

for Migration Screen• For Example: To Migrate Archives Only

• Command-Line Switches for Running SSDM in Silent Mode

• Did It Work?


Why and When To Use the SSDMQuest’s Self-Service Desktop Migrator (SSDM) is used by an end user, or by an administrator on behalf of an end user, to extract a single user’s GroupWise data 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 user’s 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.

Be sure to complete all of the Necessary Pre-Migration Preparations (chapter 1) before running the SSDM for the first desktop migration. These preparatory tasks are performed just once for all users—not 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 informa-tion about updating these files, see step 1 of the process for Batch Migration (Per User Group), also in chapter 1.

The Migration Process documented in chapter 1 explains the procedural context for running the SSDM. The remaining sections of this chapter explain:

• Customizing the SSDM

• Command-Line Switches for Running SSDM in Silent Mode

Customizing the SSDMThe SSDM 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 optional, 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

If you leave those parameters at their default values, the Desktop Migrator simply runs in its default mode, displaying all screens and all options.

72


Some elements of the SSDM program flow can also be controlled by command-line switches, 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 at the end of this chapter, in the topic Command-Line Switches for Running SSDM in Silent Mode.

Providing Program Entry Values in gwdtapp.iniIf the SSDM 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 environment—from the Windows Registry and Outlook’s initialization files, etc.—and some values can be specified by command-line switches (see Command-Line Switches for Running SSDM in Silent Mode below). 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 inthe 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] [ArchiveData]MigrateArchives=1 MigrateTrashFolder=1MigrateServerMail=1MigratePAB=1 [ServerData]MigrateFreqContacts=1 MigrateTrashFolder=1

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.)

73


The most common use of these parameters is to provide entry values when SSDM is configured to skip the Specify Data screen—by MigrateWhat=skip or MigrateWhat=silent (see Hiding Entire Screens from the User below).

Outlook Profile in the Select Profile Screen

If SSDM finds more than one eligible Outlook profile on the user’s computer, or doesn’t 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 user’s 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 user’s Outlook profile can be specified in the [General] section of gwdtapp.ini by:

[General]SelectedProfile=<ProfileName>

Alternatively, the user’s 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 1 for more information about this and other command-line switches.)

Specifying the user’s 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 user’s profile resides on the user’s own local workstation and is independent of other users’ profiles);

– OR –• a different INI file is prepared for each individual user’s 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 user’s workstation.

Archive Destination Folder inthe Specify Directory for Migrated Archive Screen

The destination folder (path) for the user’s migrated archive can be specified in the [General] section of gwdtapp.ini by:

[General]SelectedPstDir=<path>

74


... where <path> is the full UNC or mapped-drive path (without filename) relative to the user’s 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 theSelect Date and Size Filters Screen

The SSDM lets you specify date limits and ranges for messages to be migrated—to 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.

Hiding Entire Screens from the UserThe SSDM program can be customized to make some of its screen displays "silent"—that is, invisible to the end user—or 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.

75


• 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 user’s 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 Screen Name (in Title Bar) DefaultWelcome= Welcome ................................................ showMigrateWhat= Specify Data for Migration ........................ showFilter= Select Date and Size Filters ...................... no-op*Profile= Select Profile .......................................... skipPstDir= Specify Directory for Migrated Archive........ showSummary= Selection Summary.................................. showProgress= Migrating Data ........................................ showFinished= Migration Report ..................................... show*no-op: Functionally equivalent to "silent," but actually signifies that the parameter value is unassigned—in 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 user’s login credentials.

• Enter Password (occurs between the Selection Summary and Migrating Data screens): This Microsoft prompt for the user’s 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 1 for more information about these and other command-line switches.

76


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, 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 mode—that 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.

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.

77


For Example:To Migrate Archives Only

In the introduction to this section we mentioned the example of an administrator who wants to migrate users’ server mail and address books in batches, and then use the SSDM 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=0AppDoesPabs=0MigrateArchives=1

[ArchiveData]MigrateTrashFolder=1

[Screens]Welcome=skipMigrateWhat=skipProfile=skipPstDir=skipSummary=skipProgress=skipFinished=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 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 user’s 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.)

78


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 user’s 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 program’s screen sequence will be:

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 user’s profile is configured to require these credentials.

3. Migration Report: Will appear in every program run, since Finished=show.

Command-Line Switches for Running SSDM in Silent ModeThe Self-Service Desktop Migrator can be customized to skip certain screens, or even to hide all screens—to 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 obtain-ing the information it would otherwise collect from fields on the screen.

The program can read and/or infer some entry values from the operating envi-ronment—from the Windows Registry and Outlook’s initialization files—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 ....

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:

79


• /silent: Enforces a true "silent" run of the program—for 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 user’s 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.

Did It Work?To verify an SSDM run for any given user, check the user’s Outlook folders to see if his/her mail migrated as it should have, and to see if he/she is now receiving new mail in his/her Exchange mailbox.

If a User Does Not Appear To Be Migrated(After Running the SSDM)

Other sections of this chapter explain how to make some of the SSDM’s 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 informa-tion the "silent" screen would otherwise collect from the user. But if the program can’t find that information in the .ini file, and if the screen that ordinarily collects it has been hidden, the function will fail and the user’s 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."

80

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.

ACLSee Access Control List.

ArchivesFiles 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 user’s own local workstation. (Compare to Server-based data.)

Batch migrationA 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.) GME contains an Administrator-Driven Batch Migrator component that lets an administrator perform batch migrations.

CNSee Common name.

CoexistenceThe 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, typically a container. A common name must be unique within a context. (Compare to Distinguished name.)

ContactAn 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

81


sends email via the source server, or someone in another company with whom an Exchange user corresponds—a customer or a vendor, for example. A contact is associated only with an address, and has no Active Directory account.

csv filesText data files, stored in a structured comma-separated-values (csv) format that uses commas as field delimeters for data tables.

DestinationThe server or environment to which data is migrated. In GME, 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, typically a user, by a series of attribute=value pairs, separated by commas and in a particular order, to define the entire path between the object and the directory root. (Compare to Common name.) The DN contains one attribute=value pair (called a Relative distinguished name, or RDN) for each level of the directory hierarchy, as in these examples:

cn=Susannah McCorkle,ou=marketing,o=My Company,c=UScn=Tony Bennett,ou=marketing,o=My Company,c=UScn=Sarah Vaughan,ou=engineering,o=My Company,c=US

Distribution group, Distribution listSee Public distribution group.

DNSee Distinguished Name.

DNSSee 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, although any particular IP address may be associated with 0, 1 or more domain names. The DNS defines the associations of domain names to their corresponding IP addresses.

82


FQDNSee Fully qualified domain name.

Fully qualified domain nameThe complete domain name for a particular computer (host) on the Internet, specified by a notation whose dot-delimited elements identify all levels of the hierarchy from the top-level domain to the root domain. For example: ParticularHost.XYZCorp.com.

Mail-enabledTrait of an Active Directory object whereby the object’s mail-address attributes (for an address outside the Exchange domain) reside in AD, so AD can forward the object’s mail to its other address. Note that no Exchange mailbox is associated with a merely mail-enabled object. (Compare to Mailbox-enabled.)

Mailbox-enabledTrait of an Active Directory object whereby an Exchange mailbox exists for the object, and the object’s incoming mail is routed to its Exchange mailbox. (Compare to Mail-enabled.)

Migration machineThe computer that will run the Quest migration software applications.

MX recordShort 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.

OwnerFor any particular file, a user who has the most complete authority to view, modify and delete the file.

Per-desktop migrationA process of migrating data, from one server/client environment to another, for a single user per program run. (Compare to Batch migration.) GME contains a Self-Service Desktop Migrator component that performs per-desktop migrations.

83


Phased migrationA 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 migrationA 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.

ProvisioningPopulating a directory with objects (users, resources, and so forth), and the information that characterizes objects.

pst filesThe files in Microsoft Outlook, with a .pst extension, that contain users’ personal storage data—typically the form to which GroupWise archives are migrated.

Public distribution group, distribution listA set of directory objects—users and/or resources—collec-tively defined as a group of message recipients. A single message can be "broadcast" to all members of a distribu-tion group by specifying the single group as the recipient.

RDNSee Relative distinguished name.

Relative distinguished name (RDN)One element or component of a Distinguished name (DN), in the form of an attribute=value pair (e.g., ou=marketing, or cn=Melvin Montgomery) that uniquely identifies the component among the children of its parent. (See Distinguished name.)

Server-based dataEmail 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 [email protected]. SMTP is the default transport protocol for Microsoft Exchange.

84


SMTPSee Simple Mail Transfer Protocol.

SourceThe server or environment from which data is migrated. In GME, NDS and GroupWise client archives are the sources of the migration process.

SynchronizationProcess 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.

TargetThe server or environment to which data is migrated. In GME, Microsoft Exchange and the Active Directory are the targets of the migration process. (Synonymous with Destination in this context.)

Test migrationA partial migration—either with a copy of real data in a separate test environment, or with dummy data in the real, live production environment—to assess the suitability of a Migration Plan before the first full production migration run.

UNC PathA notation (UNC=Universal Naming Convention) to specify the absolute location of a resource (such as a directory or file), in this syntax: \\server\volume\dir\dir\...\file.

User-list .csv fileA comma-separated-values (csv) format data file containing the names of users to whom the features of Quest’s 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 Quest’s Directory Exporter.

85


86

About Quest Software

Now more than ever, organizations need to work smart and improve efficiency. Quest Software creates and supports smart systems management products—helping our customers solve everyday IT challenges faster and easier. Visit www.quest.com for more information.

Contacting Quest SoftwareEmail [email protected]

Mail Quest Software, Inc.5 Polaris WayAliso Viejo, CA 92656USA

Web site www.quest.com

Please refer to our Web site for regional and international office information.

Quest SupportQuest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to SupportLink, our self-service portal. Visit SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

• Retrieve thousands of solutions from our online Knowledgebase

• Download the latest releases and service packs

• Create, update and review Support cases

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

87

http://www.quest.com

http://support.quest.com


http://questsupportlink.quest.com/




http://www.quest.com


Visit Our Online CommunityThe Quest Inside Migration community is an online interactive community dedicated to issues pertaining to:

• Migration of email, identity and applications to the Windows Exchange platform—including migration from Exchange, GroupWise, and Notes.

• Active Directory migrations.

• Migrations from Notes application and Exchange public folders to Sharepoint.

• Coexistence strategies and tools.

System administrators like you join together with Quest developers, architects, QA staff, support staff and tech writers to make the Inside Migration community a place where you can:

• Learn about product releases and betas before anyone else.

• Get access to Quest product leaders and subject matter experts on migration and coexistence.

• Participate in discussion forums, share insights and ideas, and get common questions answered.

You can log in, or register to join the Quest Inside Migration community at: http://migration.inside.quest.com/index.jspa.

88

http://migration.inside.quest.com/index.jspa

INDEX

AAccess Control List 81AD Object Merge Tool 13, 32, 36, 44, 49Addproxy entry in Windows’ registry 27Addproxy prerequisites 26Addproxy utility 12, 18, 55Addproxy, uninstalling 28addproxy.ini file 27, 28AddressTranslation.csv 22, 32, 34admin driven batch migration by

password 18, 20, 43, 45, 48, 55admin driven batch migration by

proxy 18Administrator Driven Batch Migrator 15,

19, 20, 21, 32, 42API Gateway 48archives, location of in GroupWise

environment 15, 19, 21, 54, 72archives, migration of 15attachment size filtering 53auto-decline/delete forwarded

messages 46autoreply 46

Bbatch migration 15batch migration by password 15, 18, 20,

43, 45, 48, 55batch migration by proxy 15, 18batch migrator program 15, 19, 20, 21,

32, 42batch vs per desktop migration 81, 83

Cchanging GroupWise passwords 18, 20,

43, 45, 48, 55coexistence of directories during

transition 81command line switches for SSDM 23common name (CN), defined 81Connector for Novell GroupWise 20Contact (in AD), defined 81creating Exchange mail enabled

accounts 36, 44, 49, 83creating Exchange mailboxes 20, 44, 49,

83

csv file 13, 15, 17, 18, 19, 20, 21, 26, 32, 34, 37, 45, 47, 48, 50, 55, 59, 60

csv files, editing 13, 17, 18, 19, 21, 32, 34, 47, 72

Ddate filter 53date limits for messages to be

migrated 53decommissioning GroupWise server 24Default Recipient Policy 37desktop migration 21, 72, 83direct mode access to GroupWise

server 55Directory Exporter 13, 22, 32directory synchronization 14, 17, 20, 85distinguished name (DN), defined 82distribution groups, migrating 14, 42, 44,

84domain name system (DNS), defined 82

Eemail routing during migration 20, 24, 47end user migration 21, 72, 83end user training and communications 23Error Log Report feature 33, 39, 62Exchange Connector for GroupWise 20Exchange mail enabled accounts 36, 44,

49, 83Exchange mailboxes, creating 20, 44, 49,

83

FFailureLog file for Addproxy utility 27, 29filtering options 75fully qualified domain name (FQDN),

defined 83

GGME (see GroupWise Migrator for

Exchange) 9GroupsToProvision.txt 14, 32, 34, 44GroupWise Directory Exporter 13, 32GroupWise Migrator for Exchange,

requirements 12

89


GroupWise server, decommissioning 24GroupWise, versions supported 26gwdtapp.ini file 22, 23, 72, 79, 80GWISE addresses 37gwmigapp.ini 14, 57, 58

HHomeMDB column in user list csv file 19

Llicense key 43Log File Viewer 66login script, network 12, 26, 27

Mmail enabling 36, 44, 49, 83mail forwarding domain, source to

target 47mail forwarding domain, target to

source 51mail forwarding rules 24, 43, 45, 47, 49mail routing during migration 20, 24, 47mailbox enabling 20, 44, 49, 83mailboxes, creating in Exchange 20, 44,

49, 83merging contacts and security objects in

AD 13, 36Microsoft Exchange Connector for Novell

GroupWise 20migration per desktop 21, 72, 83Migration Report feature 62multiple Exchange Mailstores, migrating

to 19MX (Mail eXchange) record 14, 83

NNDS Migrator 13, 38, 44, 49network login script 12, 26, 27

OOutlook Personal Folders files 21, 58, 60,

63, 84

Ppassword method of migration 18, 20,

43, 45, 48, 55password vs proxy method of access to

GroupWise user data 18, 54

passwords, GroupWise 18, 20, 43, 45, 48, 55

per desktop migration 21, 72, 83Personal Folders files, Outlook 21, 58, 60,

63, 84phased migration strategy 84pilot migration 84post-migration clean-up 24program connection to Exchange

server 58program license key 43provisioning on Active Directory 50proxy method of migration 18proxy vs password method of access to

GroupWise user data 18, 54pst files 21, 58, 60, 63, 84pst files, location of in destination

environment 60public distribution lists, migrating 14, 42,

44, 84purge messages after forwarding 46

QQuest license key 43Quest NDS Migrator 13, 38, 44, 49

Rrecipient policy for temporary

subdomain 13Recipient Update Service 20, 37relative distinguished name (RDN),

defined 84RemoveSrcAddresses= parameter 14routing of mail during migration 20, 24,

47

SSelf Service Desktop Migrator 21, 72, 83Self Service Desktop Migrator User

Guide 23Self Service Desktop Migrator, command

line switches for 23Self Service Desktop Migrator,

command-line switches for 79Self Service Desktop Migrator,

customizing 22, 23, 79Self Service Desktop Migrator, distribution

of 22

90

Self Service Desktop Migrator, silent mode 23, 79, 80

shared address books, migration of 56shared folders, migration of 56silent mode operation of Self Service

Desktop Migrator 23, 79, 80SSDM (see Self Service Desktop

Migrator) 21staff changes during migration 17SuccessLog file for Addproxy utility 18,

27, 28, 29synchronization of directories 14, 17, 20,

85system requirements 12

Ttemporary subdomain for migration 12,

24, 48, 51test migration 85tively 84

UUNC path, defined 85user list csv file 15, 18, 19, 20, 21, 26,

32, 34, 37, 45, 47, 48, 50, 55, 59, 60

user visibility in GroupWise 43, 49UsersToMerge.csv 13, 32, 34, 36, 37UsersToMigrate.csv 18, 32, 34

Vvisibility, user 43, 49

91


92

Date post:	29-Aug-2020
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

GroupWise Migrator for Exchange - NDM Technologies · 2011. 6. 9. · Quest GroupWise Migrator for...

Documents