Oct 14, 2007  Posts: 2 Joined: 12.Oct.2007 Status: offline I have discovered that my System Attendant mailbox is gone (Exchange 2003 sp2/ Win 2k3 SP2) and it seems to have been gone for a few weeks. Singers unlimited a capella ii.

I thought that system attendant is part of the past till today when I had a call with one customer. Windows 7 all editions download. He was trying to move a mailbox between two exchange 2013 servers and the move request fails immediately with error 'Cannot open mailbox /o=Test Lab/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MY2013Server/cn=Microsoft System Attendant' If you look at any exchange 2013 mailbox server you won’t find the famous “Microsoft Exchange System Attendant” service. In the past this service used to handle many tasks, for example, it used to handle the offline address book generation and the mailbox move.

The new architecture for exchange 2013 depends in a new arbitration mailbox “Migration.8f3e7716-2011-43e4-96b1-aba62d229136” for mailbox move. Knowing the architecture changes I decided to consider this error misleading and investigate the migration mailbox issue. I found that the Migration mailbox is hosted in an offline database which is no more available due to a server crash The solution was to recreate the mailbox again, so I first started to delete the AD object and run Setup.exe/PrepareAD to recreate the AD object again. I’ve to run two more commands to mailbox enable the new AD object and to set the parameter management equal $true Enable - Mailbox - Arbitration - Identity 'Migration.8f3e7716-2011-43e4-96b1-aba62d229136' AND Set - Mailbox 'Migration.8f3e7716-2011-43e4-96b1-aba62d229136' - Arbitration – Management: $true Move started to work and we are all happy. Good morning, When i run the first command i get this: This task does not support recipients of this type. The specified recipient everest.nl/Users/Migration.8f3e7716-2011-43 e4-96b1-aba62d229136 is of type UserMailbox. Please make sure that this recipient matches the required recipient type f or this task.

And that is after we did the setup /preparead command ofcourse. We accidentally deleted the mailbox database on our passive server. The database which gets created during the install of exchange.

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: 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.