GroupWise Migration FAQs

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

From GroupWise 6.5 or earlier:

  1. Enable IMAP endpoint on the POA (just above the Enable SOAP checkbox) of your GroupWise system.
  2. Specify IMAP as the Source type when creating your MigrationWiz mailbox migration project, NOT GroupWise.
  3. Specify the IMAP host name 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. Should you require an IP lockdown, click here.
  5. To migrate using GroupWise administrative credentials, specify the Trusted Application Key on your connector. With the Trusted Application Key, you are able to 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 to NOT migrate emails (make sure only contacts, appointments and tasks are enabled in the object type filter)

If you want to use this approach, you simply need to move the mailboxes between Projects to submit without having to “burn” 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:

move_item.png

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

​GroupWise resource mailboxes cannot be logged in to, using regular user/password credentials. To migrate resource mailboxes, you must therefore use a trusted application key, which allows a single account to log in to all GroupWise mailboxes.​

There are more complex scenarios where a GroupWise shared or resource mailbox has no user name associated with it, 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 an application name and a key. By registering a Trusted Application whose name is "MigrationWiz", you will obtain a key which can be used by MigrationWiz to authenticate to multiple user mailboxes. Specify this key on your MigrationWiz connector.

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".

To register a Trusted Application called "MigrationWiz" using our command line tool, click ​here.

To register a Trusted Application called "MigrationWiz" using a graphical interface (GroupWise 8 SP1 or later):

  1. Follow Novell's instructions.
  2. Ensure that the application name is set to "MigrationWiz."
  3. Copy the key value for the application key textbox when configuring the Mailbox Connector for GroupWise.

Finally, for users migrating from GroupWise using IMAP, you can specify a Trusted Application key by specifying TrustedApplicationKey=<your key> in the Support Only options on your connector or mailbox Advanced Options as shown below:

trustedapplicationkey.png

When adding the users in an IMAP project using the TrustedApplicationKey​, the UI will still ask you to enter a password for each user. You can enter anything you like in the password field, and it will be ignored. Make sure you do not checkmark the option I don't know the password for this item, because this will send an email to the end user to enter their password.

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.

screenshot

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:

screenshot

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 a NCSP function" message is harmless. It actually means that the SOAP​​ endpoint is responding.

Workaround:

Configure your project to not 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 host name 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 doesn’t work on 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 the NETWIN32.DLL, which is packed by Novel Netware client. If you get the following error: “The program can’t start because NETWIN32.DLL is missing from your computer. Try reinstalling the program to fix this problem” 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

When the mail system is running on GroupWise, subfolders under the root "Mailbox" folder can be in a folder named "Cabinet".

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 in 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 in order for the folder mapping to be added.
  3. Click on Save Options.
  4. Click on Save Project.

On GroupWise, the Inbox is actually 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).

Was this article helpful?
0 out of 0 found this helpful