Migrator for GroupWise 4.7 - Administration Guide

Administrator-Driven Batch Migrator

Why and when to use the Admin-Driven Batch Migrator

The Administrator-Driven Batch Migrator is a multi-function application that lets you perform various functions in various combinations in a single program run. Certain screens in 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:

In a typical migration scenario the Administrator-Driven Batch Migrator is run twice for each migration group: first to perform administrative functions, and then again to migrate the user data. In the migration process (chapters 2 and 3 of the Migrator for GroupWise Scenarios Guide), the Admin Batch Migrator is run at steps 4 and 6 of each pass through the Batch Migration Process loop (per user group). The Batch Migrator is then run again after the last group, to provision public distribution lists (PDLs) as Exchange distribution groups.

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

Before running the Admin-Driven Batch Migrator ...

A GroupWise message contains several standard attributes such as the From, To and Subject fields, and can also include user-defined fields. Migrator for GroupWise’s Admin Batch Migrator and SSDM can migrate custom GroupWise message attributes to unused properties in the MAPI target mailboxes, but only if the migration application knows which properties in the target correspond to which attributes in the source. The migration of custom attributes therefore requires that an admin map these source-to-target attribute associations in a tsv data file, before the migration, so the migration applications can refer to that file to migrate the attributes.

The attribute-mapping file must be a unicode (not ANSI) file named customattrs.csv, in the default installation folder for the Admin Batch Migrator (typically C:\Program Files\Quest\Migrator for GroupWise for a 32-bit OS, or C:\Program Files (x86)\Quest\Migrator for GroupWise for a 64-bit OS), and in the folder containing gwdtapp.exe if you want to migrate GroupWise custom attributes via the SSDM. Migrator for GroupWise installs an attrs.csv file, with the same column headings required for customattrs.csv, that you can use as a template to create the customattrs.csv file.

If you want to migrate GroupWise custom message attributes

A GroupWise message contains several standard attributes such as the From, To and Subject fields, and can also include user-defined fields. Migrator for GroupWise’s Admin Batch Migrator and SSDM can migrate custom GroupWise message attributes to unused properties in the MAPI target mailboxes, but only if the migration application knows which properties in the target correspond to which attributes in the source. The migration of custom attributes therefore requires that an admin map these source-to-target attribute associations in a tsv data file, before the migration, so the migration applications can refer to that file to migrate the attributes.

The attribute-mapping file must be a unicode (not ANSI) file named customattrs.csv, in the default installation folder for the Admin Batch Migrator (typically C:\Program Files\Quest\Migrator for GroupWise for a 32-bit OS, or C:\Program Files (x86)\Quest\Migrator for GroupWise for a 64-bit OS), and in the folder containing gwdtapp.exe if you want to migrate GroupWise custom attributes via the SSDM. Migrator for GroupWise installs an attrs.csv file, with the same column headings required for customattrs.csv, that you can use as a template to create the customattrs.csv file.