Chat now with support
Chat with 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

Specify Users for Update

Enter the requested information 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 filename into the text box. The Directory Exporter automatically generates a UsersTo­Merge.csv file that you may use for this purpose.
Target Exchange system: Specify your migration destination environment from the drop-down list. (Office 365 without Federation is not an option in this list because the merge function is invalid for that scenario.)
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.

Specify AD Information

Specify the Active Directory information and provide the administrator credentials and other information Exchange will need to perform the selected administrative functions, and click Next.

Global Catalog: Type the name of the AD Global Catalog server—for example,
Domain Controller: Specify the PowerShell Domain Controller that the program will call to perform operations in Exchange.
Client access server (appears on the screen only if migrating to Exchange 2013 or 2010): The name of the target Exchange client access server.
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:
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 from the Quest Migrator for NDS database: The output data file created by the Migrator for NDS (a separate Quest product). For this option, you must also specify this SQL server information:
Server: The name of the SQL server.
Authenticate by: Method of authentication to the SQL server. Choose 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 text boxes below.
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.)

Specify Provisioning Information

This screen appears only if you told the program 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 Provisioning Information screen and click Next.

Enable users: This checkbox determines whether you want the program to logon-enable the users this program will provision.
Users container: Use the Browse button to find and specify the relative domain name for an existing organizational unit (for example, cn=users) where any new user objects will be created in AD—when the AD Object Merge tool encounters a Contact for which there is no existing corresponding AD user account.

Specify Run Information

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 the run name is unique by scanning the log file directory for other run names.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating