The following guide covers general information for GroupWise migrations utilizing MigrationWiz. This information includes setting up the source, SOAP questions, and specific steps needed for certain hosts.

GroupWise Source Preparations

1. Enable the IMAP endpoint on the POA of your GroupWise system, located just above the SOAP checkbox.
2. Specify IMAP as the Source type when creating your MigrationWiz mailbox migration project, NOT GroupWise.
3. Specify the IMAP hostname and port number. Typically port 143 without SSL/TLS and 993 with SSL/TLS.
4. To migrate using GroupWise administrative credentials, we support Trusted Application key authentication for IMAP.

From GroupWise 7+:

1. Enable the SOAP endpoint on the POA of your GroupWise system.
2. Specify GroupWise 7+ as the Source type when creating your MigrationWiz mailbox migration project.
3. Specify the GroupWise SOAP URL on your project. Instructions are below.
4. Open port 7191 in your firewall. If you require an IP lockdown, click here.
   

   Important

   IP LockDown does not work with BitTitan Autodiscover using MigrationWiz. To add Users to the project, use Bulk Add via a CSV file or add them manually.
5. To migrate using GroupWise administrative credentials, specify the Trusted Application Key on your connector. With the Trusted Application Key, you can migrate resource mailboxes.

Some deployments of GroupWise (e.g., GroupWise on NetWare due to bugs in its code) crash when accessed over SOAP. If so, you will need to create two connectors:

1. One for IMAP ​-> only emails will be migrated (migrating only emails over IMAP means fewer or no crashes)
2. One for SOAP -> configured NOT to migrate emails (make sure only contacts, appointments, and tasks are enabled in the object type filter)

If you want to use this approach, you only need to move the mailboxes between Projects to submit avoiding “burning” another license (using a Full/Delta pass instead).  Click on the Move icon and follow the instructions to move the mailbox to a different Project:

​

Moving mailboxes from one connector to another is safe; all statistics as well as the ability to resubmit using mailbox migration licenses, are preserved.

GroupWise Resource Mailboxes

There are more complex scenarios where a GroupWise shared or resource mailbox has no user name associated, and it can only be logged in to using GroupWise "proxy access". In this case, we won't be able to authenticate and log in to that mailbox, and consequently, we will be unable to migrate it.

Migrating from GroupWise using administrative credentials

To migrate from GroupWise using administrative credentials, you must use a GroupWise feature called Trusted Application.

A Trusted Application is identified by its name and key. By registering a Trusted Application named "MigrationWiz" you obtain a key. MigrationWiz uses this key to authenticate to multiple user mailboxes. Specify this key on your MigrationWiz connector.

GroupWise URLs

The GroupWise URL you specify as your project endpoint should be that of the SOAP endpoint.

Specify in the following format:

• <http or https>://<host name>:7191/soap
• <http or https>://<IP address>:7191/soap

Port 7191 is the default port for the SOAP endpoint on GroupWise.

Enable & Verify SOAP Endpoint

MigrationWiz uses GroupWise's SOAP API to migrate content. To enable the SOAP endpoint, start ConsoleOne and navigate to GroupWise Agent Settings. Checkmark the Enable SOAP​ option to enable SOAP access as shown below. The SOAP endpoint will be accessible from the current URL by default: https://server:7191/soap.

To check if the SOAP endpoint is accessible, browse to the corresponding URL (for example, http://host:7191/soap or https://host:7191/soap) using Internet Explorer, preferably outside your intranet. If the SOAP endpoint is accessible, you should see a message like this:

GroupWise NetWare Migrations

Some deployments of GroupWise crash when accessed over SOAP. Specifically, there are a lot of problems with GroupWise on NetWare, due to bugs in Novell code. Only a very small percentage of GroupWise deployments run on NetWare. 

When examining the responses to SOAP requests on Netware, the POAs crash and we get:

• HTTP/1.0 500 Internal Server Error
• Date: Fri, 17 Aug 2012 21:28:09 GMT
• Server: NetWare GroupWise POA 7.0.4
• Content-Type: text/html
• Pragma: no-cache

The "Bad parameter passed to an NCSP function" message is harmless. It means that the SOAP​​ endpoint is responding.

Workaround

Configure your project not to migrate email (make sure only contacts, calendars, and tasks are enabled), and submit for migration.

If successful

1. Enable IMAP access under your GroupWise Agent Settings (as demonstrated in the screenshot under Enable & Verify SOAP Endpoint. This is similar to enabling SOAP access but for IMAP.
2. Create another mailbox migration project to migrate only email via IMAP.
   • Specify IMAP as a Source system type.
   • Specify your hostname and port number. Typically port 143 without SSL/TLS and 993 with SSL/TLS.
   • We support Trusted Application key authentication both for SOAP and IMAP.
3. Add the same mailboxes to this new IMAP project. Contact your BitTitan Sales Manager so that they can grant you licenses to cover this 'extra' migration.
4. Uncheck contacts, calendars, and tasks. Make sure only email is enabled.
5. Submit the mailboxes for email migration.

Registering a GroupWise Trusted Application

Only GroupWise 8 Support Pack 1 or later offers a convenient graphical user interface tool for you to register trusted applications. For previous versions, we provide a command line tool. In all cases, the trusted application should have its name set to "MigrationWiz." The command line tool is attached at the end of this article. 

Using the command line tool

1. Go to the target GroupWise server.
2. Log in as a GroupWise administrator.
3. Verify the user has full access to the GroupWise domain folder.
4. Extract zipped files to a local temporary folder.
5. Run the EXE with the GroupWise database folder as an argument (ie., GenerateTrustedAppMigrationWizKey.exe C:\Novell\Databases).

Example

• C:\>GenerateTrustedAppMigrationWizKey.exe C:\Novell\Databases
• MigrationWiz Trusted App Key Generator
• Configuring: C:\Novell\Databases
• Key Generated
• Key: 865A15420BA50008B…007BCF0085003000​

If this does not work in your environment

1. Go to a Windows machine.
2. Log in as a GroupWise administrator.
3. Mount a drive letter to the remote target GroupWise server (for example, net use X: \\GW-Server\c$ /u:Administrator).
4. Follow the previously outlined steps using X:\Novell\Databases instead.

The command line tool requires NETWIN32.DLL, packed by the Novell Netware client. If you get the following error:

To resolve this issue, confirm that:

• The GroupWise client is installed on the computer.
• The Novell Netware client is installed on the computer.

Add Folder Mapping for GroupWise Cabinet Folder

Subfolders under the "Mailbox" root folder can be in a "Cabinet" folder when using the GroupWise mail system.

If no folder mapping is added to your MigrationWiz project, then all folders, once migrated, will also appear under a folder named "Cabinet". This can be confusing for end users, who might be expecting these folders to appear under the root of their inbox.

If this is the case, a folder mapping should be added to your MigrationWiz Project Advanced Options.

Follow these steps:

1. From the MigrationWiz dashboard, click on the Edit Project button, and then from the drop-down list, select Advanced Options.
2. ​In the Support section, under Support Options, specify the following:
   1. FolderMapping=”^Cabinet->Inbox”
   2. ​Click on the "+" sign. You must click on the "+" sign for the folder mapping to be added.
3. Click on Save Options.
4. Click on Save Project.

On GroupWise, the Inbox is named "Mailbox". MigrationWiz contains a default folder mapping to automatically remap "Mailbox" over to the Inbox at the Destination (for those Destinations, such as Exchange and Office 365, that contain an Inbox).