A local mailbox move in Exchange 2013 fails with the error that the System Attendant Mailbox cannot be opened. I thought System Attendant was a thing of. Arbitration or system mailboxes in Exchange could be missing or corrupted during migration, causing many issues like restriction in local movement of mailboxes. We have discussed the manual solution for recreating the Exchange arbitration mailboxes using Exchange Management Shell cmdlets.
If the dabase is deleted where the System attendant (SA) i placed, Microsoft has a fine article for Re homing the SA mailbox, in Exchange 2007.The article called 'The System Attendant homeMDB attribute is missing' is here:
http://technet.microsoft.com/en-us/library/dd535374(EXCHG.80).aspx
It's a refference from the Best practise analyzer which will tell if there's a server where the SA is missing a homemdb value.
But I havent found an article for Exchange2010, where the path to the databases are slightly different.
In Adsi Edit you should instead use this path:
- Configuration [
Domaincontroller.contoso.com] - CN=Configuration,DC=contoso,DC=com
- CN=Services
- CN=Microsoft Exchange
- CN=
- CN=Administrative Groups
- CN=Exchange Administrative Group (
ID) - CN=Databases
The new path is is obviously because the Storage groups are gone in Exchange 2010, and the databases are now global instead of dedicated to a server.