Chat now with support
Chat with Support

On Demand Migration Current - Administrator Guide

About On Demand Migration Before You Start Working with On Demand Migration Starting Migration Project Configuring Connections Sharing Availability Information Collecting Account Information Pre-Migration Assessment Account Migration Hybrid Account Migration Domain Coexistence Mail Migration OneDrive Migration Resource Processing Public Folders Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

Mail Migration

Basic mailbox migration workflow consists of the following steps:

# Step
1 Deploying Client Update Agent
2 Migrating Mailboxes
3 Configure mail forwarding from target to source
4 Configure notifications for mailbox owners
5 Switch mailboxes

Deploying Client Update Agent

Once the migration is complete, Outlook clients should be redirected to the new Exchange Online. You can control this switch automatically through On Demand Migration console – all you have is to deploy a small utiltity called Client Update Agent to the end-user machines.

Downloading the Agent
  1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the account migration Dashboard, go to step 3.
  2. Click Accounts widget.
  3. Go to the accounts migration dashboard and click More Actions | Download Agent action.
  4. Click Download.

IMPORTANT: The Client Update Agent package comes with the certificate for securing connections between the agent and On Demand Migration. If you suspect that the certificate might be compromised – download the package again, selecting Reissue the certificate option. The previously issued certificate will be immediately revoked.

Deploying the Agent

The Client Update Agent package comes with the agent’s executable that checks the migration status and performs the switching odmclient.exe and the certificate for securing connections between the agent and On Demand Migration certificate.pfx. Now you can automatically distribute then across all clients:

  1. Deploy the certificate to all end-user machines with Group Policy.

See https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/distribute-certificates-to-client-computers-by-using-group-policy for details.

  1. Create a logon script for client computers.
    For detailed information on command-line parameters, refer to the document (readme.txt) that comes with the package.

Migrating Mailboxes

Make sure that all associated accounts are matched or migrated and create the Mail Migration task:

  1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the account migration Dashboard, go to step 3.
  2. Click Accounts widget.
  1. Open Mailboxes and select the mailboxes you want to migrate.

TIP: Use search, filtering or collections to quickly navigate through the list of mailboxes.

  1. Click Migrate Mailboxes.
  2. Select the active licensing plan with Exchange Online options that will be used on the target tenant. Re-run the discovery task to update available licensing plan data, if necessary.
  3. Specify how the licenses will be assigned to the target users during the mailbox provisioning:
    • Replace all license assignments with the licenses from the selected plan. Licensed users will be switched to the selected plan.
    • Retain the existing licenses and assign the selected plan only to unlicensed accounts (default). Licensed users will retain the existing plans.

IMPORTANT: Consider the following:

  • Resource mailboxes that have not been licensed on the source tenant will retain the unlicensed status.
  • Licensed resource mailboxes will be handled according to the selected option.
  • In case no usage location is set on the target the source value will be used for the assigned license. Otherwise the target usage location value remain unchanged and can be modified manually, if necessary.

Selected licensing option is only applicable to Exchange Online. It does not affect the licensing plans picked for OneDrive Migration. Click Next.

  1. Specify the migration scenario.
    • From Primary Mailbox to Primary mailbox - migrate content of the primary mailbox (default scenario.)
    • From Archive mailbox to Archive mailbox - migrate content of the archive mailbox.
    • From Archive mailbox to Primary mailbox - restore archived content to primary mailbox.
    • From Primary mailbox to Archive mailbox - migrate some of the content of the primary mailbox to archive. Useful with the specific Migration Options selected.

Tip: It can take a while to migrate mail to archive mailboxes. Source mailboxes that have archives can be easily selected using Inventoryreport on Assessment view of Mailboxes. It would be useful to re-run the Discovery task to update the information.

  1. Specify which mailbox items (email, contacts, calendar appointments, recoverable items, tasks, and so on.) you want to transfer to the target.

Caution:

  • Recoverable items, mailbox delegation, and folder permissions are not included by default, thus they are not transferred to the target. If you want to keep this data select corresponding option on this step.
  • For all mailboxes that are migrated to the existing target mailboxes, On Demand Migration removes all the existing rules (OWA Inbox rules and the rules created in Outlook) from the target first (including previously-migrated rules), and then migrates all the rules from the source to the target.

Consider the following:

  • Mailbox delegation permissions (Full Access, Send As, and Send On Behalf) can be transferred only in case the matched delegate exists on target. In case matched delegate does not exists, mailbox delegation cannot be migrated and an error will be reported. In case the target mailbox delegation is not set, the mailbox delegation will be transferred as is. In case the mailbox delegation as been set in target before the migration starts, rules and exceptions specified in Migrating Delegate Access Permissions section of On Demand Migration for Email User Guide are applicable to set mailbox delegation.
  • Folder permission in case the target permission does not exist will be transferred as is. In case the folder permissions were already set in target before the migration starts, rules and exceptions specified in Migrating Folder Permissions section of On Demand Migration for Email User Guide are applicable to set folder permissions.

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

Click Next.

  1. Specify which mail folders should be transferred during mail migration processing, if necessary. Click Next.
  2. Limit the date range for content transfer. You can set any of the following options:
    • Migrate mail before to set end date for the date range
    • Migrate mail after to set start date for the date range
  3. Schedule when the task will be started. See Task Scheduling for details.
  1. Click Next to view the task summary. Name the task and check selected options. Click Finish to save or start the task depending on schedule option selected.

The mail migration task is created. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events.

Mailbox Migration Considerations
  • The following types of mailboxes are supported: Regular, Room, Equipment (Resource), Shared.
  • In case of re-migration, On Demand Migration remigrates mail, calendar, task, and sticky note items that have changed in the source mailbox to the target mailbox. Also, calendar items that have been removed from the source mailbox will be removed from the target mailbox. Re-migration of other types of items that have been modified or deleted in the source mailbox is not supported.
  • During the mail migration, users might receive email to both source and target mailboxes. Apparently the users might want to receive the email sent to both mailboxes or keep custom forwarding, if any. To achieve this, we automatically set up mail forwarding from target to source which works until the clients are switched to the target tenant.

 

 

Switching Clients

The mail migration is complete and you have deployed Client Update Agent in your on premises environment. Now it is time to switch the Outlook clients to the target Exchange Online.

Note: Client Update Agent may incorrectly switch the client profile during the transfer of the vanity domain name from the source tenant to the target tenant. It is not recommended to create a Mailbox Switch task during domain name transfers.

Create a Mailbox Switch Task:

  1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the account migration Dashboard, go to step 3.
  2. Click Accounts widget.
  1. Open Mailboxes.
  2. Select the migrated mailboxes.

NOTE: Only migrated mailboxes can be switched. Use filtering by Completed status to see all migrated mailboxes.

  1. Click Switch Mailboxes.
  2. Specify mail forwarding direction:
    • From source to target – standard switching scenario (switch). The clients are automatically switched to the target tenant, but custom forwarding, if set, remains unchanged as described in Mail Forwarding Scenarios
    • From target to source – reverse scenario (unswitch). The users are connected to the source tenant and all email sent to the target addresses are forwarded to the source / to custom forwarding address, if set, as described in Mail Forwarding Scenarios.

Tip In case of Outlook 2013 usage, the external Autodiscover service is required for reverse scenario. You can use Microsoft Office Outlook Connectivity Tests (Office 365 tab) to check whether Service Connection Point (SCP) is available from the cloud. Otherwise the switch fails and the following message is returned by server: Autodiscover service returned: Unauthorized.

  1. Provide the custom domain name for forwarding, typically your corporate domain name. Click Next. To use the same target domain name that was used on the source, you should check whether you have completed all steps of the Tenant to Tenant Migration with Domain Transfer Scenario

IMPORTANT: The custom domain name must be set up on the target tenant. See Quickstart: Add a custom domain name to Azure Active Directory for details.

  1. Configure notification messages (optional), if necessary. See Configuring Notifications for Mailbox Owners for details.
  2. Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.
  3. Check selected options and name the task. Click Finish to save or start the task depending on schedule option selected.

The task is created. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events.

Related Documents