Self-Service Mailbox Migration in Exchange Online Dedicated

Transcription

1 Dedicated and ITAR-support Plans Self-Service Mailbox Migration in Exchange Online Dedicated Applies to: Office 365 Dedicated - Legacy 2013 Platform Release Topic Last Modified: 31-Jan-2013 Topic Last Modified: 31-Jan-2013 Modifications Applied: Initial Release Mailbox Migration is a self-service feature of the Exchange Online dedicated and ITAR-support plans of Office 365 for enterprises. The Exchange Admin Center (EAC) is used to initiate, manage, and monitor the movement of mailboxes between on-premises environments and Exchange Online. Topic areas described within this self-service migration guide are the following: What is Self-Service Mailbox Migration? 4 Infrastructure Requirements 5 Hybrid Server 5 Network Connectivity 5 Active Directory Synchronization 5 Client Systems 6 Mailbox Migration to/from Exchange Online Dedicated 6 What do you need to know before you begin? 7 On-premises Exchange Server Configuration 7 On-Premises Permissions to Migrate Mailboxes 7 Exchange Online Dedicated Permissions to Migrate Mailboxes 8 Mailbox Preparation 8 Step 1: Create a migration endpoint 9 What do you need to know before you begin? 10 Create a migration endpoint for migrations in an Exchange hybrid deployment 10 How do you know this worked? 13 Step 2: Enable the MRS Proxy 13 Step 3: Create and execute migration batch to move mailboxes 13 Use EAC to manually select and move mailboxes 13 Use remote Windows PowerShell to manually select and move mailboxes 15 Use of a.csv input file for mailbox moves 15 Step 4: Remove completed migration batches 15 Step 5: Re-enable offline access for Outlook Web App 15

2 How do you know this worked? 15 Manage Migration Batches in Exchange Online 17 Migration Dashboard 17 Overall migration statistics 18 Migration batches 19 Commands 20 Migration batch statistics 21 Migration Users Status Report 23 Migration users report 23 Columns in the list of migration users 24 Migration user statistics for a specific user 24 Migration phases 26 Migration Cmdlets 27 Appendix A Factors that affect Exchange Online Dedicated migration performance 30 Overview of Exchange Online Dedicated migration 30 Migration methods available with Exchange Online Dedicated 30 Summary of observed migration performance 31 Overview of Exchange Online migration performance factors 31 Common migration performance factors 32 Network performance factors 33 Office 365 resource health-based throttling 34 Native Office 365 hybrid migration 34 Migration performance factors and best practices 34 Appendix B Using a CSV File for Mailbox Migration 40 Supported attributes for CSV files for bulk moves or migrations 40 On-boarding remote move migrations in a hybrid deployment 41 Off-boarding remote move migrations in a hybrid deployment 42 Attribute values in the CSV file override the values for the migration batch 45 Appendix C Mailbox migration in a multi-region environment 47 Preparation 47 Execution 48 Verification 48 Troubleshooting 49 2

3 Important 1. Preview material may be updated periodically before becoming a published version within the Exchange Online Dedicated area of the Microsoft TechNet Library. Rather than downloading or printing the content, viewing the material at this site is recommended whenever reference information is needed. 2. Not all generally available documentation produced by Microsoft to describe the features and functionality of Exchange 2013 is applicable to the dedicated and ITAR-support plan offerings of Office 365 for enterprises. Content accessible via links provided in this content are reliable sources. 3. Unless otherwise stated, all references to dedicated plans or Exchange Online Dedicated also apply to the International Traffic in Arms Regulations (ITAR-support) version of Exchange Online. 3

4 What is Self-Service Mailbox Migration? The process to migrate mailboxes between an on-premises environment and Exchange Online Dedicated involves establishing the required infrastructure, applying required Active Directory updates for the user objects representing each mailbox, and using specific tools to execute the migration. When an Exchange hybrid deployment has been established to bridge the on-premises and online Exchange organizations, user mailbox data then can be migrated from an on-premises Exchange 2013, Exchange 2010, Exchange 2007, or Exchange 2003 mail server to Exchange Online Dedicated. The movement of mailboxes aligns with the following processes: On-boarding remote move migration: Allows mailboxes from an on-premises Exchange organization or the multi-tenant version of Exchange Online to be moved to Exchange Online Dedicated. The process is also known as an on-boarding remote move migration because you onboard mailboxes to Exchange Online. Off-boarding remote move migration: Allows mailboxes from an Exchange Online Dedicated organization to be migrated to an on-premises Exchange Server or to the multi-tenant version of Exchange Online. The process is known as off-boarding. Notes 1. Both on-boarding and off-boarding remote move migrations involving an on-premises Exchange organization are initiated from your Exchange Online organization. If the offboarding source or on-boarding target is the multi-tenant version of Exchange Online, the EAC migration tool must be launched from within the multi-tenant environment and the required Migration Endpoint (Exchange Online Dedicated) must be indicated and or created. 2. Only mailbox-enabled users within the on-premises Exchange or Exchange Online Dedicated environment can be migrated. 3. To migrate mailboxes from an on-premises environment to multiple geographic regions supported by Exchange Online Dedicated, the Exchange CustomAttribute for each onpremises mailbox user (a.k.a. the Extension Attribute of a user object held in Active Directory) must be set. See the SetMailboxType section of the Office 365 Dedicated and ITAR-support Plans Provisioning Tools Handbook held within the Customer Extranet site for additional information. Once the attribute has been set, the migration feature will automatically route the mailbox to the correct region. 4

5 Infrastructure Requirements Hybrid Server The initial on-boarding of user mailbox data requires the use of a separate on-premises Exchange Server referred to as a hybrid server to bridge the on-premises and online Exchange organizations. A hybrid server can be used to support just the migration of mailboxes during the migration period or it can be used in a long term coexistence configuration to support migrations as well as the presentation of calendar free/busy availability and calendar sharing between the on-premises and online organizations. The requirements for the hybrid server are described in Exchange Server 2013 Hybrid Deployment for Exchange Online Dedicated. After a hybrid configuration has been chosen and implemented, specific processes must be followed and specific tools must be used to perform the mailbox migrations. Network Connectivity You must verify that network connectivity exists between the Exchange Online Dedicated organization and your onpremises Exchange organization. Connectivity can be via the dedicated networking facilities between Exchange Online Dedicated and your on-premises systems, via the Internet, or a combination of both. Active Directory Synchronization The Microsoft Managed Solutions Services Provisioning Provider tool (MMSSPP commonly referred to as Mississippi ) is used to propagate on-premises Active Directory object data to the Active Directory of Office 365 Dedicated. To support an on-boarding migration of your on-premises mailboxes to Exchange Online Dedicated, a corresponding object must exist in the Active Directory of Office 365 Dedicated. For additional information describing how provisioning is implemented within Office 365 Dedicated, how MMSSPP functions, and how to initially configure your on-premises Active Directory for MMSSPP synchronization, see the MMSSPP & Provisioning Tools landing page within the Customer Extranet site to access the links to the MMSSPP Customer Deployment Guide, MMSSPP Identity Synchronization Handbook, and the Office 365 Dedicated and ITAR-support Plans Provisioning Tools Handbook. Note If MMSSPP must synchronize any user objects that have mailboxes in Exchange environments that are hosted in other Active Directory forests (i.e., not the primary forest being used for the MMSSPP synchronization), these objects must have all of their Exchange service specific settings (e.g., PublicDelegates, msexchrequireauthtosendto, authoring, etc.) copied to the Active Directory object in the forest from which MMSSPP synchronizes. See Appendix B of the MMSSPP Identity Synchronization Handbook for a complete list of the attributes by object type that are currently supported for synchronization by MMSSPP. 5

6 To gain an understanding of the object attributes you will need to populate in your on-premises Active Directory to support an off-boarding migration, see the attribute listings shown in Prepare Mailboxes for Cross-Forest Move Requests. If a large scale on-boarding or off-boarding if mailboxes is required due to a corporate divestiture, merger, or acquisition, contact your Service Delivery Manager for additional guidance. Client Systems Prior to the start of the migration, all client systems must be confirmed to be compliant for use with Exchange Online. See the client system software requirements description of the Client and Application Connectivity section of the Exchange Online Dedicated Service Description. Mailbox Migration to/from Exchange Online Dedicated Within Exchange Online Dedicated, individual or multiple mailboxes can be migrated using the Exchange Admin Center (EAC) or remote Windows PowerShell. Exchange Online Dedicated is used to manage mailbox migration in either direction between the on-premises and online environments via the hybrid Exchange server within in your on-premises environment. As described in the Infrastructure Requirements section above, you must have an Exchange hybrid server deployed to use the remote move migration method for migrations to/from the on-premises environment. Mailbox migration between the multi-tenant and dedicated versions of Exchange Online does not require the use of a hybrid server. The remote move migration method is used to migrate mailboxes via an on-premises Exchange hybrid server. The execution of mailbox migrations is invoked as a batch. The batch can be created by manually selecting one or more mailboxes from the source forest or by preparing a Comma Separated Values (.csv) file that lists the mailboxes to be migrate. The.csv file can be uploaded into EAC or used by the New-MigrationBatch cmdlet from within remote Windows PowerShell. Notes 1. Both on-boarding and off-boarding remote move migrations involving an on-premises Exchange organization are initiated from your Exchange Online organization. If the off-boarding source or onboarding target is the multi-tenant version of Exchange Online, the migration must be launched from within the multi-tenant environment, the required Migration Endpoint (Exchange Online Dedicated) must be created, and this endpoint must be referenced when invoking the migration. Other configuration steps also must be addressed to initiate a migration involving the multi-tenant version of Exchange Online contact your Service Delivery Manager for assistance. 2. If a user has an archive mailbox either as an element of a standard active mailbox account or while on Legal Hold, both the primary and archive mailboxes will be migrated. 3. For a configuration involving the presence of Lotus Domino mailboxes on-premises, see the Planning, Deployment, and Migration section of the Exchange Online Dedicated Service Description for a description of migration services offered for this mailbox type. 6

7 What do you need to know before you begin? In addition to the infrastructure requirements described above, the collection of requirements included below must be met prior to the start of mailbox migrations. On-premises Exchange Server Configuration The mailbox Replication Service Proxy (MRS Proxy) must be enabled on your on-premises Exchange 2010/2013 Client Access servers (if configured to fulfill the hybrid server role) or on your standalone hybrid Exchange server if your on-premises mail server is Exchange 2003/2007. Also, the Exchange 2010/2013 Client Access server of your hybrid deployment must be configured to send and receive network traffic on Port 443 from the /16 subnet (mailbox migration data will be transferred between Exchange Online Dedicated and the customer environment on Port 443). On-Premises Permissions to Migrate Mailboxes When you migrate on-premises Exchange mailboxes to and from Exchange Online Dedicated, the on-premises account that you use to connect to your on-premises Exchange organization during the migration must have the necessary permissions to access, and in some cases modify, the on-premises mailboxes that you want to migrate. The account, referred to as the migration administrator, is used to create a migration endpoint for your onpremises organization. To successfully create a migration endpoint (or to create a migration batch if no migration endpoints exist in your Exchange Online organization), the migration administrator account must align with at least one of the following permission options within your on-premises Exchange organization: The migration administrator must be a member of the Domain Admins administrative group in Active Directory in the on-premises organization; or The migration administrator must be a member of the Exchange Recipients Administrators admistrative group in Active Directory in the on-premises organization AND be a Local Administrator on all Client Access Servers that will be used as migration MRS Proxy endpoints; or If you have an on-premises Exchange 2010 and Exchange 2013 organization, the migration administrator must be a member of the Organization Management or Recipient Management built-in role group (the default roles associated with the built-in role groups and the original exposed cmdlets/parameters for these groups are assumed to exist) AND be a Local Administrator on all Client Access servers that will be used as migration MRS Proxy endpoints. You can use the Exchange Management Shell in your on-premises organization to assign the necessary permissions to migrate mailboxes to Exchange Online. 7

8 Notes Since Exchange Server 2003 does not support the Exchange Management Shell, you have to use the Active Directory Users and Computers view to grant Full Access permission and also use Exchange Server Manager to assign the Receive As permission. For more information, see the following: How to assign users or groups full access to other user mailboxes How to assign service account access to all mailboxes in Exchange Server 2003 Exchange Online Dedicated Permissions to Migrate Mailboxes In addition to establishing appropriate access to the on-premises Exchange environment, you need to be a member of the Mailbox Migrations role group within Exchange Online Dedicated. A self-service administration account is used to initiate and manage cross-forest remote move migrations to Exchange Online. See the Self- Service Administration content within the Exchange 2013 Platform Readiness area of the Customer Extranet site for additional information. Mailbox Preparation The size of a mailbox and available network bandwidth are limiting factors in achieving a high migration velocity. A common practice to reduce the size of the mailbox is to move items out of the mailbox to an archive (e.g., a.pst file) either manually or with auto-archive functionality. To reduce mailbox size, the following actions are recommended: Delete or archive mail in the Sent Items folder. Delete or archive all Calendar attachments. Delete or archive Calendar items over 30 days old. Delete or archive Inbox items over 90 days old. Search for and delete attachments over 5 MB. Disable Journaling. Empty the Deleted Items folder. Run the Mailbox Cleanup wizard from the Outlook Tools menu (Outlook only). Notes 1. If the mailbox owner moves the mail items back to the new Exchange Online mailbox after migration, the Exchange Online mailbox will not allow the user to reply to these mail items. 2. The day span and file sizes described in the bullet list above are recommendations only; these values may not be suitable for your organization. 8

9 Your organization will need to assess the number of mailboxes, size of each mailbox, and the rate of mailbox size growth in your existing environment. The information obtained will help you evaluate the impact of migration traffic on your network. If your organization enforces maximum mailbox size limits, this information also is important to consider when you define Exchange Online storage capacities. Your new Exchange Online environment should let all users store the same amount of data allowed for their mailbox and also be size to accommodate growth. You should also confirm if the capacities of your Exchange Online plan(s) support your existing mailbox inventory. Each Exchange Online Dedicated plan supports a specific mailbox storage level. For more information, see the Standard Messaging Plan Mailboxes description of the Mailbox Features section of the Exchange Online Dedicated Service Description. For additional recommendations to streamline the migration process, see Appendix A Factors that affect Exchange Online Dedicated migration performance. If assistance is required to support any level of migration planning and preparation, contact your Service Delivery Manager to gain access to additional Microsoft resources. Step 1: Create a migration endpoint A migration endpoint is a management object that contains the connection settings and administrator credentials for your on-premises environment. The migration endpoint also defines the number of mailboxes to migrate simultaneously during initial synchronization and the number of mailboxes to synchronize simultaneously during incremental synchronization (occurrence once every 24 hours for selected migration types). During incremental synchronization, on-premises and Exchange Online mailboxes are synchronized so that new sent to mailboxes on the source server is copied to the corresponding Exchange Online mailbox. Prior to the execution of a remote move migration to on-board or off-board mailboxes in an Exchange hybrid deployment, an Exchange remote migration endpoint must be created. Consider the following: Recommended is the creation of the migration endpoint in advance followed by selection of the endpoint when the migration batch is created (Step #3 below). If no endpoints exist at the time a migration batch is created, you can provide server and remote credentials when prompted during the batch creation step. If one or more endpoints have been configured but the endpoint you require is not present in the list of available endpoints displayed at the time the migration batch is created, you must follow the Use the EAC to create an Exchange remote migration endpoint instructions below to add your entry to the endpoint selection list. 9

10 What do you need to know before you begin? Estimated time to complete each procedure: 3 minutes. You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the Mailbox Move and Migration Permissions section in the Recipients Permissions topic. When you create a migration endpoint, by default, it will support 20 maximum concurrent migrations during initial synchronization and a maximum of 10 concurrent incremental synchronizations. You can specify a different number of concurrent migrations when you create a migration endpoint. To change these settings, you can edit an existing migration endpoint using the EAC or the Set-MigrationEndpoint cmdlet. There is a limit of 100 concurrent migrations. We recommend that you test the connection settings to the server that hosts the mailboxes that you want to migrate. The connection settings will be tested when you create a migration endpoint; verifying the settings before you create an endpoint will give you an opportunity to troubleshoot any issues. Run the following commands using remote Windows PowerShell within Exchange Online Dedicated to test the connection settings to the source server: $Credentials = Get-Credential Test-MigrationServerAvailability ExchangeRemoteMove Autodiscover Address < address for on-premises administrator account> -Credentials $Credentials For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard Shortcuts in the Exchange Admin Center. Create a migration endpoint for migrations in an Exchange hybrid deployment The migration endpoint contains the connection settings for a Client Access server in your on-premises Exchange organization. Note The same Exchange remote migration endpoint can be used for moving on-premises mailboxes to Exchange Online or for moving Exchange Online mailboxes to your on-premises organization Important You must have a hybrid deployment configured between your on-premises and Exchange Online organizations to create an Exchange remote migration endpoint and to use remote move migrations to move mailboxes between your on-premises and Exchange Online organizations. For more information regarding hybrid deployments, review the Infrastructure Requirements section above. 10

11 Use the EAC to create an Exchange remote migration endpoint 1. In the EAC of Exchange Online Dedicated, navigate to Recipients > Migration. 2. Click (more) on the EAC toolbar and select Migration endpoints in the pop-up that appears. 3. On the Migration endpoints page, click (add). 4. On the Enter on-premises account credentials page, complete the following boxes: address Type the address of any user in the on-premises Exchange organization that will be migrated using this endpoint. Exchange Online will test the connectivity to this user's mailbox. Account with privileges Type the user name (using the domain\user name format or address) for an account that has the necessary administrative privileges in the on-premises organization. Exchange Online will use the Autodiscover service and this account to detect the migration endpoint and to test the permissions assigned to this account by accessing the mailbox specified in the previous box. Password of account with privileges Type the password for the administrator account that you specified in the previous box. 5. Click Next. Exchange Online uses the information provided to test connectivity to an on-premises server and then displays the Confirm the migration endpoint page. Do one of the following based on whether the connection settings were successfully detected: o o If Exchange Online successfully connects to an on-premises server, the connection settings are displayed. Click Next. If the test connection to an on-premises server isn't successful, you have to enter the fully qualified domain name (FQDN) of the on-premises server that the MRS Proxy service is running on in your hybrid deployment (e.g., mail.contoso.com). The MRS Proxy service typically runs on the Exchange Client Access server in your on-premises organization. You have to successfully connect to an onpremises server to continue. Important Online creates a new migration endpoint using the connection settings that were successfully discovered or that you provided manually. We recommend that you create migration endpoints whose connection settings were automatically discovered rather than creating endpoints whose settings you entered manually. This is because the Autodiscover service will be used to connect to each user mailbox during the migration. If manual settings are used, Exchange Online won't use the Autodiscover service, but will connect to a specific source server using the connection settings you manually entered. If you use manual settings and have multiple on-premises Exchange servers, you may need to create different migration endpoints that correspond to each server. 7. Click Next. Enter information in the following boxes: Migration endpoint name - Name displayed in the list of migration endpoints. It's also used in the drop-down list of migration endpoints when you select a migration endpoint while creating a migration batch. This is required. 11

12 Maximum concurrent migrations - Number of connections to the source server that are available to migrate on-premises mailboxes and mailbox items to Exchange Online during initial and incremental synchronization. If the value is set to 20, which is the default value, you can migrate up to 20 mailboxes at the same time. If multiple migration batches use the same Exchange remote migration endpoint, the maximum number of concurrent migrations allowed by the migration endpoint is shared across all the migration batches. Note As previously stated, there is a limit of 100 concurrent migrations for all Exchange remote migration endpoints in your organization. Maximum concurrent incremental syncs - Number of connections to the source server that are available to perform incremental synchronizations. If the value is set to 10, the default value, then incremental synchronization can be performed on up to 10 mailboxes at the same time. For example, if the endpoint is configured with 100 maximum concurrent migrations and 40 maximum concurrent incremental syncs, 40 connections can be used for incremental synchronization, if necessary. The other 60 connections are reserved for initial synchronizations. 8. Click New to create the migration endpoint. Use the Shell to create an Exchange remote migration endpoint This example creates a migration endpoint that can be used to support either on-boarding or off-boarding for remote move migrations. In both cases, the migration endpoint is an Exchange server in your on-premises Exchange organization that is running the MRS Proxy service typically the Client Access server. Using remote Windows PowerShell in your Exchange Online Dedicated environment, execute the steps below. Note You must be a member of the Mailbox Migration role group within Exchange Online Dedicated to execute the New-MigrationEndpoint cmdlet shown below. $Credentials = Get-Credential New-MigrationEndpoint ExchangeRemoteMove Name OnpremEndpoint -Autodiscover Address < address for on-premises administrator account> -Credentials $Credentials 12

13 How do you know this worked? To verify that you've successfully created an Exchange remote migration endpoint, do one of the following: 1. In the EAC, navigate to Recipients > Migration. 2. Click (more) on the EAC toolbar and select Migration endpoints in the pop-up that appears. The new migration endpoint is displayed in the list, and the endpoint type is Exchange Remote. Alternatively, use remote Windows PowerShell to run the following command to display information about the migration endpoint: Get-MigrationEndpoint <identity> Format-List EndpointType,RemoteServer,UseAutoDiscover,Max* Step 2: Enable the MRS Proxy To allow the on-premises Client Access server to accept incoming remote move requests, you have to enable the MRS Proxy endpoint. If the MRS Proxy is not already enabled, follow these steps in the EAC: 1. Within the on-premises Exchange organization, open the EAC and navigate to Servers > Virtual Directories. 2. Select the Client Access server, select the EWS virtual directory, and click Edit. 3. Select the MRS Proxy enabled check box and then click Save. See Enable the MRS Proxy Endpoint for Remote Moves for additional information including Windows PowerShell examples. Step 3: Create and execute migration batch to move mailboxes You can use the migration dashboard of the EAC or remote Windows PowerShell in Exchange Online Dedicated to either move existing user mailboxes in the on-premises organization to the Exchange Online organization or to move Exchange Online mailboxes to the on-premises organization. A Comma Separated Values (.csv) file containing all mailboxes to be migrated also can be used as input for the EAC or PowerShell options. Use EAC to manually select and move mailboxes Within Exchange Online Dedicated, perform the following: 1. Open the EAC and then navigate to Office 365 Dedicated > Recipients > Migration. 2. Click + (add) and then select either of the following: Migrate to Exchange Online Migrate from Exchange Online 3. On the Select the users page, click + (add), select the on-premises users to move to Office 365, click + (add), and then click OK. Click Next. 13

14 4. If moving on-premises mailboxes to Exchange Online Dedicated and migration endpoints have not been created, the Enter the Windows user account credential page will appear. Enter the on-premises administrator account name in the On-premises administrator name text field and enter the associated password for this account in the On-premises administrator password text field. For example, corp\administrator and a password. Click Next. Note If you ve already created a migration endpoint, you ll receive an endpoint confirmation prompt for this step. If you ve created two or more migration endpoints, you must choose an endpoint from the migration endpoint drop-down menu. 5. On the Confirm the migration endpoint page, verify that the FDQN of your on-premises Client Access server is listed when the dashboard shows a confirmation of the migration endpoint. For example, mail.contoso.com. Click Next. Note The MRS Proxy service on the Exchange Client Access servers automatically throttles the mailbox move requests when you select multiple mailboxes to move to Exchange Online. The total time to complete the mailbox move depends on the total number of mailboxes selected, the size of the mailboxes, and the configuration of the MRS Proxy. 6. On the Move configuration page, enter a name for the migration batch in the New migration batch name text field. Use the down arrow to select the Target delivery domain for the mailboxes that are migrating to Office 365 Dedicated. In most hybrid deployments, this is the coexistence SMTP domain used for Exchange Online organization mailboxes. For example, mgd.contoso.com. To apply specific migration settings for BadItemLimit and LargeItemLimit, select More Options in this view. Descriptions of the limit options can be found in the Parameters section of the New-MigrationBatch cmdlet description (custom cmdlet version specifically for Exchange Online Dedicated see Migration Cmdlets below). Click Next. 7. On the Start the batch page, select at least one recipient to receive the batch complete report. Also select appropriate batch start and complete options. Select Automatically start the batch and Automatically complete the migration batch options if custom settings are not required. If start/complete options are required, see the New-MigrationBatch cmdlet description (custom version specifically for Exchange Online Dedicated) in the Migration Cmdlets section below. After all start/complete settings have been applied, click New. Note If you must migrate an Inactive mailbox, the mailbox first must be re-enabled as an active mailbox type, migrated, and then placed back into an inactive status on the destination system. 14

15 Use remote Windows PowerShell to manually select and move mailboxes To use remote Windows PowerShell to execute a remote move migration, see the New-MigrationBatch cmdlet description (custom version specifically for Exchange Online Dedicated) in the Migration Cmdlets section below. Use of a.csv input file for mailbox moves You can use a CSV file to bulk migrate a large number of user mailboxes. You can specify a CSV file when you use the Exchange Admin Center (EAC) or remote Windows PowerShell to create a migration batch. For additional information, see Appendix B - Using a CSV File for Mailbox Migration. Step 4: Remove completed migration batches After your mailbox moves have completed, we recommend the completed migration batches to minimize the likelihood of errors if the same users are moved again. To remove a completed migration batch: 1. Open the EAC and navigate to Office 365 Dedicated > Recipients > Migrations. 2. Click a completed migration batch, and then click Delete. 3. On the deletion warning confirmation dialog, click Save. Step 5: Re-enable offline access for Outlook Web App Offline access in Outlook Web App lets users access their mailbox when they are not connected to a network. The default Client Access server configuration of Exchange Online Dedicated enables Outlook Web App offline access. If the feature was enabled for supported Web browsers using group policy settings within the on-premises environment prior to the migration of mailboxes, the offline access feature will be active following migration to Exchange Online Dedicated. See Offline access in Outlook Web App 2013 for a description of the offline access feature including use of the Set-OwaMailboxPolicy cmdlet to enable/disable the feature (an exposed remote Windows PowerShell cmdlet within Exchange Online Dedicated). See Using Outlook Web App offline for a user level description of the feature. How do you know this worked? You can verify the status of the migration batch by opening the EAC and selecting Office 365 Dedicated > Recipients > Migration. You can also run the following remote Windows PowerShell cmdlet to verify the status of the migration batch: Get-MigrationBatch Identity <batch name> Within the EAC, the move status for specific mailboxes within the batch can be viewed by selecting Recipients > Migration. The Status value is Syncing during the mailbox move and it is Completed when the mailbox has successfully migrated. 15

16 When the Status entry for the migrated mailbox is Completed, you can verify the result by examining the properties of the mailbox. For an on-boarding migration, access the EAC of Exchange Online Dedicated, navigate to the Recipients area, and select the tab that represents the type of mailbox that was migrated, i.e., User for a standard or shared mailbox or Resource for a resource mailbox. The mailbox should show a Mailbox Type of Linked. If Exchange Server 2013 is the on-premises version of Exchange to receive off-boarded mailboxes, the mailbox value type displayed in the on-premises EAC will be User. For either environment, the Windows PowerShell cmdlet Get-Mailbox can be used to check mailbox status. Mailbox Type Destination EAC Navigation Mailbox Type Value Exchange Environment in Destination Environment Displayed User Online Recipients > Mailboxes Linked User On-premises Recipients > Mailboxes User Resource Online Recipients > Resource Room or Equipment Resource On-premises Recipients > Resource Room or Equipment Shared Online Recipients > Mailboxes 1 Linked Shared On-premises Recipients > Mailboxes 1 User 1 Exchange Online Dedicated does not use the RecipientType and RecipientTypeDetails properties of Exchange Server to identify shared mailboxes; thus, the shared tab of the EAC is not applicable. A shared mailbox is represented as a user mailbox within Exchange Online Dedicated. The provisioning attribute for the object that represents a shared mailbox must be set to include TYPE=SHARED. See the Office 365 Dedicated and ITAR-support Plans Provisioning Handbook for additional information. 16

17 Manage Migration Batches in Exchange Online You can use the Migration dashboard in the Exchange Admin Center (EAC) to manage mailbox migrations to Exchange Online Dedicated. The Migration dashboard displays statistics about the overall migration in addition to statistics about a specific migration batch. You can create, start, stop, pause, and edit migration batches. Migration Dashboard To access the Migration dashboard in the EAC, select Recipients > Migration. The following screenshot identifies the different areas of the Migration dashboard that you can use to get migration information and manage migration batches. Included below are descriptions of the five sections highlighted in the EAC migration Tab view shown above. 17

18 Overall migration statistics Click Status for all batches to display the overall statistics about all migration batches that have been created. The following fields display cumulative information about all migration batches. Field Total mailboxes Synced mailboxes Finalized mailboxes Failed mailboxes Description The total number of mailboxes from all current migration batches. The number of mailboxes from all migration batches that were successfully migrated. The number of mailboxes from all migration batches that have been finalized. Finalization only occurs when using remote move migrations to migrate mailboxes between your on-premises Exchange organization and Exchange Online in an Exchange hybrid deployment. Mailboxes can be finalized after the initial synchronization is successfully completed. For more information about finalizations in remote move migrations, see Complete- MigrationBatch. The number of mailboxes from all migration batches for which migration failed. 18

19 Migration batches Migration batches that are created are listed in the migration queue. The following columns display information about each migration batch. Column Name Status Total Synced Finalized Failed Description The name of the migration batch that was defined when the migration batch was created. The status of the migration batch. The following is a list of the different status states for migration batches, along with what you can do with migration batches in each of these states: Created: The migration batch has been created, but it hasn't been started. In this state, you can start, edit, or delete it. Syncing: The migration batch has been started, and mailboxes in the migration batch are being actively migrated. When a migration batch is in this state, you can stop it. Stopped: The migration batch is stopped, and no more mailboxes from the batch are being migrated. When a migration batch is in this state, you can restart it. Synced: The migration batch has completed, and no mailboxes are being actively migrated. A migration batch in this state may contain errors if mailboxes weren t migrated. Synced with errors: The migration batch has completed, but some mailboxes failed migration. Mailboxes that were successfully migrated in migration batches with errors are still synchronized every 24 hours during incremental synchronization. Indicates the number of mailboxes in the migration batch. Indicates the number of mailboxes that were successfully migrated. The number of mailboxes in the migration batch that have been finalized. Finalization is only performed for migration batches for remote move migrations in an Exchange hybrid deployment. For more information about the finalization process, see Complete-MigrationBatch. The number of mailboxes in the migration batch for which migration failed. You can display information about specific mailboxes that have migration errors. For more information, see Migration Users Status Report. Important Migration batches with a status of Synced that have no administrator-initiated activity for the last 90 days (for example, no administrator has stopped and restarted a migration batch or edited a migration batch) will be stopped and then deleted 30 days later if no further action is taken by the administrator. 19

20 Commands The Migration dashboard contains a set of commands that you can use to manage migration batches. After you create a migration batch, you can select it and then click one of the following commands. If a migration batch is in a status state that isn t supported by a command, the command is either dimmed or not displayed because it s unavailable. Command New Edit Start Resume Pause Delete More Refresh Description Create a new migration batch. Use this command to migrate onpremises mailboxes to Exchange Online (also called on-boarding) or to migrate Exchange Online mailboxes back to your on-premises Exchange organization in a hybrid deployment. Edit an existing migration batch. You can change the migration endpoint used for the migration batch. You can only edit a migration batch that has a status of Created. Start a migration batch that s been created. After the batch is started, the status is changed to Syncing. Resume the running of a migration batch that was paused and has a status of Stopped. If there are errors for a migration batch, you can restart it with this command and Exchange Online will attempt to migrate the mailboxes that failed. Stop a migration batch that s currently running or that s been started but has a status of Queued. You can resume incremental synchronizations by selecting the migration batch and clicking Resume. Delete a migration batch after you verify that all mailboxes in the migration batch have been successfully migrated and that mail is being routed directly to cloud-based mailboxes after you ve configured your MX record to point to Office 365. When you delete a migration batch, Exchange Online cleans up any records related to the migration batch and removes it from the list. Click this command and then click Migration endpoints to create new migration endpoints or view and edit existing migration endpoints. For more information, see Create Migration Endpoints. Refresh the Migration dashboard to update the information displayed for the overall migration statistics, the list of migration batches, and the statistics for the selected migration batch. 20

21 Migration batch statistics The details pane in the Migration dashboard displays the following information about the selected migration batch. Overall Status Field Type Direction Status Description Indicates the migration type of the selected migration batch. The value of this field also denotes the type of migration endpoint associated with the migration batch. Remote move migration: The migration batch is either an onboarding or off-boarding remote move migration in an Exchange hybrid deployment. Indicates if mailboxes are being migrated to Exchange Online or to your on-premises Exchange organization. On-boarding indicates that mailboxes are being migrated to Exchange Online. The supported on-boarding migration type for Exchange Online Dedicated is remote move migrations. Off-boarding indicates that Exchange Online mailboxes are being migrated to your on-premises Exchange organization. Off-boarding remote move migrations are the only type of offboarding migration. The current state of the selected migration batch. Created Syncing Stopped Synced Synced with errors See the previous description of each of these states. 21

22 Mailbox Status Synced mailboxes Finalized Failed mailboxes View details The number of mailboxes out of the total number in the migration batch that have successfully completed initial synchronization. This field is updated during the migration. The number of mailboxes out of the total number in the migration batch that have successfully been finalized. Finalization only occurs in on-boarding and off-boarding remote move migrations. The number of mailboxes that failed initial synchronization. Click View details to display status information for each mailbox in the migration batch. For more information, see Migration Users Status Report. Statistics Field Created by Create time Start time Initial sync time Initial sync duration Last sync time Associated endpoint Description The address of the Exchange Online administrator who created the migration batch. The date and time when the migration batch was created. The date and time when the migration batch was started. For batches scheduled with the StartAfter time/date variable set, the Start time will display as $null as this reflects the time the batch was initially submitted. The date and time when the migration batch completed initial synchronization. The amount of time it took to complete the initial synchronization for all mailboxes in the migration batch. The last time the migration batch was restarted or the last time that incremental synchronization was performed for the batch. The name of the migration endpoint being used by the migration batch. You can click View details to view the migration endpoint settings. You can also edit the settings if none of the migration batches using the endpoint are currently running. 22

23 Migration Users Status Report You can use the Migration dashboard in the Exchange Administration Center (EAC) to display migration status information for all mailboxes in a migration batch. You can also display detailed migration information for each user in a migration batch. This information, also called migration user statistics, can help you troubleshoot issues that might prevent the migration of a user s mailbox or mailbox items. You can display this migration status information for migration batches that are currently running, that have been stopped, or that are complete. Migration users report To access the migration users report for a migration batch, select Recipients > Migration, select the migration batch, and then click View details under Mailbox status in the details pane. 23

24 The name of the migration batch and the following commands are displayed at the top of the window. Command Delete Refresh Description Delete the selected user from the list of migration users. Refresh the list of migration users to update the information displayed for the users in the migration batch. Columns in the list of migration users Column Address Status Items Synced Items Skipped Description The user s address. The user s migration status. See the status descriptions in the table in the next section. The number of items in the user s on-premises mailbox that were successfully migrated to the Exchange Online mailbox. The number of items in the user s on-premises mailbox that weren t migrated to the Exchange Online mailbox. Migration user statistics for a specific user To view status information (also called migration user statistics) for a specific mailbox, mail contact, or distribution group, click the mailbox, contact, or distribution group in the list. Status information for the selected mail object is displayed in the details pane. The following table describes each field displayed in the details pane. Field Status Description Identifies the specific point in the migration process for each mail object in the migration batch. This status is more specific than the high-level status summary displayed in the list of migration users. The following list describes each status state. Queued The object is in a migration batch that is running, but the migration of the object hasn t started yet. Objects typically have a status of Queued when all of the connections in the migration endpoint associated with the migration batch are being used. Provisioning The migration process has started for the mail object, but it isn t provisioned yet. Provision updating The mail object has been provisioned, but not all of the object s properties were migrated. For example, after a distribution group has been migrated, this state occurs when members of the group haven t been migrated yet or 24

25 Field Skipped item details Data migrated Migration rate Error Report Last successful sync date Description there s a problem migrating a user who is a member of the group. In this case, the status indicates the migration process can t update the group membership because not all group members have been migrated. Synced The migration process successfully provisioned the Exchange Online mailbox and completed the initial synchronization where all mailbox items were copied to the cloud-based mailbox. For cutover Exchange migrations and IMAP migrations, this status can also indicate that incremental synchronization completed successfully. Failed The provisioning or the initial synchronization of the mail object failed. If an Exchange Online mailbox is successfully created for a user, but the migration of mailbox items fails, the status for the user will be Failed. Click Skipped item details to display information about each item that was skipped for the selected user. The following information about each skipped item is displayed: Date The time stamp of the mailbox item. Subject The subject line of the message. Kind The type of error that caused the item to be skipped. Folder name The folder where the skipped item is located. The total amount of data (in bytes and megabytes) for the mailbox items that have been migrated to the Exchange Online mailbox. This number includes items migrated in both the initial and incremental synchronizations. This field doesn't have a value for IMAP migrations. The average transfer rate (in bytes or MB per minute) of data copied to the Exchange Online mailbox. This field doesn't have a value for IMAP migrations. If the migration for the user failed, this field displays a description of the error. This error description is also included in the Migration Errors report. Click Download the report for this user to open or save a detailed migration report that contains diagnostic information about the migration status of the user. You or Microsoft Support can use the information in this report to troubleshoot failed migrations. The last time that any new items in the on-premises mailbox were copied to the cloud-based mailbox. 25

26 Click More details to display the following additional information about the selected migration user. Field Queued duration In-progress duration Synced duration Stalled duration Description The length of time the user had a status of Queued. The length of time the user was actively being migrated. The length of time the migration user had a status of Synced. The length of time the migration process was stalled for the user. You also can use the remote Windows PowerShell in your Exchange Online Dedicated environment to display migration user statistics using the Get-MigrationUser and Get-MigrationUserStatistics cmdlets. Within the Exchange Online Dedicated environment, you must be a member of one of the role groups that provides access to these cmdlets. To locate the role groups, search for the Get-MigrationUser and the Get-MigrationUserStatistics cmdlets within the Self-Service Administration content held within the Exchange 2013 Platform Readiness area of the Customer Extranet site for additional information. Migration phases To help you understand the migration status states described in the previous sections, it s helpful to be familiar with the phases of the migration process. The following table describes these phases and indicates whether the phase is included in each type of migration. Migration phase Hybrid Exchange migration Initial synchronization The migration process migrates mailbox items to the newly cloud-based mailboxes. Incremental synchronization - The migration process synchronizes the on-premises mailbox and the corresponding Exchange Online mailbox every 24 hours. Yes (includes calendar times and contacts) Yes 26