Chat now with support
Chat mit Support

Migrator for GroupWise 4.7.1 - Administration Guide

About this guide AddProxy utility Directory Exporter AD Object Merge Tool Administrator-Driven Batch Migrator
Why and when to use the Admin-Driven Batch Migrator Before running the Admin-Driven Batch Migrator ... Online search feature Per-screen instructions and application notes Did it work? Remember to distribute any user .pst files
The Log Viewer Office 365 Admin Account Pool Utility Discovery utility

Did it work?

The first and simplest way to verify that Quest Directory Exporter has done its job is to see whether it has generated its four output data files:

 

 

In Migrator for GroupWise Program Folders:

GroupsToProvision.txt
UsersToMerge.csv
UsersToMigrate.csv

In Migrator for GroupWise Shared Subfolders:

AddressTranslation.csv

Since these files contain critical input data for other Migrator for GroupWise 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 files

The 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 environment. 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.
* 
NOTE: The Directory Exporter will replace an apostrophe in a user's SMTP address with an underscore character ("_") in the TargetAddress as stored in the CSV file. Also, when creating Exchange accounts, Migrator for GroupWise will replace any apostrophe that occurs in the TargetAddress in the CSV file with an underscore character ("_"). Please see TFS 227717 for detail.
•
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.

AD Object Merge Tool

•
Why and when to use the AD Object Merge Tool
•
Before you begin...
•
Online search feature
•
Per-screen instructions and field notes
•
Did it work?

Why and when to use the AD Object Merge Tool

The AD Object Merge Tool is used only when provisioning to a local, proprietary Active Directory—either as a final destination, or as an intermediary (when using Microsoft’s DirSync tool to provision from a local AD to Office 365).

The AD Object Merge Tool does not provision directly to an Office 365 target Active Directory. A hosted AD (for Office 365) is provisioned either with Microsoft’s DirSync tool, or can be provisioned directly by Migrator for GroupWise’s Admin-Driven Batch Migrator, or manually by Microsoft’s Office 365 admin tools.

The AD Object Merge Tool is used for either or both of two purposes:

•
To mail-enable existing AD objects. Quest Migrator for NDS 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.

The AD Object Merge Tool is our tool of choice for mail enabling in the Pre-Migration Preparations (as described in the Migrator for GroupWise Scenarios Guide). The AD Object Merge Tool updates and mail-enables Active Directory accounts identified in a UsersToMerge.csv file specified during the program run. Since that data file is generated by the Migrator for GroupWise Directory Exporter, the AD Object Merge Tool cannot be run until after the Directory Exporter.

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 corresponding Contact exists, the program simply merges the SourceAddress from UsersToMerge.csv into the AD security object, to mail-enable the object.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen