Exchange 2013 in Hybrid need to remove and reinstall

I have been working on this installation with issue after issue.  The Microsoft Exchange 2013 server is being installed as a Hybrid solutions for Microsoft Office 365 and On-premise Exchange 2007.

The Exchange 2013 server has been installed, but it has been a bodgy installation and I think instead of running around in circles it is best to remove installation and start again, would be good if I could just start fresh with new server if it is possible.

The Exchange 2013 has not been configure in any real way except for the button be click to enable hybrid.  Can some suggest some best ways to remove and reinstall or is it best to start with new server.

Regards,
ITSystemSolAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
If you deselect the option to be hybrid, you should be able to remove Exchange using add/remove programs. The most you may have to do is move/remove some arbitration mailboxes. The uninstaller will tell you what needs to be done.

Simon.
0
ITSystemSolAuthor Commented:
I actually went through the uninstall it got to stage 3 and crashed now I cannot install or uninstall.  Even tried a registry hack which allowed me to install part of it again but it crashed.

Is there a good method to just remove this server and start on another, what should I be looking at if I do this.  I have performed a manual removal of a Exchange 2010 but not sure if it is same.
0
Simon Butler (Sembee)ConsultantCommented:
Crashed for what reason? I have rarely seen the uninstaller crash - it will often fail with an error message, but that is about it.
There are no manual removal methods for any version of Exchange 2007 and higher which are supported. You cannot just wipe the machine either.

Depending on how far it got, you may be able to recover it. That would mean wiping the machine, resetting (NOT DELETING) the computer account, then reinstalling WIndows with the same name and installing Exchange from the command line. Once installed, removing it again using add/remove programs.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

ITSystemSolAuthor Commented:
I can understand what your saying, but from the out set a installation into the MSExchange 2007 environment was performed with a non CU2 exchange 2013 and it failed installing correctly then I installed overt the top of this with CU2 and something happened all the services disabled including non exchange 2013 services.

In the end I thought I would uninstall however after removing the mailboxes and performing an uninstall it just failed and would not go any further.

So I will give your method a go and see what happens.  This was meant to be a simple Hybrid installation finished days ago.
0
ITSystemSolAuthor Commented:
I have run the installation on a new server build using the Setup /mode:recoverserver all was going fine and then got the following error when it was doing the Mailbox role: Client Access Service

set-installPathInAppConfig -ConfigFileRelativePath "ClientAccess\PushNotifications\" -ConfigFileName web.config

" was run: "Specified cast is not valid.".
0
ITSystemSolAuthor Commented:
The above issue fixed now a new one.  To resolve this had to go into ADSI edit and manually remove the virtual directories under the Exchange Server name also when running the setup had to remove the connectors as well.

New issue is I stupidly removed the actual virtual directory powershell.  Can anyone provide me a list of the commands to rebuild the virtual directories or best solution to repair all of them.
0
Simon Butler (Sembee)ConsultantCommented:
This is the command structure for ECP:
http://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx

The others are pretty much the same - so that will be OWA, OAB, Autodiscover, EWS. You will find them listed down the left hand side.

Simon.
0
ITSystemSolAuthor Commented:
I ended up rebuilding a new server with exact name and ip and reset domain account.

Performed a server recovery and got the following message,


Preparing Setup                                           COMPLETED
    Stopping Services                                         COMPLETED
    Copying Exchange Files                                    COMPLETED
    Language Files                                            COMPLETED
    Restoring Services                                        COMPLETED
    Language Configuration                                    COMPLETED
    Mailbox role: Transport service                           COMPLETED
    Mailbox role: Client Access service                       FAILED
     The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
          get-OwaVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVd
irIdentity -DomainController $RoleDomainController| remove-OwaVirtualDirectory -
DomainController $RoleDomainController;
          new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End"
 -DomainController $RoleDomainController;
          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
        " was run: "The operation couldn't be performed because object 'EXCH-SRV
-HYBRID\OWA (Exchange Back End)' couldn't be found on 'bhs-srv-acc-dc1.balwynhs.
vic.edu.au'.".


The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Thought I would just run the recovery again now I get this message:  Can some please help get me through this as I am now out of options.  If there was a way to just run a fresh new installation I am open to this.  The original install was done with the notion of a Exchange 2007 with OFfice 365 so far I cannot get past this.

Welcome to Microsoft Exchange Server 2013 Cumulative Update 2 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Mailbox role: Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service
Client Access role: Front End Transport service
The following server roles are already installed: BridgeheadRole,
 ClientAccessRole, MailboxRole, UnifiedMessagingRole, FrontendTransportRole,
 AdminToolsRole, CafeRole.

The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
0
Simon Butler (Sembee)ConsultantCommented:
A clean installation isn't going to be possible because you have this broken installation in place. If you are moving to Office365 then you might be able to get support from Microsoft that way.

What does the log say? Don't attach the entire thing - most of it is useless. Look for the error and post the lines around it.

Simon.
0
ITSystemSolAuthor Commented:
This is meant to be a Hybrid installation coexistence with Exchange 2007 (Which is patched to support exchange 2013) that went wrong.

Before you posted I just tried to perform a uninstall of exchange to see if I could get it to reinstall no luck as mailboxes exist and usually you can remove them but the uninstall broke EMC.

What I have done a several times is try to rebuild new server same name, same IP same hardware spec and then do a /m:recoverserver, but everytime I do this I get the issues related to ClientAccess server.

I am now looking for ideas on how to do a clean up if there is one
0
ITSystemSolAuthor Commented:
This is the current message I am getting.  I fixed EMC by removing the Unistall options on the MAILbox role in registry

Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
          new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController;
          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
        " was run: "The operation couldn't be performed because object 'EXCH-SRV-HYBRID\OWA (Exchange Back End)' couldn't be found on 'bhs-srv-acc-dc.balwynhs.vic.edu.au'.".
0
ITSystemSolAuthor Commented:
I am applying the points to you as you have helped so much throughout and I don't want you to loose them.  I did do a reinstall of the server but I am getting the missing OWA in AD so I am posting new question for that alone.
0
Simon Butler (Sembee)ConsultantCommented:
I have nothing else to suggest other than a call to Microsoft. If you are migrating to Office365 it may well come under Office365 support (As you cannot do hybrid).

Simon.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.