Chat now with support
Chat with Support

Welcome, ApexSQL customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

On Demand Migration for Email Current - User Guide

Introduction Preparing Migrations Test and Pilot Migrations Configuring and Running Migrations Post Migration Third Party Assessments and Certifications Glossary

Migrating Delegate Access Permissions

Migrating Delegate Access Permissions

ODME supports migration of delegate access permissions from Exchange server and Office 365.

To set up delegates migration:

  1. Click the Options tab.
  2. Open the Migrate Permissions portion of the screen.
  3. Select the Delegates option.

Matching information for source and target users is taken from the migration plan. During the migration of the delegate list for the mailbox, ODME checks for the presence of a delegate in the mailbox list of the plan. If the delegate is not in the list, it will not be migrated.

We recommend the following migration approach:

  • To migrate delegates, create one or several separate plans in which:
    • Only the Delegates option is selected. Items from the Select Items to Migrate partition are not selected.
    • A list of mailboxes contains all mailboxes that planned to be migrated by ODME and groups that can potentially participate as delegates in migrated mailboxes. These groups will not be migrated, they will be used only for the matching operation.

NOTE: The following statuses will be displayed for the groups:

  • Completed status when Use end-user credentials option is not selected.
  • Interrupted status when Use end-user credentials option is selected.
  • The statuses do not mean that something goes wrong.
  • You can run these plans as many times as necessary to synchronize the delegate permissions.

NOTE: After migration, the migration status of groups will show as Interrupted instead of Completed when end-user credentials are used for migration. No negative effects are found besides the status.

In case target delegate does not exist, delegate access permissions are migrated by ODME as is. If the target delegate exists, a maximal value of the source and target access permissions will be set .

In case a set of permissions was customized the following exceptions of this rule are applicable, see the tables below and the Known Limitations section for details:

Source Target (in case matched delegate does not exist in target)
Delegate access permission on source
Delegate access permission on target before migration Delegate access permission on target after migration
None N/A None
Reviewer N/A Reviewer
Author N/A Author
Editor N/A Editor
Customized set (except None, Reviewer, Author, Editor) N/A None

 

Source Target (in case matched delegate exist in target)
Delegate access permission on source
Delegate access permission on target before migration Delegate access permission on target after migration
None or customized set (except None, Reviewer, Author, Editor) None or customized set (except None, Reviewer, Author, Editor) None

Customized set (except None, Reviewer, Author, Editor)

Reviewer or

Author or

Editor

Reviewer or

Author or

Editor (value from target)

 

Reviewer or

Author or

Editor

Customized set (except None, Reviewer, Author, Editor) Reviewer or

Author or

Editor (value from source)

Reviewer or

Author or

Editor

Reviewer or

Author or

Editor

Maximal value of the source and target access permissions.

Possible values - Reviewer or

Author or

Editor

Migrating Folder Permissions

Migrating Folder Permissions

ODME supports migration of folder permissions from Exchange server and Office 365.

Note: Migration of folder permissions for Recoverable Items is not supported.

To set up migration of folder permissions:

  1. Click the Options tab.
  2. Open the Migrate Permissions portion of the screen.
  3. Select the Folder Permissions option.

Matching information for source and target users is taken from the current migration plan.

We recommend the following migration approach:

  • To migrate folder permissions, create one or several separate plans in which:
    • Only the Folder Permissions option is selected. Items from the Select Items to Migrate partition are not selected.
    • A list of mailboxes contains all mailboxes that planned to be migrated by ODME and groups that can potentially participate as grantees in migrated mailboxes folder permissions. These groups will not be migrated, they will be used only for the matching operation.

    NOTE: The following statuses will be displayed for the groups:

    • Completed status when Use end-user credentials option is not selected.
    • Interrupted status when Use end-user credentials option is selected.

    The statuses do not mean that something goes wrong.

    You can run these plans as many times as necessary to synchronize the folder permissions.

  • For the content migration, use migration plans as usual and do not check the Folder Permissions option in these plans.

In case the target permission does not exist, permissions are migrated by ODME as is. If the target permission exists, a maximal value of the source and target access permissions will be set .

Source Target (in case matched folder permission does not exist in target)
Folder permission on the source
Folder permission on the target before migration Folder permission on the target after migration
None N/A None
Owner N/A Owner
Publishing Editor N/A Publishing Editor
Editor N/A Editor
Publishing Author N/A Publishing Author
Author N/A Author
Nonediting Author N/A Nonediting Author
Reviewer N/A Reviewer
Contributor N/A Contributor
Custom N/A Custom

Migrating OWA Inbox Rules

Migrating OWA Inbox Rules

ODME supports migration of OWA (Outlook Web App) Inbox rules from Office 365, Exchange 2019, 2016, 2013, and 2010. The rules must be created and managed only in the OWA, rules managed by Outlook might not migrate correctly. See Known Limitations for other limitations about migrating OWA Inbox rules.

IMPORTANT: Use the OWA Inbox Rules option to migrate only OWA Inbox rules, i.e if you use OWA only.

If Outlook is used (with or without OWA) to create and managed rules – CPUU should be used with prior x500 address assignment to the recipients on the target side. For more details, see Updating Outlook Client Profiles. The option to migrate rules in the plan settings should be disabled.

To set up migration of OWA Inbox rules:

  1. Migrate other content (such as messages, contacts) except OWA Inbox rules: Use migration plans as usual and do not check the OWA Inbox Rules option in these plans.
  2. Create a separate plan in which,
    • Only the OWA Inbox Rules option is selected. Other items from the Select Items to Migrate partition are not selected.
    • A list of mailboxes contains all mailboxes that planned to be migrated by ODME and groups that can potentially participate in the rules to be migrated. These groups will not be migrated, they will be used only for the matching operation.

    NOTE: The following statuses will be displayed for the groups:

    • Completed status when Use end-user credentials option is not selected.
    • Interrupted status when Use end-user credentials option is selected.

    The statuses do not mean that something goes wrong.

Matching information for source and target users is taken from the migration plan. When the source email address is an Active Directory user or group, you must specify the email address with its primary domain name in the target, or rules may not work properly after migration. During the migration of the rules for the mailbox, ODME checks for the presence of a user or group in the mailbox list of the plan. If the user or group is not in the list, rules will not be migrated.

You can run the migration plan for rules as many times as necessary to synchronize the OWA Inbox rules, which will not change the OWA Inbox rules that already exist on the target. The existing OWA Inbox rules migrated by ODME on the target will skipped when you run the migration plan again.

Caution: If Outlook was connected to the target mailbox and client-side send rules were created there, ODME will delete them. Outlook cannot recreate such rules, so they will be lost.

Rules containing unsupported conditions, exceptions or actions will not be migrated, you will need to set them up manually on the target. The following table lists the conditions and exceptions supported by each platform:

Condition / Exception Office 365 Exchange 2019/2016 Exchange 2013 Exchange 2010
Message was received from the specified users or groups in GAL Yes Yes Yes Yes
Message was sent to the specified users or groups in GAL Yes Yes Yes Yes
Message was received through the specified account No N/A N/A N/A
Message contains the specified words in the subject

Yes

Yes

Yes

Yes

in the subject or body Yes Yes Yes Yes
in the sender's address Yes Yes Yes Yes
in the body

Yes

Yes

N/A

Yes

in the recipient's address Yes Yes N/A Yes
in the message header Yes Yes N/A Yes
My name is in the To or Cc box Yes Yes Yes Yes
the only recipient listed Yes Yes N/A Yes
in the To box Yes Yes N/A Yes
in the Cc box Yes Yes N/A Yes
not in the To box Yes Yes N/A Yes
Message is marked with an importance... Yes Yes N/A Yes
a sensitivity... Yes Yes N/A Yes
Message is accompanied by an attachment Yes Yes N/A Yes
of the type... Yes Yes N/A Yes
classified as... No No N/A No
flagged as... Yes Yes N/A Yes
Message size is within a specified range Yes Yes N/A Yes
Message was received within a specified date span Yes Yes N/A Yes

The following table lists the actions supported by each platform:

Action Office 365 Exchange 2019/2016 Exchange 2013 Exchange 2010
Move message to folder Yes Yes Yes Yes
Copy message to folder Yes Yes N/A Yes
Delete message* Yes Yes Yes Yes
Pin message No No N/A N/A
Mark message as read Yes Yes N/A Yes
as junk Yes Yes N/A N/A
with importance Yes Yes N/A Yes
with a category Yes Yes Yes Yes
Forward message to... Yes Yes N/A Yes
Forward message as an attachment to... Yes Yes N/A Yes
Redirect message to... Yes Yes Yes Yes
Send a text message to... Yes Yes Yes Yes
Stop processing more rules Yes Yes Yes Yes

* Rules with the action "Delete message" will have the option Stop processing more rules selected on the target after migration.

Setting Up Mail Forwarding

Setting Up Mail Forwarding

ODME supports automated mail forwarding on a per-user basis for these email services: G Suite, Office 365, GroupWise and Zimbra. After configuring your email service to interface with the ODME mail forwarding feature (as described in the section Setting Up Mail Routing), specify the required forwarding parameters in the Options tab.

To set up mail forwarding:

  1. Click the Options tab.
  2. Open the Forwarding (Optional) portion of the screen.
  3. Select the type of mail forwarding operation you want ODME to execute.

Options include:

  • Forward new items as they arrive — Mail is forwarded to a mailbox in a specified source or target email service and domain. When you select this option, you are prompted to select the source or target email service in the migration plan that you want to set forwarding on as well as the domain that mail is to be forwarded to.
  • Turn off existing forwarding — Existing mail forwarding settings are removed from a mailbox in a specified source or target email service and domain.

These options are enabled only if mail forwarding is supported for the source or target email service in the migration plan. If mail forwarding is supported for only one email service in the migration plan (source or target), then you can only select one of the two options.

If mail forwarding is supported for both the source and target, then both options are enabled. In this case, when you select one option, the other option is automatically selected as well. This is designed to prevent messages from looping perpetually between two mailboxes in the event that mail forwarding is inadvertently set on both the source and the target email service. However, if you want to set or remove mail forwarding on only one of the two email services in the migration plan, you can de-select one of the automatically selected options.

  1. If you selected the Forward new items as they arrive option, do the following:
    1. In the Set forwarding address on: field, select the source or target email service that you want to set forwarding on.

The source email service specified in the migration plan is selected by default. Select the target email service if you want to set forwarding on that instead.

When G Suite or GroupWise is selected as the source email service, these Forwarding Actions are available for you to decide what you want ODME to do when new mail items arrive:

  • KEEP: When new mail items arrive, new item is delivered to source mailbox and kept in the Inbox as well as forwarded to target mailbox.
  • DELETE:
    • For G Suite: When new mail items arrive, new item is delivered to source mailbox and moved to the Trash folder as well as forwarded to target mailbox.
    • For GroupWise: When new mail items arrive, new item is delivered to source mailbox and deleted from Inbox as well as forwarded to target mailbox.

  • MARK AS READ: When new mail items arrive, new item is delivered to source mailbox and marked as read in the Inbox as well as forwarded to target mailbox.
  • ARCHIVE (for G Suite only): When new mail items arrive, new item is delivered to source mailbox and archived (not visible in the Inbox) as well as forwarded to target mailbox.

 

Note: If mail forwarding is supported for both the source and target email services, when you set mail forwarding on one service (source or target), the option to turn off existing forwarding defaults to the other service automatically.

  1. In the Forward to: field, enter the domain that mail is to be forwarded to.

Improperly formatted domain names result in an error message.

The domain name part of the forwarding email address (<local_part>@<domain>) is specified by the domain you enter in the Forward to field. The local part depends on which email service you selected in step a: When the source email service is selected, the local part of the target email address will be used; And when the target email service is selected, the local part of the source email service will be applied.

  1. For G Suite only, enter the name and password of the administrator account used for mail forwarding.
  1. Click Test.

This validates that the proper administrator credentials have been provided to perform mail forwarding. For Office 365, the administrator account must be assigned the “Recipient Management” role. See the section Setting Up Mail Routing for more information.

  1. If you selected the Turn off existing forwarding option, do the following:
    1. In the Remove forwarding address from: field, select the source or target email service that you want to remove existing forwarding settings from.

Note: If mail forwarding is supported for both the source and target email service and you already set mail forwarding on one email service, this field defaults to the other service.

  1. In the Forwarding to: field, enter the domain to which mail is currently forwarded.

Improperly formatted domain names result in an error message.

  1. For G Suite only, enter the name and password of the administrator account used for the mail forwarding settings you want to remove.
  1. Click Test.

This validates that the proper administrator credentials have been provided to perform mail forwarding. For Office 365, the administrator account must be assigned the “Recipient Management” role. See the section Setting Up Mail Routing for more information.

Related Documents