VCSServiceManager not uninstalling



Summary:
So here is the scenario.  I'm uninstalling vCenter, but leaving SSO because I am testing something.  I go to upgrade SSO 5.5 to 6.0, I get an error of "Cannot start vCenter Service" or something close to that effect.  Uh ok, why?  vCenter Service isn't even there,  Turns out, my uninstallation of vCenter did not uninstall VCSServiceManager service properly and it now is stuck there.



Workaround:

  1. Visit this page from the affected system
    1. Make sure to add http://*.microsoft.com and https://*.microsoft.com to your trusted sites list in IE.
    2. If you don't, well, you'll likely end up in IE hell.
  2. Run FixIT and run through the wizard to have it remove the VCSServiceManager install.


Details:
The vCenter installation for 6.0, I guess, detects this VCSServiceManager and bombs on the upgrade even if it is just SSO.  So I'd run the uninstall manually and the entry wouldn't go away.  No interactive error, nothing.  Looking at event logs would show that the uninstall bombed w/ a MSI error of 1603.  Basically you have to debug it from what I read.

Then I was dealing w/ wonderful IE security while trying to run the above Microsoft FIXit app.  Once I got around that, it was able to successfully cleanup the stale/broken entry and SSO 5.5 to PSC 6.0 upgrade worked perfectly.

Comments

Anonymous said…
Kudos Bro, you got that one !
June 24, 2016 at 7:59 AM
Anonymous said…
Awesome fix it saved me.
March 24, 2017 at 3:20 PM
Anonymous said…
Worked perfectly for me, great fix!
June 9, 2017 at 6:30 AM
Anonymous said…
You are a life saver !!!
July 17, 2017 at 9:24 PM
Anonymous said…
Thanks for the solution, solved my problem.
October 5, 2017 at 2:11 PM
Anonymous said…
Congrats, solve perfectly problem!
January 9, 2019 at 10:17 AM
Anonymous said…
I was searching hard for a solution to this issue. Thanks for posting this online. You rock!
February 25, 2020 at 11:20 PM
Anonymous said…
Thank you very very much! Fixed the problem!
May 29, 2020 at 7:27 AM
Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more