locked
How to remove arbitration mailboxes without access to Exchange Shell RRS feed

  • Question

  • All

    We have a failed Exchange 2010 SP1 w/SP2 we would like to remove, clean and insure environment is more stable, then attempt reinstall.

    Our Exchange services are unstable, won’t start or hang in “starting” state.

    We cannot access EMC or Exchange Shell… errors and cannot find server or Exchange Organization.

    When run Setup to remove of course, hangs at “arbitration mailboxes”, and also “IIS metabase error – IIS might not be installed” (IIS is installed).

    If had shell access could ID and remove arbitration mailboxes no problem (have done in past)… how to do this without Exchange Shell?

    Also what is this “IIS metabase” error?

    We currently have existing production Exchange 2003 running so cannot effect this one when removing failed Exchange 2010.

    Thanks in advance for assist.  -J-

    Wednesday, July 18, 2012 7:03 PM

Answers

  • You're right.  If there is no CAS to which to connect, the tools won't do anything for you.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Thursday, July 19, 2012 4:59 PM

All replies

  • The only supported way to remove an Exchange server is to uninstall it.  If the server was deleted uncleanly, then one option you have is to reinstall it with the /RecoverServer switch and then uninstall it.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Wednesday, July 18, 2012 7:28 PM
  • Thanks for your reply.

    So, if understanding you correctly, we have to get he server running enough (by running setup with the  /RecoverServer switch), for the Exchange Shell to remove arbitration mailboxes and allow Remove to complete?

    What about the IIS metabase error issue?

    Not sure this is the direction we were looking to go but will try running Setup /RecoverServer.  Thx.  -J-

    Wednesday, July 18, 2012 7:57 PM
  • I would hope that reinstalling would fix the metabase error.  Be sure that you have all the prerequisites installed first--IIS Metabase is one of the prerequisites.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Wednesday, July 18, 2012 8:03 PM
  • Thanks for update Ed (by the way.. followed a few of your helpful msexchange.org articles in past).

    We had all prerequisites installed as Exchange would have balked if not; did double check IIS and its there with the Exchange site there in Default Sites.

    Went ahead and ran recover... here is output (names changed to protect the innocent):

    _________________

    E:\>Setup.com /mode:RecoverServer /InstallWindowsComponents /t:"C:\Exchange\Micr
    osoft\Exchange Server\V14" /dc:ourad.ourdomain.com

    Welcome to Microsoft Exchange Server 2010 Unattended Setup

    Preparing Exchange Setup

        Copying Setup Files                           COMPLETED

    The following server roles will be recovered
    Languages
    Management Tools
    Server is not found in Active Directory. Server must be present in Active
     Directory to recover.
    The following server roles are already installed: BridgeheadRole,
     ClientAccessRole, MailboxRole, AdminToolsRole.

    Exchange Server setup encountered an error.

    E:\>_________________

    So now looking up why server is not listed in AD as error says here... any additional insight as feeling this may be original reason first 2010 installation did not work correctly?  Thx.  -J-

    Wednesday, July 18, 2012 8:19 PM
  • You must have me mixed up with someone else.  I've never published any articles there.

    If the server is no longer in Active Directory, then you can just shut it down and remove its computer account.

    You can check in ADSI Edit, Configuration naming context, CN=Services > CN=Microsoft Exchange > CN=<your org name> > CN=Administrative Groups > CN=Exchange Administrative Group (FYDIBOHF23SPDLT) > CN=Servers, inside are your servers.  Is the server you're uninstalling show up there?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Wednesday, July 18, 2012 8:38 PM
  • Hi Stratos,

    Any updates?

    This is your last Exchange 2010 server?

    Did you try to install Exchange 2010 Management Tool on a client to open EMS to delete the arbitration mailboxes?

    Install the Exchange 2010 Management Tools

    http://technet.microsoft.com/en-us/library/bb232090.aspx

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Frank Wang

    TechNet Community Support

    Thursday, July 19, 2012 7:04 AM
  • Back working on this today.

    Don’t see how Management Tools install will help if none of the required Exchange services are running so didn’t do as Mr. Wang suggested?

    Hoping we can all stay on same page as clearly stated this is NOT last Exchange server and must be careful not to interfere with production Exchange 2003.

    About to confirm if see server in ADSI Edit as suggested by Mr. Crowley:

    Configuration naming context, CN=Services > CN=Microsoft Exchange > CN=<your org name> > CN=Administrative Groups > CN=Exchange Administrative Group (FYDIBOHF23SPDLT) > CN=Servers,

    Will post findings right away and thanks again all for assistance.  -J-

    Thursday, July 19, 2012 4:57 PM
  • You're right.  If there is no CAS to which to connect, the tools won't do anything for you.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Thursday, July 19, 2012 4:59 PM
  • OK; so in the AD (via ADSIEdit) see the Exchange Administrative Group (FYDIBOHF23SPDLT) was created and the failing server is listed there.

    It almost seem like will have to repair this installation more before can remove it... and if repair that much it most likely should be stable to go into production.

    Right now there appears may be, or was, domain communication issue as cannot connect to DC to fire ADSIEdit.

    This is a Hyper-V guest machine and working on getting NIC correctly configured again.

    Will update once restored full domain connectivity to failed Exchange 2010 server.

    Thursday, July 19, 2012 7:09 PM
  • OK; Current newly built failed Exchange 2010 server is not acting correctly as far as domain access.

    As mentioned before we have a new Exchange Admin group (FYDIBOHF23SPDLT) and our original, but separate, Exchange 2003 Admin group (OURADMINGROUP).

    Can we just remove the failed server from the new admin group (ADSIEdit), or entire admin group, re-insure our domain is stable and reinstall Exchange 2010?

    Thanks.  -J-

    Thursday, July 19, 2012 8:50 PM
  • Can we just remove the failed server from the new admin group (ADSIEdit), or entire admin group, re-insure our domain is stable and reinstall Exchange 2010?

    Hi Stratos,

    Ad Ed said, this is not supported.

    Did you follow the steps to recover the Exchange Server as link listed:

    Recover an Exchange Server

    http://technet.microsoft.com/en-us/library/dd876880.aspx


    Frank Wang

    TechNet Community Support


    • Edited by emma.yoyo Friday, July 20, 2012 5:52 AM Remove->Recover
    Friday, July 20, 2012 3:40 AM
  • Thanks for your reply; however, as mentioned in thread above (with specific output), that did not work and is why asking specific questions.

    We are obviously in an unsupported state and have to get past it... if you can please scan through details of entire thread perhaps you could provide some helpful insight.  Thx.  -J-

    Friday, July 20, 2012 5:09 AM
  • Stratos,
    It's not clear in your previous post that you did reinstall the OS.
    To me it looks like you tried to run setup.com /recoverserver on the server and that will not work.


    Martina Miskovic

    Friday, July 20, 2012 5:47 AM
  • Thanks for your reply; you are correct… however we are at point where there is no value in pursuing this route any longer as our environment has deeper issues that most likely contributed to failed Exch2010 installation.

    May post strange symptoms, going on in domain, in the Windows Directory Services or Migration forum.

    Thanks for all you replies.  -J-

    Friday, July 20, 2012 6:37 AM