Also, keep in mind the logging for the Database where the migration mailbox resides. If you are doing a lot of moves, the logs will start to increase. So Either plan your moves in between backups to flush the transaction logs of the DB that holds the migration mailbox, or set Circular logging on the DB that holds the migration mailbox.
-->Exchange Server contains five special system mailboxes known as arbitration mailboxes. Arbitration mailboxes are used for storing different types of system data and for managing messaging approval workflow. The following table lists each type of arbitration mailbox and their responsibilities.
Arbitration mailbox Name | Display name | Persisted capabilities | Function |
---|---|---|---|
FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 | Microsoft Exchange Federation Mailbox | none | This mailbox stores data used to maintain federation between different Exchange organizations. This includes Rights Management Services, cross-premises mail-flow monitoring probes and responses, notifications, online archives, messaging records management, and cross-premises free/busy information. |
Migration.8f3e7716-2011-43e4-96b1-aba62d229136 | Microsoft Exchange Migration | Management | Stores data for the Exchange migration service to use when moving mailboxes in batches. |
SystemMailbox{1f05a927-XXXX-XXXX-XXXX-XXXXXXXXXXXX} (for example, SystemMailbox{1f05a927-9350-4efe-a823-5529c2d64109}; most of the mailbox name is unique to your organization) | Microsoft Exchange Approval Assistant | none | This mailbox is provisioned for use by the Exchange approval framework for recipient moderation and auto group approval requests. |
SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} | Microsoft Exchange | ClientExtensions GMGen MailRouting MessageTracking OABGen PstProvider UMGrammar UMGrammarReady (Exchange 2016 only) | This is known as an organization mailbox. It is used for creating offline address books (OABs). To load-balance OAB generation across your organization, including across geographically separate sites, you can create additional organization mailboxes. |
SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} | Microsoft Exchange | UMDataStorage | Discovery system mailbox. Provisioned for use by the e-Discovery feature, which is used by compliance officers to locate messages that match specified selection criteria. This mailbox is also used by Unified Messaging in Exchange 2016 for storing UM console attending files and other information. |
If you need to re-create one of more of these arbitration mailboxes, see the instructions that follow.
What do you need to know before you begin?
- Estimated time to complete: 10 minutes per procedure.
- You need to be assigned permissions before you can perform these procedures. To see what permissions you need, see the 'Recipient Provisioning Permissions' section in the Recipients Permissions topic.
- To run
Setup.exe /PrepareAD
, your account needs to be a member of the Enterprise Admins security group. - The computer that you use to run
Setup.exe /PrepareAD
requires access to Setup.exe in the Exchange installation files:- Use your most recently downloaded copy of the Exchange ISO image file, or download an updated copy from Updates for Exchange Server.
- In File Explorer, right-click on the Exchange ISO image file and then select Mount. Note the virtual DVD drive letter that's assigned.
- Open a Windows Command Prompt window. For example:
- Press the Windows key + 'R' to open the Run dialog, type cmd.exe, and then press OK.
- Press Start. In the Search box, type Command Prompt, then in the list of results, select Command Prompt.
- For more information about opening the Exchange Management Shell, see Open the Exchange Management Shell.
- For more information about running Exchange Setup in unattended mode, see Use unattended mode in Exchange Setup.
Re-create an arbitration mailbox
Use the following instructions to re-create a particular type of arbitration mailbox.
Re-create the Microsoft Exchange Federation Mailbox
To re-create the arbitration mailbox FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042, run the following commands:
- If the mailbox is missing, run the following command from a Windows Command Prompt window:For example:
- In the Exchange Management Shell, run the following command:
Re-create the Microsoft Exchange Migration mailbox
To re-create the arbitration mailbox Migration.8f3e7716-2011-43e4-96b1-aba62d229136, run the following commands:
- If the mailbox is missing, run the following command from a Windows Command Prompt window:For example:
- In the Exchange Management shell, run the following command:
- In the Exchange Management Shell, set the Persisted Capabilities (msExchCapabilityIdentifiers) for the mailbox by running the following command:
![Microsoft Microsoft](http://msexchangeteam.in/wp-content/uploads/wp-content/uploads/2013/02/image_thumb9.png)
Re-create the Microsoft Exchange Approval Assistant mailbox
To re-create the arbitration mailbox SystemMailbox{1f05a927-XXXX-XXXX-XXXX-XXXXXXXXXXXX}, run the following commands:
- If the mailbox is missing, run the following command from a Windows Command Prompt window:For example:
- In the Exchange Management Shell, run the following command:
Re-create the Microsoft Exchange organization mailbox for OABs
To re-create the arbitration mailbox SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}, run the following commands:
- If the mailbox is missing, run the following command from a Windows Command Prompt window:For example:
- In the Exchange Management Shell, run the following command:
- In the Exchange Management Shell, set the Persisted Capabilities (msExchCapabilityIdentifiers) for the mailbox by running the following command:
- In the Exchange Management Shell, add the required capabilities to the mailbox by running the following commands:
Re-create the Microsoft Exchange Discovery system mailbox
To re-create the arbitration mailbox SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}, run the following commands:
- If the mailbox is missing, run the following command from a Windows Command Prompt window:For example:
- In the Exchange Management shell, run the following command:
- In the Exchange Management Shell, set the Persisted Capabilities (msExchCapabilityIdentifiers) for the mailbox by running the following command:
Re-create the Microsoft Exchange 2016 CU8 and later system mailboxes
To re-create the arbitration mailbox SystemMailbox{D0E409A0-AF9B-4720-92FE-AAC869B0D201} and SystemMailbox{2CE34405-31BE-455D-89D7-A7C7DA7A0DAA}, run the following commands:
- If the mailboxes are missing, run the following command from a Windows Command Prompt window:For example:
- In the Exchange Management shell, run the following command:
- In the Exchange Management Shell, set the Persisted Capabilities (msExchCapabilityIdentifiers) for the mailbox by running the following command:
How do you know this worked?
To verify that you've successfully re-created the arbitration mailbox, set the search scope to search the entire Active Directory forest, an then use the Get-Mailbox cmdlet with the Arbitration switch to retrieve system mailboxes.
View the results of the command to verify that appropriate system mailbox, either by Name or Display Name from the above table, has been re-created.
Tip
Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server.
-->Applies to: Exchange Server 2013
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. The Microsoft Exchange system mailbox is named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}; the display name is Microsoft Exchange.
When you upgrade your existing Exchange 2010 organization to Exchange 2013, you have to move the Microsoft Exchange system mailbox to a mailbox database on an Exchange 2013 Mailbox server. You should move this mailbox after you've installed and verified Exchange 2013. If you don't move this system mailbox to Exchange 2013, the following issues will occur when Exchange 2010 and Exchange 2013 coexist in your Exchange organization:
- Exchange 2013 tasks aren't saved to the administrator audit log. When you run the Search-AdminAuditLog cmdlet or try to export the administrator audit log in the EAC, you'll receive an error that says you can't create an administrator audit log search because the system mailbox, SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}, is located on a server that isn't running Exchange 2013. A Microsoft Exchange error with an Event ID of 5000 is also logged in the Windows Application log each time a command is run.
- You can't run eDiscovery searches using the EAC or the Shell in Exchange 2013. Mailbox searches can be created and queued, but they can't be started. An error with an Event ID of 6 is logged in the MsExchange Management log, stating that the Start-MailboxSearch cmdlet failed. However, you can search mailboxes using the Shell and the Exchange Control Panel (ECP) in Exchange 2010.
You also have to move the Microsoft Exchange system mailbox to Exchange 2013 as part of upgrading Exchange 2010 Unified Messaging to Exchange 2013.
For more information about upgrading to Exchange 2013, see the following topics:
What do you need to know before you begin?
- Estimated time to complete: 20 minutes. The actual time may vary depending on the size of the system mailbox.
- 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' entry in Recipients Permissions.
- Run the following command in Exchange 2013 to obtain the identity and version of the Exchange servers and mailbox databases that contain the system mailboxes in your organization.The AdminDisplayVersion property indicates the version of Exchange that the server is running. The value
Version 14.x
indicates Exchange 2010; the valueVersion 15.x
indicates Exchange 2013. - For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
Tip
Having problems? Ask for help in the Exchange forums. Visit the forums at Exchange Server.
Use the EAC to move the system mailbox
- In the EAC, go to Recipients > Migration.
- Click New , and then click Move to a different database.
- On the New local mailbox move page, click Select the users that you want to move, and then click Add .
- On the Select Mailbox page, add the mailbox that has the following properties:
- The display name is Microsoft Exchange.
- The alias of the mailbox's email address is SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}.
- Click OK, and then click Next.
- On the Move configuration page, type the name of the migration batch, and then click Browse next to the Target database box.
- 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.
- Click OK, and then click Next.
- On the Start the batch page, select the options to automatically start and complete the migration request, and then click New.
Use the Shell to move the system mailbox
First, run the following command in Exchange 2013 to obtain the names and versions of all mailbox databases in your organization.
After you identify the name of the mailbox databases in your organization, run the following command in Exchange 2013 to move the Microsoft Exchange system mailbox to a mailbox database located on an Exchange 2013 server.
How do you know this worked?
To verify that you've successfully moved the Microsoft Exchange system mailbox to a mailbox database located on an Exchange 2013 server, run the following command in the Shell.
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, 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 using the EAC or the Shell in Exchange 2013.