GroupWise to On-Premises Exchange Migration Guide
- This is the complete onboarding task flow for migrating mailboxes from GroupWise (version 7.0 and later) to On-Premises Microsoft Exchange, versions 2007, 2010, 2013, or 2016.
- Complete each step in order. Links to corresponding Knowledge Base articles are provided.
- GroupWise can be running on Windows, Linux, and Novell NetWare. If you are running it on Novell NetWare, there are some extra steps required in order to migrate successfully. To learn more, read KB005093.
- The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. Deploying DMA to end users is a prerequisite if you will be using DeploymentPro.
Note: The steps in this guide for DMA and DeploymentPro are only neccessary if end users are using Microsoft Outlook as their email client.
- We recommend that you use DeploymentPro to reconfigure the Outlook profiles in this migration scenario if end users are using Microsoft Outlook as their email client.
Note: DeploymentPro requires licenses to be purchased before it can be used. Refer to Scenario 2 in KB004875 to read why it is recommended (but not mandatory).
Prepare the Source Environment
- Enable the SOAP endpoint on each Post Office Agent (POA). Start GroupWise ConsoleOne > navigate to GroupWise Agent Settings > checkmark the Enable SOAP option to enable SOAP access. KB004481
Note: If the Source environment has multiple POAs, it is necessary to open a SOAP port (typically 7191) on each POA.
- Generate the user list. This can be generated through your GroupWise ConsoleOne portal. Note: GroupWise migrations require both the email address AND the username, e.g., email address = testuser001@Sourcedomain.com AND username = testuser001.
- Single POA
- If there is only one POA, you will only need to generate one user list and migrate all users from one MigrationWiz mailbox project.
- Multiple POAs
- If there are multiple POAs and they are not linked:
- You will need to generate a user list for each POA.
- You will then use these lists to add the users to each MigrationWiz mailbox project.
- You will create multiple Source endpoints, one for each POA, and include the IP address of the POA as part of the GroupWise SOAP URL, under the MSPComplete section of this guide. It will follow this format: <http or https>://<IP address>:7191/soap
- If there are multiple POAs and they are linked:
- You will only need to generate one user list, which should include all users from all POAs.
- You will then use this list to add the users to a single MigrationWiz mailbox project.
- You will create only one Source endpoint and include the external IP address of the POA as part of the GroupWise SOAP URL, under the MSPComplete section of this guide. It will follow this format: <http or https>://<IP address>:7191/soap
Note: If GroupWise is installed on Novell NetWare, register a Trusted Application Key by following the directions here.
· Source = GroupWise 8 SP1 or later
- Use the GroupWise graphical interface to register a Trusted Application key called "MigrationWiz".
- Ensure that the application name is set to "MigrationWiz".
§ Make a note of the key value for the application key textbox. This will need to be entered under the Source endpoint in MSPComplete.
· Source = an earlier version than GroupWise 8 SP1
o Use our command line tool to generate the Trusted Application Key.
- To register a Trusted Application key called "MigrationWiz" using our command line tool, follow the directions in KB004445.
Prepare the Destination Environment
- Set up user accounts.
- Create an admin account for migration that has full access permissions to all mailboxes. KB004725
- Set up a remote PowerShell session with Exchange 2010+. KB005111
- To manually grant administrative access for migration, execute the following PowerShell command in the Exchange PowerShell Console:
Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User MigrationWiz
- In the PowerScript script above, change the -User account to match the name of the admin account that was set up for migration.
- Any user account that is a part of the domain administrator, schema administrator, or enterprise administrator groups will not have any administrative rights to mailboxes, no matter how many permissions are granted. A security default of Exchange Server is to explicitly deny any user that is a member of these groups. This is why we recommend creating a new user account specific for migration.
- Increase message size limits. KB004613
- For the Source endpoint:
Note: If there are multiple Post Office Agents (POAs), and they are not linked, create separate Source endpoints for each POA.
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select GroupWise 7+
- Enter the GroupWise SOAP URL. KB004482
- Click on the Provide Credentials radio button, and enter the Trusted Key for the Trusted Application Key that was set up under the Prepare The Source Environment section of this guide.
- For the Destination endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Exchange Server 2003+.
- Enter the OWA URL KB004392
- Click on the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the Prepare The Destination Environment of this guide.
Note: Check to see if there are any available bundles for discounts (e.g., MigrationWiz-Mailbox and DeploymentPro Bundle). KB004647
- Via Group Policy Object (GPO).
Note: This is the recommended methodology, because no end user interaction is required. KB005412 video
- Via email. KB005411
- Launch DeploymentPro.
- Go to All Products > DeploymentPro and follow the prompts to launch.
- Select a customer from list by clicking on the customer name.
Note: The status column will show enabled when a customer account has had DMA deployed.
- Configure the customer DeploymentPro module:
- Enter the Domain.
- Select the Destination endpoint.
- Checkmark the Auto-populate box.
- In the Client Interface Configurations section, upload your company logo and add supporting text.
Note: We strongly recommend doing this, because this is the logo and text that end users will see in a desktop pop-up when they are prompted to reconfigure their Outlook profiles. If you do not upload your own logo, the default BitTitan logo will be included instead.
- Save and continue.
- Either select all users (by checkmarking the box to the left of the Primary Email column heading), or select the individual users (by checkmarking the boxes to the left of the user email addresses).
Note: You will need to purchase DeploymentPro licenses for each user that will be using DeploymentPro. KB004647
- Click on the Schedule Cutover button.
- Set the date and time for the Outlook profile configuration to occur, and click on the Schedule Cutover button.
- The DeploymentPro module will install on user devices immediately, and then run silently until this date.
- The profile cutover date should be set to a date and time that is shortly after MX record cutover.
Watch this video to see a walk-through of the steps below.
- Create the Mailbox Migration project. KB004380
Note: If there are multiple Post Office Agents (POAs) that are not linked, you will create multiple Mailbox Migration Projects and match the Source endpoint to the project that corresponds to the users on the POA.
- Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
Note: GroupWise migrations require both the email address AND the username, e.g., email address = firstname.lastname@example.org AND username = testuser001.
- The following options are most valuable for this migration scenario:
- Set Maximum concurrent migrations. We recommend setting this to a very low value, such as 10, to ensure that server utilization does not go above 80%. If the Source server has enough server resources, set this parameter based on the bandwidth guideline of three (3) mailboxes per 1Mbps of bandwidth. Therefore, for example, if there is a 10Mbps connection, we recommend setting the maximum concurrent migrations parameter to be 30. If the Source server has very few available server resources (e.g., it is running low on memory or it has very high CPU utilization), we recommend setting this value to a lower number to avoid overwhelming the Source server with requests.
- Add folder mapping: FolderMapping=”^Cabinet->Inbox” under Support/Support options.
Note: This will map folders under the cabinet subfolder on GroupWise, to the Inbox on the Destination. KB005793