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.
The CSV data files generated by Migrator for GroupWise’s 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 particularly 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 a local 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 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 UsersToMerge.csv (or UsersToMigrate.csv). Then use the resulting file 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 Active Directory security objects, save the CSV file and use it as the template for creating lists of users for the merge and migration process.
Microsoft's Online Services DirSync tool can provision Office 365 with object data from a local AD server. To provision Office 365 with Microsoft’s DirSync, the existing NDS users and groups must already be provisioned as security principals in the local Active Directory.
Quest CMG or Migrator for NDS (separate Quest products, not part of Migrator for GroupWise) can automate object and group provisioning into the local AD. Quest CMG Directory Connector or Migrator for NDS offers the most complete capabilities for provisioning a local AD, but other methods are possible.
NOTE: If you already have existing mail-enabled objects in a local Active Directory but plan to use CMG’s Directory Connector to populate the local AD from GroupWise, enable the Directory Connector’s Migrator for GroupWise Compatability Mode to avoid duplicate entries in AD. The CMG Mail Connector and Free/Busy Connector can be configured similar to other scenarios. See the CMG User Guide for much more information.
In the next step below 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.
For Microsoft’s DirSync or Migrator for GroupWise to create Office 365 mailboxes (in the below), the objects in the local Active Directory must be mail-enabled. If you are implementing full coexistence, there may now be two objects in Active Directory for each GroupWise user: the security principal, and the routing contact synchronized in the preceding step of this procedure. In that case, run Migrator for GroupWise’s AD Object Merge Tool to merge the objects into a single mail- enabled user object in the local Active Directory prior to the migration.
If contacts have not been added to the local AD in support of coexistence, the AD Object Merge Tool can still be used to mail-enable existing security principals. In this case, addresses and attributes are pulled from Migrator for GroupWise’s CSV files to mail-enable objects rather than pulling information from contacts within AD.
NOTE: Remember the difference between mail-enabling and mailbox-enabling. A mail-enabled Active Directory object is one with a mail-address attribute for an address outside the Exchange domain, so AD can forward the object’s mail to the other address. A mailbox-enabled AD object is one that has an Exchange mailbox. A mail-enabled AD object that has no Exchange mailbox cannot receive mail in Exchange; it can only forward mail to an object’s external forwarding address.
The AD Object Merge Tool applies its functions to AD accounts listed in a CSV file specified during the program run. You can run the AD Object Merge Tool for the entire UsersToMerge.csv file (generated by the Directory Exporter and updated in earlier steps) to perform these functions for all users at once. Or you could use the UsersToMerge.csv file as a template to create subset lists of users. Keep the header row and any rows corresponding to users you want to include in the merge. Then save the file to a new name, still in CSV format.
The result of the merge process (under any of the above scenarios) is a single, mail-enabled user object corresponding to each object copied from GroupWise. Any existing AD security credentials and routing are preserved. For more details, see the AD Object Merge Tool chapter of the Migrator for GroupWise Administration Guide.