I think the most important thing to remember is that the VM’s keep running whatever happens to your VC Server and HA will still work if VC fails, well except for adding hosts to the cluster of course.
So reinstalling the Virtual Center server and re-adding the hosts is still possible, but in my opinion not recommended.
4 4.1 7 2008 client compliance converter esx esxi esxtop free get-vm guest guide hardening host ibm iso mail offline onyx parallel plugin powercli Power Shell powerwf script scripts sdk server snapshot state Tools tripwire upgrade vc vcenter virtual virtualcenter Virtual Center virtual hardware vm vmware vsphere windows When connecting some storage systems to v Sphere, v Sphere sometime doesn’t select the most optimal multipathing policy.
I came across the above problem when adding an EMC VPLEX storage system to a large v Sphere 4.1 installation.
We are offering the firmware updating program to the TS-590SG owners.
You can update the TS-590SG firmware by connecting the TS-590SG to the PC by using a USB cable or an RS-232C cable.
The firmware updating program may not behave properly if a connection is in place through a USB hub.It should give you a web page and a link to download the client and a link to login to the Web UI.If the page displays correctly then login to the web ui to test your logon/pw Looks like there is a bigger problem.When I try to connect to a couple of our ESXi servers with my v Sphere client I get the following error message: "v Sphere Client could not connect to "IP Address". (The client could not send a complete request to the server.(The underlying connection was closed: An unexpected error occurred on a send.)) I'm thinking this may have something to do with a version incompatibility but I'm not sure. This error troubled me for quite a while, and since this thread is still the first google result, here is my solution.