From an earlier install on a server that was removed it left the Arbitration mailbox though I thought it had been properly removed. How do I repair it and get it pointed back to the new server? [PS] C:\Windows\system32>Get-Mailbox -Arbitration Name Alias ServerName ProhibitSendQuota ---- ----- ---------- ----------------- SystemMailbox{1f05a927... SystemMailbox{1f0... newmail unlimited WARNING: The object XXX.local/Users/SystemMailbox{1f05a927-20f4-466a-9c6a-240a65a5a644} has been corrupted, and it's in an inconsistent state. The following validation errors happened: WARNING: Database is mandatory on UserMailbox. WARNING: Database is mandatory on UserMailbox. SystemMailbox{e0dc1c29... SystemMailbox{e0d... newmail unlimited WARNING: The object XXX.local/Users/SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} has been corrupted, and it's in an inconsistent state. The following validation errors happened: WARNING: Database is mandatory on UserMailbox. WARNING: Database is mandatory on UserMailbox. FederatedEmail.4c1f4d8... FederatedEmail.4c... exch2010 unlimited [PS] C:\Windows\system32> Also when I run get-help * it does not find the get-mailbox cmdlet but finds 297 others. Why is it missing? Thanks

First, try running Setup.com /PrepareAD again. Also, try this article. I'm not sure but the technique may work for all of them. http://technet.microsoft.com/en-us/library/gg588318.aspx Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

It failed saying it needed to be restarted to complete a previous setup. I deleted the disabled SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} and the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 I have 1 disabled system mailbox shown below, I cannot determine where it belongs. Could it be from the 2003 Exchange server or is it orphaned from the 2010 server? SystemMailbox{1f05a927-20f4-466a-9c6a-240a65a5a644} I restarted and have restarted the AD integration D:\Exchange\2010\SP1>Setup.com /prepareschema Welcome to Microsoft Exchange Server 2010 Unattended Setup Preparing Exchange Setup Copying Setup Files COMPLETED No server roles will be installed Performing Microsoft Exchange Server Prerequisite Check Organization Checks COMPLETED Configuring Microsoft Exchange Server Extending Active Directory schema COMPLETED The Microsoft Exchange Server setup operation completed successfully. D:\Exchange\2010\SP1>Setup.com /preparead Welcome to Microsoft Exchange Server 2010 Unattended Setup Preparing Exchange Setup Copying Setup Files COMPLETED No server roles will be installed Performing Microsoft Exchange Server Prerequisite Check Organization Checks COMPLETED Configuring Microsoft Exchange Server Organization Preparation COMPLETED The Microsoft Exchange Server setup operation completed successfully. D:\Exchange\2010\SP1>Setup.com /pad Welcome to Microsoft Exchange Server 2010 Unattended Setup Preparing Exchange Setup Copying Setup Files COMPLETED No server roles will be installed Performing Microsoft Exchange Server Prerequisite Check Organization Checks COMPLETED Configuring Microsoft Exchange Server Prepare Domain Progress COMPLETED The Microsoft Exchange Server setup operation completed successfully. D:\Exchange\2010\SP1> After rerunning the 3 AD integration setups I now have a NEW disabled SystemMailbox SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} and FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 accounts WHY are they disabled?

ED, perhaps you can explain why I cannot recreate the federatedemail mailbox? Is it supposed to have one? [PS] C:\Windows\system32>New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincip alName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain> Active Directory operation failed on DATA2.HDH.local. The object 'CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e04 2,CN=Users,DC=HDH,DC=local' already exists. + CategoryInfo : NotSpecified: (0:Int32) [New-Mailbox], ADObjectAlreadyExistsException + FullyQualifiedErrorId : 7E58B7D9,Microsoft.Exchange.Management.RecipientTasks.NewMailbo

CJlindell, You cannot create a NEW account for an account that already exists in AD. If the AD account exists, as the error tells you, and you don't see it in Get-Mailbox -Arbitration, then you can use the Enable-Mailbox -arbitration -id "<federatedemail account>". This also goes for the system mailboxes. Please let us know if your problem is fixed. Kind regards, Rein