You are on page 1of 3

Move arbitration mailbox

Estimated time to complete: 10 minutes


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 2013 into an existing Exchange 2010
organization, you need to move the arbitration mailbox to an Exchange 2013
Mailbox server. If you don't move the arbitration mailbox, Exchange 2013 cmdlets
that are run won't be logged in the administrator audit log and eDiscovery searches
run on Exchange 2013 servers will be queued but won't start.

How do I do this?
1. In the EAC, go to Recipients > Migration.
2. Click New

, and then click Move to a different database.

3. On the New local mailbox move page, click Select the users that you
want to move, and then click Add .
4. On the Select Mailbox page, add the mailbox that has the following
properties:
o

The display name is Microsoft Exchange.

The alias of the mailboxs email address is


SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}.

5. Click OK, and then click Next.


6. On the Move configuration page, type the name of the migration batch,
and then click Browse next to the Target database box.
7. On the Select Mailbox Database page, add the mailbox database to move
the system mailbox to. Verify that the version of the mailbox database that
you select is Version 15. x, which indicates that the database is located on an
Exchange 2013 server.
8. Click OK, and then click Next.
9. On the Start the batch page, select the options to automatically start and
complete the migration request, and then click New.

How do I know this worked?

To verify that youve successfully moved the Microsoft Exchange system mailbox to
a mailbox database located on an Exchange 2013 server, run the following
command in the Shell.

Get-Mailbox -Arbitration -Identity "SystemMailbox{e0dc1c29-89c3-4034-b678e6c29d823ed9}" | FL Database,ServerName,AdminDisplayVersion


If the value of the AdminDisplayVersion property is Version 15.x (Build xxx.x),
this verifies that the system mailbox resides on a mailbox database that is located
on an Exchange 2013 server.
After you move the Microsoft Exchange system mailbox to Exchange 2013, youll
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 using the EAC or the Shell
in Exchange 2013.

Remove Exchange 2010 External URLs


The Exchange 2010 primary site at CBTS will be switched from an Internet facing
site to a non-Internet facing site. To make this change the external URL properties of
the CAS virtual directories on the Exchange 2010 servers in CBTS need to be set to
NULL. The below PowerShell cmdlets need to be run for the following servers:
NAWINCBTMXC
001
NAWINCBTMXC
002
NAWINCBTMXC
003
NAWINCBTMXC
004
Get-OwaVirtualDirectory Server <servername> |Set-OwaVirtualDirectory ExternalUrl $NULL
Get-EcpVirtualDirectory Server <servername> |Set-EcpVirtualDirectory ExternalUrl $NULL
Get-ActiveSyncVirtualDirectory Server <servername> |Set-ActiveSyncVirtualDirectory ExternalUrl
$NULL
Get-WebservicesVirtualDirectory Server <servername> |Set-WebServicesVirtualDirectory
ExternalUrl $NULL
Get-OABVirtualDirectory Server <servername> |Set-OABVirtualDirectory ExternalUrl $NULL

Configure DNS records


Estimated time to complete: 15 to 20 minutes
Important:
Before you make any changes to your DNS records, we strongly recommend that
you reduce the time to live (TTL) values of each DNS record you want to change to
its minimum interval. The TTL value determines how long a DNS record stays
cached on DNS servers. A smaller interval, such as 5 or 10 minutes, will allow you
to reverse any changes faster in the event you need to revert back to your original
configuration. If you do need to change the TTL of your DNS records, don't make
any other changes until the original TTL interval has passed.
You might need to make changes to your firewall to support the new Exchange 2013
server. You might need to add new firewall rules, add an external IP address for your
Exchange 2013 server, or make other configuration changes. If your organization
has a network management group, a security review process, or change
management process, you may need to request permission to perform these
changes or have someone else make them for you.
Now that you've configured your Exchange 2010 and Exchange 2013 servers, it's
time to change your DNS records to direct connections to your new Exchange 2013
server. You'll move the host names (for example, mail.contoso.com) users have
been using to connect to Outlook Web Access, Autodiscover, and so on, from your
Exchange 2010 server to your Exchange 2013 server. When an Exchange 2010 user
tries to open their mailbox, the Exchange 2013 server will proxy their request and
communicate with the Exchange 2010 server on their behalf. Configuring DNS
includes the following:

Change the primary host names, such as mail.contoso.com,


autodiscover.contoso.com, and owa.contoso.com (if used) to point to the
external, publically-accessible, IP address of the Exchange 2013 Client Access
server with your public DNS provider.

Change the primary host names, such as mail.contoso.com (or


internal.contoso.com if you're using different internal host names) and
owa.contoso.com (if used) to point to the internal load balanced VIP of the
Exchange 2013 Client Access server on your internal DNS servers.