The Manage Mappings area of the Admin Interface contains multiple views of the containers involved in the archive migration.
The three views provided are:

  • Bulk Mapping
  • Manual Mapping
  • Existing Mappings

The different views are described in the following sections.

Mapping Templates

Using the Mapping Templates feature, you can create a container mapping template where you can set the total mailbox item count limit or item size limit. Then, when creating a mapping, you can assign a template and override settings for the O365 Module in SysConfig.
Note: Currently the Mapping Templates feature is available for Virtual Journal only.

Creating a Mapping Template

Create a mapping template before creating a mapping by following these steps:

  1. Select Configuration > Templates > Mapping Templates from the left menu bar.
  2. Click Add.
  3. Enter a name/description and desired limits using the Mapping Template Configuration window (shown below).
  4. Save the template.

Or, if you don’t create a mapping template in advance, you can create one using the Create new Template link available on the Add Mappings Wizard (shown below).

Assigning a Mapping Template

For new mappings, the Add Mappings Wizard prompts you to choose the mapping template you want to assign (see image above).
If you don’t assign a template (or an empty one is assigned) during mapping and item collection/migration is enabled, you’ll see this warning message (in red) within the wizard:

If you opt to not choose a mapping template, the default settings configured in SysConfig – O365 Module are applied.
If you haven’t enabled item collection/migration for the mapping, you can change or assign a mapping template on Existing Mapping page using the Set Template button shown below.

Bulk Mappings

This page is used to map containers to either new or to existing containers based on certain criteria.
The following basic information about each container is visible in the grid view:

  • Name
  • Indicator field to show whether the container has an owner or not
  • Owner Full Name
  • Group
  • Type of container (e.g., Enterprise Vault)
  • Archive Type
  • Indicator field to show whether the container has a mailbox or not
  • Link Name
  • EV Archive Status
  • Item Count
  • Total Size
  • Indicator field to show whether the container is mapped or not

If a Container’s owner / user could not be determined in Active Directory, it is considered “ownerless”, and is marked as such in the Name column. Example: John Doe (Ownerless)

Actions to be performed on the Bulk Container Mapping page

  • Add Mappings

Add mappings for selected containers. A pop-up wizard allows the mapping to be defined. The information that is required depends on the target:

  • Enterprise Vault

The target user strategy must then be chosen as follows:

    • Same User
  • Different User

Choose this option if the migration is to take place to another domain. The target domain can be chosen from a drop-down list, and matching criteria must be specified (e.g., Legacy Exchange DN, SID History, User Name)

The container strategy must then be chosen as follows:

  • Create new containers

Choose this option if Archive Shuttle should create new containers in the target environment.

  • Using existing containers

Choose this option if Archive Shuttle should use existing containers in the target environment.

  • Create new if there is no existing

Choose this option if Archive Shuttle should primarily use existing containers in the target environment, and if they do not exist, they will be created.

The target link must then be selected.

  • Choose the Link where you want to migrate to:

Select an entry from the drop down list that will correspond to a link in the target environment.

  • Exchange

The mailbox type must then be chosen as follows:

  • Primary mailbox: Choose this option if Archive Shuttle should ingest the data in to the users primary mailbox.
  • Secondary (Archive) Mailbox: Choose this option if Archive Shuttle should ingest the data in to the users secondary (archive) mailbox. If this option is selected, then an option of what action should be taken if a secondary mailbox does not exist can be specified. The choice of options are to either skip the ingestion or ingest into the primary mailbox instead.
  • Office 365

The mailbox type must then be chosen as follows:

  • Primary mailbox: Choose this option if Archive Shuttle should ingest the data in to the users primary mailbox.
  • Secondary (Archive) Mailbox: Choose this option if Archive Shuttle should ingest the data in to the users secondary (archive) mailbox. If this option is selected then an option of what action should be taken if a secondary mailbox does not exist can be specified. The choice of options are to either skip the ingestion or ingest into the primary mailbox instead.

The target link must then be selected.

  • Choose the Link where you want to migrate to:

Select an entry from the drop down list that will correspond to a link in the target environment.

  • PST

The format must then be chosen as follows:

  • PST: The output format will be PST

The target link must then be selected.

  • Choose the Link where you want to migrate to:

Select an entry from the drop down list that will correspond to a link in the target environment.

Later in adding this type of mapping, it is required to choose a PST File name policy. This is selected from a drop down list.

The remaining elements in the pop-up wizard are then the same regardless of the target for the migration:

  • Workflow Policy: The workflow policy must then be chosen, the list of workflows that are available will be determined by the chosen target. For example, if the migration is to Enterprise Vault, only those workflows applicable to an Enterprise Vault migration will be shown. Additional workflow policies can be defined. This is described in the section Workflow Policies.
  • Filter Policy: The filter policy must then be chosen from the drop-down list. The will be a default filter which performs no filtering. Additional filter policies can be defined. This is described in the section Filter Policies.
  • Choose Container Mapping Settings: Properties for the new mapping can then be set.
  • Migration Status: Enabled: Enable immediate migration for the newly added mappings.
  • Migration Status: Disabled. Does not immediately start migration for the newly added mappings.
  • Item Gathering Status: Enabled. Enables item gathering for the newly added mappings.
  • Item Gathering Status: Disabled: Does not start item gathering for the newly added mappings. There will be a summary page displayed at the end of the wizard when creating a new container mapping. This contains all of the information gathered during the wizard and should be reviewed before committing the changes.
  • Run Item Gathering: Start Full or Delta item collection for selected containers. The source container will be examined and data relating to each item will be collected and added to the appropriate Archive Shuttle Link database.

Note: This would normally be set when configuring the container mapping and is provided in the navigation bar as a means of forcing the update and for troubleshooting.

  • Run Shortcut Gathering: Start Full shortcut collection for selected containers.
  • Add to Group: One or more containers can be added to an existing or new group. This group membership can then be used for filtering and batching of users for migration.
  • Assign Archive User: A different owner can be associated with a particular container.
  • Refresh: Refresh the data in the grid view.
  • Columns: Add additional columns to the table. Drag and drop a column name to the header column of the grid view.
  • Reset: Resets the source and target container tables back to the default list of columns, and removes any currently defined filters.
  • Export to PDF, XLS, XLSX, CSV: Allow data to be exported to several formats

On the Bulk Mapping screen, it is also possible to view details of a particular container/user. To do this, select the small magnifying glass next to the user and a pop-up window will be launched showing the User Information page for that container.
When performing a bulk mapping it is possible to postpone and schedule the collection of items, and the migration. This is a step in the mapping wizard.

Manual Mappings

Allows an administrator to create mappings for single containers. The source as well as target container must already exist. Performing a mapping operation in this manner is useful for containers such as Enterprise Vault Journal Archives, or where containers need to be merged to a target container.
The following basic information about each container is visible in the grid view:

  • Name
  • Owner Full Name
  • Group
  • Type
  • Mailbox Type
  • Link Name
  • Content Count
  • Content Size
  • Link name
  • Mapping Counts for the source and target

Actions to be performed on the Manual Mapping page

  • Add Mapping: Adds a mapping for the selected containers. A source and target container must have been selected before this navigation bar item is available.
  • Add to Group: One or more containers can be added to an existing or new group. This group membership can then be used for filtering and batching of users for migration.
  • Refresh: Refreshes source and target container tables.
  • Reset: Resets the source and target container tables back to the default list of columns, and removes any currently defined filters.

Existing Mappings

Containers that have already been mapped are listed on the Existing Mappings page. This page gives the ability to Enable/Disable mappings for migration and perform other container mapping related actions.
Note: Additional columns are available if the ‘Advanced view’ is enabled (under the ‘Views’ tab) though this makes the user interface slower if there are a large number of mappings.
The table shows the following information for each existing container mapping:

  • Container Mapping ID
  • Source Container Type
  • Source Container User
  • Source Group
  • Source Container Link Name
  • Flag to indicate if the container has an owner
  • Flag to indicate if the container has a mailbox
  • Target Container Type
  • Target Container User
  • Target Group
  • Target Container Link Name
  • Workflow Policy
  • Filter Policy
  • Priority
  • Item Gathering Enabled: Indicates whether the container mapping is enabled for item gathering (container level).
  • Enabled for Migration: Indicates whether the container mapping is enabled for migration. Archive Shuttledoes NOT start to export / import when a container mapping is disabled for migration.
  • Stage 2: Indicates whether the container mapping has been switched to the target. If it has, Stage 2 of the Workflow has been started.
  • Stage 2 Finished: Indicates whether Stage 2 has finished for this mapping

Actions to be performed on the Existing Container Mappings page

These actions can be performed on this page:

  • Set Priority: Adjust the priority for the selected container mapping(s)
  • Enable Stage 2: Switch the selected container(s) to the target
  • Enable for Migration
  • Disable for Migration
  • Enable Item Gathering
  • Disable Item Gathering
  • Delete Mapping
  • Run Item Gathering
  • Run Shortcut Gathering
  • Set Workflow Policy
  • Set Filter Policy
  • Set Failed Item Threshold
  • Add to Group: One or more containers can be added to an existing or new group. This group membership can then be used for filtering and batching of users for migration.
  • View Mappings Health: Switches to a status page which can be used to check mappings.  See the section in this document called ‘Mappings Health’ for more information.
  • Comment: Set a comment of up to 256 characters on one or multiple mappings.
  • Refresh
  • Columns
  • Reset
  • Set Rollover Threshold: Specify the size in MB, or number of items that PST files should be rolled over.
  • Disable Offline Mode
  • Enable Offline Mode
Print Friendly, PDF & Email