With an Exchange-based hybrid deployment, you can choose to either move on-premises Exchange mailboxes to the Exchange Online organization or move Exchange Online mailboxes to the Exchange organization. When you move mailboxes between the on-premises and Exchange Online organizations, you use migration batches to perform the remote mailbox move request. This approach allows you to move existing mailboxes instead of creating new user mailboxes and importing user information. This approach is different than migrating user mailboxes from an on-premises Exchange organization to Exchange Online as part of a complete Exchange migration to the cloud. The mailbox moves discussed in this topic are part of administrative Exchange management in a longer-term coexistence relationship between on-premises Exchange and Exchange Online organizations.
What do you need
to know before you begin?
·
Estimated time to complete: 10 minutes to configure the migration
batch, but total time to complete the migration depends on the number of
mailboxes included in each migration batch.
·
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.
·
Hybrid deployment is configured between your on-premises and
Exchange Online organizations.
·
If you're running Exchange 2013, make sure the Mailbox Replication
Proxy Service (MRSProxy) is enabled on your on-premises Exchange 2013 Client
Access servers.
Step 1: Create a
migration endpoint
Prior to performing on-boarding and off-boarding remote move
migrations in an Exchange hybrid deployment, we recommend that you create
Exchange remote migration endpoints. The migration endpoint contains the
connection settings for an on-premises Exchange server that is running the MRS
proxy service, which is required to perform remote move migrations to and from
Exchange Online.
Step 2: Enable the
MRSProxy service
If the MRSProxy service isn't already enabled for your on premises
Exchange 2013 Client Access servers, follow these steps in the Exchange admin
center (EAC):
1. Open the
EAC, and then navigate to Servers > Virtual Directories.
2. Select the
Client Access server, and then select the EWS virtual directory and click Edit.
3. Select
the MRS Proxy enabled check
box, and then click Save.
Step 3: Use the
EAC to move mailboxes
You can use the remote move migration wizard on the Office 365 tab in
the EAC on an Exchange server 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. Choose one of the
following procedures:
Move on-premises
mailboxes to Exchange Online
You can use the remote move migration wizard on the Office 365 tab in
the EAC on an Exchange server to move existing user mailboxes in the
on-premises organization to the Exchange Online organization. Follow these
steps:
1. Open the
EAC, and then navigate to Office
365 > Recipients > Migration.
2. Click Add, and then
select Migrate to
Exchange Online.
3. On
the Select a
migration type page, select Remote move migration and
then click Next.
4. On
the Select the users page,
click Add and
select the on-premises users to move to Office 365 and click Add and then
click OK.
Click Next.
5. On
the Enter the Windows
user account credential page, 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.
6. On
the Confirm the
migration endpoint page, verify that the FQDN of your on-premises
Exchange server is listed when the wizard confirms the migration endpoint. For
example, "mail.contoso.com". Click Next.
Note
The MRSProxy service on the
Exchange 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 MRSProxy. To learn more
about customizing the MRSProxy, see Message
Throttling.
7. 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.
In most hybrid deployments, this is the primary SMTP domain used for the
Exchange Online organization mailboxes. For example,
contoso.mail.onmicrosoft.com. Verify that the Move primary mailbox along with archive
mailbox option is selected, and then click Next.
8. On
the Start the batch page,
select at least one recipient to receive the batch complete report. Verify that
the Automatically
start the batch option is selected, and then select
the Automatically
complete the migration batch check box. Click New.
Note
If you select Manual Complete the batch in
step 8,
Exchange Online will only synchronize 95% of each mailbox in that batch.
Exchange Online will periodically synchronize the batch to keep each mailbox at
95% synchronization until the batch is manually completed by clicking the Complete this migration batch,
at which point the remaining 5% is migrated.
Move Exchange
Online mailboxes to the on-premises organization
You can use the remote move migration wizard on the Office 365 tab in
the EAC on an Exchange server to move existing user mailboxes in the
on-premises organization to the Exchange Online organization:
1. Open the
EAC and navigate to Office
365 > Recipients > migration.
2. Click Add, and then
select Migrate from
Exchange Online.
3. On
the Select the users page,
select Select the
users that you want to move and then click Next.
4. On
the Select the users page,
click Add and
then select the Exchange Online users to move to the on-premises organization,
click Add and
then click OK.
Click Next.
5. On
the Confirm the
migration endpoint page, verify that the FQDN of your
on-premises Exchange server is listed when the wizard confirms the migration
endpoint. For example, "mail.contoso.com". Click Next.
Note
The MRSProxy service on the
Exchange 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 properties of the MRSProxy. To learn more
about customizing the MRSProxy, see Message
Throttling.
6. On
the Move
configuration page, enter a name for the migration batch
in the New migration
batch name text field. Then enter the target delivery
domain in the Target
delivery domain for the mailboxes that are migrating to Office 365 field.
In most hybrid deployments, this is the primary SMTP domain used for both
on-premises and Exchange Online organization mailboxes. For example,
contoso.com.
7. Choose
whether to also move the archive mailbox for the selected user and enter the
database name you'd like to move this mailbox to in the Target database text
field. For example, Mailbox Database 123456789. Click Next.
8. On
the Start the batch page,
select at least one recipient to receive the batch complete report. Verify
that Automatically
start the batch is selected, and then select the Automatically complete the migration
batch check box. Click New.
Step 4: Remove
completed migration batches
After your mailbox moves have completed, we recommend removing 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 > Recipients > Migrations.
2. Click a
completed migration batch, and then click Delete.
3. On the
deletion warning confirmation dialog, click Yes.
Step 5: Re-enable
offline access for Outlook on the web
Offline access in Outlook on the web (formerly called Outlook Web
App) lets users access their mailbox when they're not connected to a network.
If you migrate Exchange mailboxes to Exchange Online, users have to reset the
offline access setting in their browser to use Outlook on the web offline. For
more information about offline access in Outlook on the web, the browsers that
support it, and how to turn it on, see Using Outlook Web App
offline.
How do you know
this worked?
When you move existing user mailboxes between the on-premises and
Exchange Online organizations, the successful completion of the remote move
wizard will be your first indication that moving the mailbox will complete as
expected.
Because the
mailbox move process takes several minutes to complete, you can also verify
that the move is working correctly by opening the EAC and selecting Office 365 > Recipients > Migration to
display the move status for the mailboxes selected in the remote move wizard.
The value of the Status is Syncing during the
mailbox move, and it's completed when
the mailbox has successfully moved to either the on-premises or Exchange Online
organization.
After the
mailbox move has completed, you can check that the remote mailbox located on
the on-premises or Exchange Online organization has been successfully moved by
verifying the mailbox properties. To do this, navigate to Recipients > Mailboxes in the EAC
for either the on-premises organization or Exchange Online organization. The
user mailbox should show a Mailbox
Type of Office
365 for Exchange Online mailboxes and User for
on-premises mailboxes.
No comments:
Post a Comment