Move Arbitration mailbox and delete the default database in Exchange Server 2010

After you install a new Exchange 2010 server for mailbox role, it created a default mailbox database with some database ID as suffix.

The name of the database could be something as “Mailbox Database 1514210160”.

This default database contains Arbitration Mailboxes which are not directly visible through Exchange Management Console. The arbitration mailbox is used to store the original message that’s awaiting approval.

By default, one arbitration mailbox is created for moderated transport during setup. It’s used for all moderated recipients.

The list of Arbitration Mailboxes is:

· Microsoft Exchange Approval Assistant

· Microsoft Exchange

· Discovery Search Mailbox

· Microsoft Exchange Federation Mailbox

In case you want to remove this default mailbox database, you will need to first move the arbitration mailboxes to another database and this has to be done through EMS.

Remove Default Database


I hope the above screenshot is self-explanatory and easy to understand. Please let me know through comments if walkthrough guide is required.

Cheers and more posts to follow Smile


“The type initializer for ‘InstanceContext’ threw an exception.” during the installation of Exchange 2007/2010 server

When you try to install Exchange 2007/2010 on a brand new server or virtual machine running Windows Server 2008 operating systems, it throws the following exception when it tries to check the prerequisites installed.

The type initializer for ‘InstanceContext’ threw an exception.

The type initializer for 'InstanceContext' threw an exception.InstanceContext Exception error screenshot

In normal scenarios, you’ll never find this exception occurring. To resolve the issue, you have to make sure that the hostname of the server does not exceed 15 characters which is default limit for NetBIOS name resolution.

If the hostname of the servers is more than 15 characters, you will have to perform the following steps:

  1. Quit the Exchange setup.
  2. Remove the machine from the domain.
  3. Remove few characters from the hostname of the server
  4. Re-add the server to the domain.
  5. Re-run the setup.

This will resolve the issue and the setup will continue without any error.