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


Review the Welcome screen and click Next.

GroupWise System Information

Enter the requested GroupWise System Information and click Next.

Admin user ID: The name of the admin’s GroupWise account (not the Novell account).
Admin password: The password for the admin’s GroupWise account (not the Novell account).
GWIA TCP/IP hostname: The hostname of the GroupWise Internet Agent LDAP server. This value must be a resolvable name or IP address for the GroupWise server, to which the Migrator for GroupWise admin workstation can talk.
GWIA LDAP context (disabled if no value is entered for GWIA TCP/IP hostname above): This is the context within which the user account will search for objects to export. For example, if you want to include users in the context named Marketing, but not users in the context Sales, then set this value to O=Marketing instead of [Top]. If necessary you can find this path in the ConsoleOne or NWADmin NetWare admin program: In the ConsoleOne navigation tree, select the name of the server, and then double-click GWIA in the adjacent window to open a Properties of GWIA dialog box for the selected server. On the LDAP tab, the LDAP context shown there is the value to use for this field — for example: O=Acme,C=US.
Domain path: The file system path to your GroupWise domain file wpdomain.db, as specified during the GroupWise installation in the form \\SERVER\SHARE\.
GroupWise SOAP Server URL (optional): Location of the GroupWise SOAP web service. This field is optional, but will help resolve a duplicate-meetings issue that can occur in some scenarios in some environments where Quest CMG coexistence product is also deployed. When a GroupWise user creates a meeting in GroupWise, and then changes it (or changes one instance of a recurring series) after he/she is migrated, the invitees' calendars may show duplicate instances unless the SOAP service is enabled and its URL is specified here. This solution works only for GroupWise 8 and later (not for GroupWise 7).


The Status screen reports the progress while the export process is running, and the program automatically advances to the Finished screen when it is finished.


Note the location of the program’s exported data files and click Exit.

This Finished screen may also offer an Error Log Report button if the Directory Exporter encountered any errors during its run. If the Error Log Report button does appear, you should click it to view the program log and assess the severity of the errors. (They may be trivial, since the logging feature tends to be picky.) The Error Log Report button launches Quest Log Viewer utility (see The Log Viewer chapter) to help you interpret and resolve logged issues.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating