43 Responses to Recreate and enable missing arbitration user accounts and mailboxes in Exchange Server 2010

  1. Paul says:

    Hi I recreated the Active Directory accounts using the setup /PrepareAD as in your Web Page but when I try and create the mailboxes it fails.

    I get the following error:

    The operation couldn’t be performed because object ‘FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042’ couldn’t be found on “ourchild.domain.local”

    The Exchange Servers are all in the child domain. Do you know what is wrong? It seems to be looking for the account in the child domain and not the root domain.

    Any help would be greatly appreciated.

    Thanks,

    Paul

  2. Paul says:

    Ah found what was wrong needed to change the scope to look at the whole forest.

    • msundis says:

      Great to hear that you solved it on you own, thanks for posting back with the answer!

  3. Alan McBurney says:

    Superb article. Saved me a bucket load of time and research in recreting the arbitaion accounts after a DR situation with a customer.

    Many thanks.

  4. Pingback: Recreate arbitration accounts in Exchange 2010 « Alan's sysadmin Blog

  5. Brad says:

    Great article, but getting the error: The user’s Active Directory account must be logon-disabled for linked, shared, or resource mailbox. The accounts are locked and disabled.

  6. Jose Byron Gonzalez says:

    Outstanding work! I was ready to commit harakiri….. so now I am getting this long message:

    “This task does not support recipients of this type. The specified recipient pennyxxxx.org/Users/SystemMailbox{1f05a927-e1a6-4713-8a8f-e2cd53bacd2 is of type UserMailbox. Please make sure that this recipient matches the required recipient type for this task….”

    It also tells me (when I run [get-mailbox -arbitration]): “The object xxyy has been corrupted and is in an inconsistent state. The following validation errors happened: Database is mandatory on UserMailbox.”

    Thanks so much for ANY help!

    • msundis says:

      Hi Jose and thanks for reading. I would recommend you to delete that specific mailbox and recreate it. Have you tried that already?

  7. SupaTrupa says:

    Nice, thank you, your howto helped me out

  8. Thanks, saved me a lot of time after I had reinstalled the OS for a test Exchange box without deleting the FederatedEmail and SystemMailbox mailboxes.

  9. JBrady says:

    Fantastic Article!!!!!!!!!!!!! One addition, not only did I have to target -DomainController xx due to having multiple domains, I also had to delete my existing “SystemMailboxes” in order to recreate them and enable them.

    Symptom, when running the “enable” command you get this error:
    This task does not support recipients of this type. The specified recipient domain.com/Users/SystemMailbox{e
    0dc1c29-89c3-4034-b678-e6c29d823ed9} is of type UserMailbox. Please make sure that this recipient matches the required
    recipient type for this task.

    SystemMailbox account did exist in AD, had to delete it and run setup /PrepareAD for the “Enable” command to work

    • msundis says:

      Hi and thanks for reading!

      Nice to hear that you solved it and thanks for sharing your findings and experience.

  10. Jonas says:

    Hi Martin,

    Nice article there!
    great sharing

  11. Great Job, Worked like a champ.

  12. Sherrie says:

    Hi, I have only 2 of the 3 accounts listed in AD, and when trying to enable them am receiving: “This task does not support recipients of this type. The specified recipient SystemMailbox{xxxxxxxx} is of type UserMailbox. Please make sure that this recipient matches the required recipient type for this task….”

    It also tells me (when I run [get-mailbox -arbitration]): “The object xxyy has been corrupted and is in an inconsistent state. The following validation errors happened: Database is mandatory on UserMailbox.”

    You mentioned they should be deleted and recreated. Do you mean just delete the objects in AD and then run
    “setup.com /PrepareAD”?

    By the way, I did try running this command today and it said something about a reboot pending from a previous install. Is it safe to our current Exchange setup to reboot it and run the PrepareAD command?

    Many thanks for a helpful article.

    • msundis says:

      Hi,

      Yes, what I mean is that you can just delete the mailboxes and user accounts and then run setup.com /PrepareAD. This will recreate the user accounts and then you can enable the mailboxes.

      If it says you have got a pending reboot that is what you should do. My guess is that you have a previous installation done that is not related to this issue. But you will have to restart the server anyway to be able to run the setup.com /PrepareAD command.

      Give that a try and get back to me if it doesn’t solve your problem!

      Thanks for reading!

      • Sherrie says:

        Awesome, worked great! Thanks so much. I am now confident that my Exchange environment is fully functional. Thanks for an informative article.

      • msundis says:

        No worries Sherrie, Just glad you find it usefull. Thanks for reading and commenting :)

  13. MBW says:

    Created a new database as the archive bit wasn’t resetting after a successful backup. Couldn’t move the FederatedEmail mailbox over to the new database at the final step. Ended up deleting the FederatedEmail user from AD, ran setup /PrepareAD, enabled FederatedEmail mailbox per instructions above, was able to move the FederatedEmail mailbox after that, set quota and then was able to delete old database.

  14. Ed says:

    Hi, I dismount the database, and delete everything (log, .edb file) before removing the database from DAG. I now see the old DB is still existing even no .edb exists. I cannot re-mount the DB, remove the DB(there are arbitration mailbox still attached for some reason)…basically nothing i can do. Running the command “get-mailbox -arbitration”, those 3 entries are still showing. However, i cannot move the mailbox to other DB since I have deleted the .edb already. Can I just mail-enable to user account on another DB? Any advise? Thanks.

    Ed

    • msundis says:

      Hi Ed,

      You should be able to remove the database using ADSIEdit.

      In ADSIEdit,
      1. Connect to the Configuration context
      2. Navigate to Services / Microsoft Exchange / / Administrative Groups / Exchange Administrative Group (FYDIBOHF23SPDLT) / Databases
      3. Delete the failed database

      To rehome the mailboxes that recides in the failed database use the following command:
      Get-Mailbox -Database | Set-Mailbox -Database

      • Ed says:

        thx for the reply, actually i have fixed it by using the command Set-mailbox to relocate the arbitration mailboxes. then I can sucessfully remove the DB via EMC.

      • msundis says:

        Excellent, nice to hear that you solved it. Thanks for posting you solution!

  15. Markus says:

    I solved the problem of a deleted discoverymailboxuser by undeleting the account in AD. The tombstone live time was not over, so this was the quickest option.
    http://www.petri.co.il/recovering-deleted-items-active-directory.htm
    After that, you might have to reassociate the discovery mailbox to the restored user or recreate the mailboxes:
    http://mostlyexchange.blogspot.com/2011/12/exchange-2010-sp2-upgrade-issue-with.html

    hth,
    Markus

  16. X-Tremis says:

    Awesome article! Used it to “recreate” the arbitration mailboxes that were on a corrupted database. Very nice! :)

    • Martin Sundström says:

      Great to hear that you found it helpfull, thanks for reading and commenting!

  17. AHMAD K. says:

    For ME the issues that you must consider once you want to upgrade to any SP’s for exchange 2010.
    1- extract 2010 SP2 to use as run setup /PrepareSchema, /PrepareAD etc…, also my exchange server 2010 all of it was crashed and the AD was missed everything, however i tried to to get
    back to the same AD , they said use another , but after my own conclusion, you only need
    to returen the commands for the exchange on the active directory but be aware first which the latest sp you have SP1, SP2 . and use the setup file for the one you already have.

    Also i got error about things for federation could not found as some of members said , or Display R5 from R4, and that some mailbox once you recieved the mailbox role.

    Ok so what i want to say is as follow:
    1- First if your EX server was smashed crashed what ever happy, just get the database
    and what you need.

    2- you dont have to create another new DC with new AD , you just need to do the following.
    – Delete the mailbox all federation, displaysearch , both systemmailbox.
    – then run the from the setup files the same verion you have. so
    * if you have the first version of EX , use the same file, iso, dvd what ever.
    * if you have already ex with SP1 use the extracted files setup from SP1 to run the
    common commands, setup /prepareAD /organizationName:your netbios name
    * if you want to upgrade from SP1 to SP2 , just get the extracted files from SP2
    and run the commands as follow and as i mension exactly.
    – Setup /PrepareLegacyExchangePermission
    will prepare exchange for SP2 installation.
    will Prepare permission, values.
    – Setup /PrepareSchema
    – Setup /PrepareAD /OrganizationName: your domain name “netbios Name”.
    this will prepare for you the Organization in the domain controller and if you have
    any missing object there will be recreated such the mailboxes that you delete in
    above steps. “federation, sysmailbox , displaysearchmailbox “.

    Finally , from my little experiance is to install the fresh DVD from microsoft then update ur
    EX with SP2.

  18. Humberto It says:

    Hi, I have a problem when to connect a client to exchange server 2007, requesting the name given “administrator \ pperez” and does not accept the domain name.
    What can this happening, you can help me with this?

  19. ITAdmin says:

    Worked great, thanks for sharing.

  20. M Sourbes says:

    Hi, should I be able to access those mailboxes via OWA or see them in the exchange console? They show up fine when I do the Get-Mailbox –Arbitration.

    • Martin Sundström says:

      Hi,

      No they don’t show up in EMC, you have to use Powershell to view Arbitration mailboxes.

      Thanks for reading!

  21. Sachin Ps says:

    Great article

  22. Hi I recreated the Active Directory accounts using the setup /PrepareAD as in your Web Page but when I try and create the mailboxes it fails.

    I get the following error:

    The operation couldn’t be performed because object ‘FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042′ couldn’t be found on “dc.domain.local”

    And so on all 4 mailboxes.
    “Get-Mailbox -Arbitration” shows nothing

    i have 1 domain and 1 DC in it.

    what should i do ?

    Thank you

  23. John says:

    Does this include Discovery Search Mailbox?

  24. Sarfraz Aslam says:

    Hi I recreated the Active Directory accounts using the setup /PrepareAD as in your Web Page but when I try and create the mailboxes it fails.

    I get the following error:

    The operation couldn’t be performed because object ‘FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042’ couldn’t be found on “ourchild.domain.local”

    The Exchange Servers are all in the child domain. Do you know what is wrong? It seems to be looking for the account in the child domain and not the root domain.

    Any help would be greatly appreciated.

  25. Martinus says:

    Hi!
    Great article, the best collection of advice on Exchange recovery I’ve found online.
    My current case is with a Exchange 2013 server with what looks like the remains of a failed default database, and a running new one with missing arbitration mailboxes. I found out about the failed one as is appears to be the cause of VSS backups failing. The server is setup on a single partition with 4k NTFS allocation size instead of the recommended 64k.
    I tested repairing the default database in order to migrate the system mailboxes off it on a cloned VM (together with AD DC clone in isolated network). But after a repair with eseutils and attemting to mount, I stumbled on a missing database AD object record for the failed DB.
    How hard can it be to clean out the failed database and recreate the missing system mailboxes on the workign database?
    Now I’m pondering if it would be better to migrate the working user mailboxes to a fresh new setup Exchange server with 64k allocations size, and I guess all the system mailboxes should fall in place as well, and getting backup to work should be straightforward as well.

    Any advice greatly appreciated.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: