Part 6: Exchange 2010 to Exchange 2016 Migration-Mailboxes Move

In this Part 6 Article, We will see how to move Arbitration mailboxes to Exchange 2016

If you would like to read the part 1 in this article series please go to Exchange 2010 to Exchange 2016 Migration -Part 1: AD Installation

If you would like to read the part 2 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 2: Exchange 2010 Installation and configuration 

If you would like to read the part 3 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 3: Exchange 2010 DAG and outlook Anywhere Configuration

If you would like to read the part 4 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 4: Exchange 2016 Installation 

If you would like to read the part 5 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 5: Exchange 2016 Configuration 

In Exchange 2010, the Microsoft Exchange system mailbox is an arbitration mailbox used to store organization-wide data such as administrator audit logs, metadata for eDiscovery searches, and Unified Messaging data such as menus, dial plans, and custom greetings. When you install Exchange 2016 into an existing Exchange 2010 organization, you need to move the arbitration mailbox to an Exchange 2016 server. If you don’t move the arbitration mailbox, Exchange 2016 cmdlets that are run won’t be logged in the administrator audit log, and eDiscovery searches run on Exchange 2016 servers will be queued but won’t start.

Open Exchange admin center-->Recipients–>Click on migration 

1

Click on Move to a different database

2

Select the users that you want to move and click on Add

3

Select the arbitration Mailboxes which are being hosted from Exchange 2010 and click on Add 

4 5

Click on Next

6

Enter the New Migration batch name and browse to select the target database

7

Select the Database of the Exchange 2016 and click on Add

8

Enter the Bad item limit and click on Next

9

add the reporting notification recipient  and click on New

10

You can see the migration status

11

After you moved the Microsoft Exchange system mailbox to Exchange 2016, you’ll also be able to successfully perform the following administrative tasks:

  • Run the Search-AdminAuditLog cmdlet.
  • Export the administrator audit log in the EAC.
  • Successfully create and start eDiscovery searches by using the EAC or the Shell in Exchange 2016.

If you would like to read the part 1 in this article series please go to Exchange 2010 to Exchange 2016 Migration -Part 1: AD Installation

If you would like to read the part 2 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 2: Exchange 2010 Installation and configuration

If you would like to read the part 3 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 3: Exchange 2010 DAG and outlook Anywhere Configuration

If you would like to read the part 4 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 4: Exchange 2016 Installation

If you would like to read the part 5 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 5: Exchange 2016 Configuration 

Author Bio

Radhakrishnan Govindan

5 thoughts on “Part 6: Exchange 2010 to Exchange 2016 Migration-Mailboxes Move”

  1. Hi,
    Thanks for sharing this article.
    I have a question regarding the migration- Will the user be able to send/receive emails while the migration is in process?

    Thanks.

  2. Our mailboxes say “complete” but remain in their original database.

    2010=>2016

    FIRST mailbox moved fine. One new guy also moved. The rest… stuck.
    No error messages; say ‘complete’. But nada.

Leave a Reply

Your email address will not be published. Required fields are marked *