Share via

How to Recreate System Mailboxes, FederatedEmail and DiscoverySearchMailbox in Exchange 2013

  • Article

As with Exchange Server 2013 CU5 Setup.exe /PrepareAD might not recreate required system mailboxes as described here, when the Exchange organization does have Exchange 2007 Servers, the Exchange 2010 SP3 Schema update, but no Exchange 2010 servers. The Active Directory schema has even been upgraded to Exchange Server 2013 CU5.

During setup of the first Exchange 2013 server setup 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.”.

Because no Exchange 2010 or Exchange 2013 Servers are available you are not able to run an Enable-Mailbox –Arbitration cmdlet.

The following solution is provided AS-IS, because it requires the use of ADSIEdit, which might result in an inconsistent state of Active Directory.

To enable Exchange Server 2010 SP3 setup to execute /PrepareAD it is required to set the schema version value to match Exchange 2010 SP3 or earlier values.

Change the following Active Directory Attribute values (the values shown are Exchange Server 2010 SP2):

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

    rangeUpper = 14732

  • CN=<ExhangeOrg>,CN=Microsoft Exchange,CN=Services,CN=Configuration

    objectVersion = 14322

  • CN=Microsoft Exchange System Objects

    objectVersion = 13040

After modifying the values run Exchange Server 2010 SP3 setup.com /PrepareAD

This creates the missing accounts.

Afterwards run the Exchange Server 2013 CU5 setup using the /PrepareSchema, /PrepareAD and /PrepareDomain (/PrepareAlLDomains) switches.

Enjoy Exchange,

Thomas

Reference Links