Use the Shell to re-create the Discovery system mailbox
Use the Shell to re-create the Discovery system mailbox
- Delete the SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} user account from Active Directory, if it exists. By default, Exchange Server 2013 Setup creates the mailbox in the Users container in Active Directory. For details about how to delete a user account from Active Directory, see Delete a User Account.
- Prepare Active Directory by running Microsoft Exchange 2013 (same for Exchange 2010) Setup with the /PrepareAD switch in the root domain of your Active Directory forest. For details, see Prepare Active Directory and Domains. (go to Exchange installation directory then run setup /p)
- Use the Shell to enable the Discovery system mailbox.
Note:You can’t use the EAC to enable the Discovery system mailbox. This example enables the Discovery system mailbox. You must specify the fully qualified domain name (FQDN) of a global catalog server in the root domain of the Active Directory forest.
Enable-Mailbox -Arbitration -DomainController <FQDN of root global catalog server> -Identity "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}"Example:
Enable-Mailbox -Arbitration -DomainController ADVEXCH.mydomain.com -Identity “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}”
To resolve this issue, run the following command from the Exchange Management Shell:
Get-Mailbox -Arbitration and check the validity of the System MailboxSystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} SystemMailbox{1f05a927-af78-475a-aba4-fc281398eb54} FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 DiscoverySearchMailbox{D919BA05-46A6-415f-80AD-7E09334BB852}In this case, two system mailboxes were corrupted:SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} SystemMailbox{1f05a927-af78-475a-aba4-fc281398eb54}So from the ADSIEdit.msc , Domain Naming contextUsers , user deleted the System mailbox and recreated using Setup/ADprep command (Exchange setup).After creating, System mailbox, user needs to enable them. Below is the command to enable them:Enable-Mailbox -Arbitration -Identity “FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042” Enable-Mailbox -Arbitration -Identity “SystemMailbox{1f05a927-8668-4003-adad-9b80758e86db}” Enable-Mailbox -Arbitration -Identity “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}” Enable-Mailbox -Discovery “DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}”And finally, run the following command to set the display name for one System Mailbox and quota for FederatedEmail:Set-Mailbox -Arbitration -Identity “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}” -DisplayName “Microsoft Exchange” Set-Mailbox -Arbitration -Identity “FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042” -ProhibitSendQuota 1MB
Categorised as: Exchange, Microsoft
[…] to verify we had no more issues and no more poison messages were generated. Further Reading Use the Shell to re-create the Discovery system mailbox Recreate Arbitration mailbox in Exchange 2010 – Applies to Exchange 2013 as well. Mail access […]