When you want to run VI client on Windows 7 recently released or on Windows 2008 Server R2
The problem was known for some time now, and the bloggers community found a workaround quite quickly. VMware was a bit late to officially fix this trouble with this official KB article:
Cannot launch vSphere Client after installing in Windows 7 or Windows 2008 R2
In case that you did not use VMware VI client on Windows 7 before. you might did not even notice the need, but if you now want to try to you must follow this KB otherwise you'll get an error when you'll want to execute the VI client…..
I think that a complete fix will become widely available with an update of vSphere 4. Would it be ESX 4.1? Who knows…
Recently a new version of VMware vSphere has been introduced and is available for download. The new installer has been completely revamped and introduced two ways of installing VMware vSphere:
Express Install of vSphere 5.1 – Installation process has been simplified to install the VMware vSphere 5.1 suite. There is now Simple Install button, which can be used to install the necessary products one after another using the same installer.
Custom Install – There is also Custom Install possibility as well, which let’s you customize the installation, and install different components, like the New vSphere 5.1 Web client, or the Single Sign-On, on different servers, to improve scalability.
Also, the new enhanced vMotion is new in vSphere 5.1 – Enhanced vMotion enables you to move VMs which runs on local storage on one host to local storage on another host. The VMDK disk files are moved from one side to another without the need of shared storage. The VM moves from one physical host to another. Servers with local disks can now be used for VMware vSphere installations in SMB.
– Hosts must be managed by same vCenter Server.
– Hosts must be part of same Datacenter.
– Hosts must be on the same layer-2 network (and same switch if VDS is used).
