This part of the documentation explains how to integrate Mailbox Shuttle with Archive Shuttle to migrate live email followed by archived email, from any of the sources supported by Archive Shuttle.
The following areas are covered:
Setting Up Integration
Configuring Mailbox Shuttle to work with Archive Shuttle involves several steps which are described here.
If you have purchased the option to migrate your legacy email archives along with live mailboxes you will have received an email which contains an additional user account. This account is called the integration account, and is required along with the name of the Core Server to connect to.
If you do not have the integration and Core Server URL you will not be able to complete subsequent steps and integration will not be available.
Enter additional credentials
The two systems need to communicate to each using a special account which has to be specified in the Credentials Editor. This is similar to the way communication works to Office 365. To configure the additional account perform the following steps:
- Login to the server running the modules as the service account that was used for the installation of the modules
- Locate the Mailbox Shuttle Credentials Editor on the start menu and launch it
- Click on the PowerShell tab
- Click Add
- Type in the name for Archive Shuttle end point, it will be similar to https://givenname.archiveshuttle.com
- Type in the full name for the account (which normally ends in ‘quadrotech-it.com’) *1
- Type in the password for this account, and click ‘ok’.
- Click ‘Save’ and close the Credentials Editor.
- Go into services and restart the “Mailbox Shuttle (AS Module)”
*1 This account is called the Integration Account. If this is Mailbox Shuttle and Archive Shuttle in the cloud, ask the Customer Experience Team to create an account. If this is an on premises installation then the service account can be used, but the credentials must still be input into the PowerShell tab of the Credentials Editor.
Enter connectivity information
To enter the connection information navigate to Configuration -> Integration in the user interface.
On this screen you should add the Core Server Name, and ensure the Source Type is selected appropriately. When enter correctly, click on Save to commit your changes. The Core Server name will similar to this:
Building a Workflow
The final step to perform on this screen is to build a workflow which will be used to migrate the archived data to your mailboxes (or secondary mailboxes). Building a workflow is described here.
Managing Archive Migration
In the user interface the Stage 3: Integration page can be used to monitor the progress of mappings through Stage 3, which is the legacy archive migration part of the migration. This page shows useful information about the migration, and allows for some actions to be performed. They are described below:
The stage 1 page in the user interface shows synchronization progress for groups and for mappings. It shows information about them, and allows actions to be performed on them, as described below:
|Group Name||The name of the group|
|The primary SMTP address of the mailbox / user|
|WF Step Status||The status of the step that the mapping is currently on|
|WF Step Name||The name of the step.|
|Message||Any informational messages about the mapping will be displayed here|
|WF Scripts Execution||An indicator to show whether a workflow script is going to be executed. A green dot indicates that it will be executed, a red dot shows it won’t be executed.|
|Retry||This button allows you to queue a command to retry the migration|
|Refresh / Columns / Reset||These buttons are used to refresh the grid containing the list of mappings, select any additional data columns which might be available, or to reset the grid back to the default display.|
Integration Status Report
This page in the user interface shows the progress of the legacy archive migration. It contains key information relating to item level counts from the source legacy-archive, and the target environment.