unable to uninstall Management Tools 2013

%3CLINGO-SUB%20id%3D%22lingo-sub-69439%22%20slang%3D%22en-US%22%3Eunable%20to%20uninstall%20Management%20Tools%202013%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69439%22%20slang%3D%22en-US%22%3E%3CP%3ESo%2C%20as%20I%20already%20mentioned%20in%20another%20post%20I%20had%20this%20%22great%22%20idea%20to%20move%20from%20a%202013%20to%20a%202016%20onpremise%20server.%20After%20removing%20(guess%20that%20was%20error%20one)%20the%20exchange%202013%20server%20I%20tried%20to%20change%20the%20management%20tools%20on%20my%20desktop%20as%20well%2C%20which%20resulted%20in%20total%20desaster.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%20the%20setup%20refused%20and%20said%20it%20needed%20a%20reboot%2C%20so%20fine%20I%20did%20that.%3C%2FP%3E%3CP%3EThen%20it%20complained%20about%20the%20setup%20had%20not%20properly%20finished%20and%20I%20needed%20to%20rerun%20that%2C%20which%20turned%20out%20to%20be%20impossible%20as%20I%20no%20longer%20had%20any%202013%20in%20my%20domain.%3C%2FP%3E%3CP%3ESo%20I%20looked%20it%20up%20and%20found%20an%20upgrade%20switch%20for%20the%20exchange%20setup%2C%20so%20I%20though%2C%20well%2C%20just%20do%20something%20like%20a%20management%20tool%20upgrade%20from%202013%20to%202016%2C%20guess%20what%2C%20this%20did%20not%20work%20neither.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20got%20desperate%20and%20tried%20to%20remove%20the%20directory%2C%20registry%20keys%20I%20found%2C%20the%20entry%20in%20the%20installed%20programmes%2C%20but%20still%20the%202016%20setup%20refuses%20to%20start%2C%20telling%20me%20I%20have%20still%20a%202013%20console%20installed%20which%20needs%20to%20be%20gone%20first.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20my%20question%20is%2C%20does%20anyone%20have%20an%20idea%20how%20I%20get%20this%20baby%20rolling%20again%20besides%20reinstalling%20my%20whole%20desktop%2Fmove%20to%20another%20pc%20in%20order%20to%20have%20local%20management%20tools%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-69439%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69528%22%20slang%3D%22en-US%22%3ERE%3A%20unable%20to%20uninstall%20Management%20Tools%202013%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69528%22%20slang%3D%22en-US%22%3EDigged%20into%20Registry%20again%20and%20removed%20anything%20looking%20remotely%20like%20Exchange%20(searched%20for%20%22Exchange%20Server%22).%20Afterwards%202016%20setup%20went%20through%20fine%20and%20I%20have%20an%20exchange%20powershell%20again.%20Happy%20Panda%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E
Contributor

So, as I already mentioned in another post I had this "great" idea to move from a 2013 to a 2016 onpremise server. After removing (guess that was error one) the exchange 2013 server I tried to change the management tools on my desktop as well, which resulted in total desaster.

 

First the setup refused and said it needed a reboot, so fine I did that.

Then it complained about the setup had not properly finished and I needed to rerun that, which turned out to be impossible as I no longer had any 2013 in my domain.

So I looked it up and found an upgrade switch for the exchange setup, so I though, well, just do something like a management tool upgrade from 2013 to 2016, guess what, this did not work neither.

 

I got desperate and tried to remove the directory, registry keys I found, the entry in the installed programmes, but still the 2016 setup refuses to start, telling me I have still a 2013 console installed which needs to be gone first.

 

So my question is, does anyone have an idea how I get this baby rolling again besides reinstalling my whole desktop/move to another pc in order to have local management tools?

 

 

1 Reply
Digged into Registry again and removed anything looking remotely like Exchange (searched for "Exchange Server"). Afterwards 2016 setup went through fine and I have an exchange powershell again. Happy Panda :)