Migrator for GroupWise 4.7.1 - Scenarios Guide

Step 9: Run Quest Directory Exporter

Migrator for GroupWise’s Directory Exporter extracts user and group data from the GroupWise environment and creates CSV data files that feed input data to other Migrator for GroupWise applications. Run the Directory Exporter to generate the necessary data files. For more information and operating instructions for the Directory Exporter program, see the Directory Exporter chapter in the Migrator for GroupWise Administration Guide.

Step 10: Review CSV files to verify attributes and matching attributes

The CSV data files generated by Directory Exporter provide critical input to other Quest programs, so it is important to verify that the information is accurate and properly formatted. This verification step also provides an opportunity to update addresses and other attributes as required before initiating migrations. For example, the content may be modified to facilitate the organization's consolidation to a new SMTP domain as part of the migration process.

It is also important to verify the matching criteria that will be used for the merge process later in this procedure. If Quest Migrator for NDS was (or will be) used to create security principals, the Migrator for NDS SQL database can be leveraged by Migrator for GroupWise to locate and update the user objects.

If mail-enabled users already exist in an existing Active Directory: Make sure the addresses listed in the TargetAddress and TargetAlias columns are appropriate. With existing mail-enabled users, Migrator for GroupWise will use the TargetAddress to locate the object for mailbox creation. The address in the TargetAddress of the CSV must therefore match a valid SMTP address on the target mail-enabled object. Also, the TargetAlias addresses will be applied as secondary/proxy addresses, so it is important to verify them before proceeding.

If Migrator for NDS is not used but AD objects still must be created, Migrator for GroupWise must still be able to match the exported GroupWise user records to the AD objects to perform some of its operations. If the AD objects must be merged or mail- enabled by Migrator for GroupWise, an attribute must be identified and/or populated into the CSV input files to establish a match between the GroupWise user and corresponding security principal in AD. The Directory Exporter extracts the NDSUserName, which commonly matches to the SAMAccountName in AD. If this is the case in your environment, simply copy the values from the NDSUserName column into the SearchKey column within the UsersToMerge.csv (or UsersToMigrate.csv). The resulting file can be used as the template to generate user lists for the merge and migration.

If alternate matching criteria are required, one of the additional attributes within UsersToMerge.csv can be used, or a match can be forced using the SearchKey column within the CSV. To force a match, a common approach is to export the existing objects from Active Directory and use the export file to populate the SearchKey column within the CSV. This may be done through macros or scripting, but sometimes requires manual intervention as well.

When the SearchKey column contains appropriate values for locating and merging the AD security objects, save the CSV file and use it as the template for creating lists of users for the merge and migration process.

Step 11: Provision AD with NDS users and groups

NOTE: This step applies only if security objects do not already exist in AD. If the security objects already exist in AD, skip ahead to the next step.

The existing NDS users and groups must be provisioned as security principals in Active Directory. Quest CMG Directory Connector or Migrator for NDS (separate Quest products, not part of Migrator for GroupWise) offers the most complete migration capabilities for this task, but other methods are also possible.

In a later step you may run Migrator for GroupWise’s AD Object Merge Tool to mail-enable these accounts. Functional integration between the AD Object Merge Tool and CMG’s Directory Connector or Migrator for NDS streamline this process.

You could also use Migrator for GroupWise’s Admin Batch Migrator to provision Active Directory and create Exchange mailboxes directly from contact objects. This can be a valuable feature in environments where security principals do not already exist in AD, and CMG is used to create routing contacts in AD. This approach is also useful for provisioning resource objects in some migrations. For more information, see the MBoxFromContact parameter in the Migrator for GroupWise Program Parameters Reference.

Step 12: Verify target/forwarding addresses

As Migrator for GroupWise migrates users to Exchange, new mailboxes will be created in Exchange for the migrating users. Migrated users will need to communicate with users still residing in GroupWise, and will rely on existing mail-enabled objects to do so. The routing address must therefore be verified and tested to ensure proper delivery back to the GroupWise environment.