Chat now with support
Chat with Support

On Demand Migration Current - User Guide

About On Demand Migration Before you Start Working with On Demand Migration Account Migration Mailbox Migration OneDrive Migration Microsoft Teams Migration Microsoft 365 Groups Migration SharePoint Migration Public Folders Migration Troubleshooting Finalizing the Migration Appendix A: Working with PowerShell

Upgrading Throttling Policies

Exchange Web Services (EWS) are throttled by Microsoft whenever large quantities of data flows through the EWS platform. The On Demand Migration service throughput can be improved by upgrading the following throttling policy parameter setting to Unlimited:

  • EwsMaxBurst - Defines the amount of time that an EWS user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
  • EwsRechargeRate - Defines the rate at which an EWS user's budget is recharged (budget grows by) during the budget time.
  • EwsCutoffBalance - Defines the resource consumption limits for EWS user before that user is completely blocked from performing operations on a specific component.

Tenant administrators can upgrade the throttling policies by making a service request with Microsoft.

Update Agents

To complete a migration project, a lightweight user desktop application (update agent) must be configured and deployed by administrators and run on users workstations. There are two types of update agents:

Client Update Agent (CUA)

CUA enables users to automatically reconfigure their Microsoft Outlook Profile to connect to the Exchange Online server in the new home tenant.

Desktop Update Agent (DUA)

DUA provides enhanced support, helps ensure the success of cross-tenant migration projects, makes agent delivery easier, and status reporting more informative. DUA has the following advantages over CUA:

  • Ability to manage user’s application reconfigurations activities from a single view within On Demand Migration.
  • Support for OneDrive for Business and Microsoft Teams.
  • Support for Microsoft 365 application license reset.
  • Support for various client authentication mechanisms.

For more information about downloading, administration and use of CUA and DUA, see the Quest On Demand Migration Update Agent Guide.

Working with On Demand Migration

On Demand Migration provides intuitive project management for migrating accounts and content from one tenant to another. You can create a migration project that provides a full range of migration features, and track accounts and content migration in one comprehensive migration project dashboard. You can create multiple migration projects and use the My Projects list view for a summarized list of all your migration projects.

Migration steps

# Step
1 Create a migration project.
2 Match source accounts with the existing target accounts
3 Migrate accounts
4 Start Address Rewriting for Domain Coexistence
5 Migrate mailboxes
6 Grant target users access to source user's resources
7 Migrate OneDrive
8 Migrate Microsoft Teams and other Microsoft 365 Groups
9 Migrate SharePoint
10 Migrate Public Folders
11 Monitor the progress and track issues

Test and Pilot Migrations

Any full scale migration should be preceded by test and pilot migrations, to confirm that your migration processes and procedures will accommodate the organization requirements.

  • A test migration uses real users and real data in a segregated test environment, or dummy users and dummy data in your live production environment.
  • A pilot migration uses a small portion of real users and real data in the live production environment.

In either case - a test or pilot migration - the data to be migrated should be a representative sample of the production data, and the test or pilot migration should be run with the Quest applications set for the same configuration and process options that you intend to use for the production migration. it is recommended to select test or pilot users whose usage and data types make them representative of the total user population. Then create and run matching / migration tasks for those accounts, including all range of tasks you are planning to perform. When the tasks are completed, review errors and warnings, if any. See Event Management section for more information.

Quest recommends that you use both test and pilot migrations:

Perform one or more test migrations in a separate test environment, migrating test copies of real users and their real data. The separate test environment ensures that no test process will affect the data or configurations of your production environment. If a test exposes any problems under migration, you can make amendments and then repeat the test by simply dumping the test environment and recreating it from scratch.

When you are confident that your test migrations have sufficiently refined your planned migration, perform a pilot migration for 20 or 30 users to verify if your planned migration is satisfactory for your "real world."

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating