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.
- If there is only one POA, you will only need to generate one user list and migrate all users from one MigrationWiz mailbox project.
Create a Trusted Application Key. This is used to migrate from GroupWise, using adminstrative credentials. 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".
- Source = earlier version than GroupWise 8 SP1
- Use our command line tool to generate the Trusted Application Key.
Prepare the Destination Environment
Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. KB004948
Set up accounts on Office 365 and assign licenses. These can be created in several ways:
- Prepare the tenant to send and receive large mail items. KB005139
- Contact Microsoft to ask to have the tenant EWS throttling limits raised for 60 days. Note: This step is only required if your Source environment will support migration speeds that are faster than the Destination. KB005493
- Create the customer. KB005421
- Create the Source and Destination endpoints. KB005427
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Office 365 > fill in the required fields.
Purchase licenses. From your MSPComplete dashboard, click on Purchase > Mailbox Migration > select MigrationWiz-Mailbox and enter the number of licenses you wish to purchase. Note: Check to see if there are any available bundles for discounts (e.g., MigrationWiz-Mailbox and DeploymentPro Bundle). KB004647
Deploy DMA to users. Once DMA has been deployed to users, check the Users tab in MSPComplete. This will be populated with the user accounts that have DMA installed. DMA can be deployed by either of these options:
- 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.
- For the Destination endpoint:
- 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.
- 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.
Go to All Products > DeploymentPro and follow the prompts to launch.
Select a customer from the list by clicking on the customer name. Note: The status column will show enabled when a customer account has had DMA deployed.
Configure customer DeploymentPro module:
Activate the DeploymentPro module for users.
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: DeploymentPro requires licenses to be purchased before it can be used. Subscriptions include DeploymentPro. However, if you are not using subscriptions, and you are using mailbox licenses, you must purchase additional DeploymentPro licenses in order to use DeploymentPro.
Click on the Run Module button.
Schedule the profile cutover date.
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.
On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.
HealthCheck for Office 365 Steps
- Go all All Products > HealthCheck for Office 365 and follow the prompts to launch.
- Select a customer from the list by clicking on the customer name. Note: The status column will show enabled when a customer account has had DMA deployed.
- Review results. Note: If any computers have a red X on their row, you should review the detailed results by clicking on the pie chart in the far right-hand part of the row.
- Include upgrading action items and costs in your Statement of Work.
- Perform remediation steps.
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.
Add the accounts (also referred to as "items") that will be migrated to the project. KB004842 Note: GroupWise migrations require both the email address AND the username, e.g., email address = firstname.lastname@example.org AND username = testuser001.
Set the Project Advanced Options. KB004834
- Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
- Set to use impersonation at Destination. Checkmark the Use impersonation at Destination box. KB004727
- Set Maximum concurrent migrations. We recommend setting this to a very low value, such as 10, to ensure that server utilization does not go below 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
Run Verify Credentials. KB004511
Notify users that a migration is occurring. Send email to all users, telling them the time and date of the migration.
Pre-Stage pass: Select the users > Click on the Start button from the top, and select Pre-Stage Migration > Under the Migration Scheduling section, from the drop-down list, select 90 days ago > Click on Start Migration. KB004938
MX Record Cutover. Change over MX records on the DNS provider's portal. Also include the AutoDiscover (CName) setting.
Send email to end users to let them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to KB005799 for some sample text and screen shots that can be included in this email.
Full (Delta) pass: Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938
Run Retry Errors. KB004658
Look through the user list and click on any red "failed migration" errors. Review information and act accordingly.
If problems persist, contact Support. KB004529
If not using DeploymentPro, users must create new Outlook profiles, and set up their signatures again, and reattach any PST files that were attached to their previous profile.
Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626
- The following options are the most valuable for this migration scenario: