Share via

How to Recreate SystemMailbox, FederatedEmail, and DiscoverySearchMailbox in Exchange 2013

  • Article

The re-creation of corrupted or missing arbitration mailboxes has already been described here. The solution assumes that an Exchange server is available the is capable of executing an Enable-Mailbox –Arbitration cmdlet.

The situation encountered with Exchange Server 2013 in this situation is different:

  • Exchange servers are member servers of an AD child domain
  • Exchange Server 2007 in use
  • Exchange Server 2010 schema applied, but no Exchange 2010 deployed in VARUNA Exchange organization
  • Exchange Server 2013 schema applied
  • Deployed Exchange 2013 serves got removed and/or installed from Active Directory
  • No exisiting Exchange 2013 server in the VARUNA Exchange organization

Setup for a new Exchange 2013 Server fails with the following error:

The following error was generated when “$error.Clear();

 

if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )

 

{

 

Update-RmsSharedIdentity -ServerName $RoleNetBIOSName

 

}

 

” was run: “RMS Shared Identity user FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 not found.”.

 

It seemed to be corrupted and got deleted by an administrator as described here.

Running Exchanger Server 2013 CU5 setup using /PrepareAD did re-created the SystemMailbox and DiscoveryMailbox accounts but not the required FederatedEmail account in the root domain.

The fact that the documentation available in regards to the re-creating the FederatedEmail account was only referring to Exchange Server 2010, the idea was born to run the Exchange Server 2010 setup.com /PrepareAD command.

Because the Exchange Server 2013 CU5 schema update had already been applied to Active Directory, the version information needed to be set to Exchange Server 2010 SP3 or earlier.

The information for the following changes is provided AS-IS, as it requires the use of ADSIEdit. The use of ADSIEdit can result in an inconsistent state of your Active Directory.

The following version information has been changed to make Exchange 2010 setup.com believe it can be executed in the AD environment.

Change the follow AD attributes in the schema, domain and configuration context of Active Directory:

  • CN=ms-Exch-Schema-Version-Pt,cn=schema,cn=configuration

     

    rangeUpper = 14732

     

  • CN=,CN=Microsoft Exchange,CN=Services,CN=Configuration

     

    objectVersion = 14322

     

  • CN=Microsoft Exchange System Objects

     

    objectVersion = 13040

The values provided set the version to Exchange Server 2010 SP2.

After executing Exchange Server 2010 SP3 setup.com /PrepareAD the missing FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 account had been created.

To ensure that all required Exchange Server 2013 CU5 changes are available in Active Directory, the required prerequistes for Exchange Server 2013 CU5 had been executed as well:

  • Setup.exe /PrepareSchema
  • Setup.exe /PrepareAD
  • Setup.exe /PrepareAll Domains (or /PrepareDomain in a single domain environment)

Enjoy Exchange,

 

Thomas Stensitzki

 

Reference Links

FederatedEmail Arbitration Mailbox Account Not Created By PrepareAD, http://www.sf-tools.net/Messaging/tabid/55/EntryId/209/FederatedEmail-Arbitration-Mailbox-Account-Not-Created-By-PrepareAD.aspx

 

How to recreate System Mailbox , FederatedEmail & DiscoverySearchMailbox in Exchange 2010, http://bit.ly/RecreateSystemMailboxes

 

Prepare Active Directory and domains, http://bit.ly/PrepareADforExchange2013