Windows 7 and VMware VI client issue fixed with official KB
When you want to run VI client on Windows 7 recently released or on Windows 2008 Server R2
The problem was know for some time now, and the bloggers community found a workarround 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 folow this KB otherwise you’ll get an error when you’ll want to execute the VI client…..
I think that a complete fix will became widelly available with an update of vSphere 4. Would it be ESX 4.1? Who knows…
Other posts from Server Virtualization
- Create your own Provider Virtual Data Center
- Measure some perf benchs with VMark
- VMware partners with Symantec on ApplicationHA
- Andre Leibovici's Linked cloning storage calculator
- SIOC yes, but not in the SMB kit...
- Best practices KB on how-to install ESX 4.1 and vCenter
- Hyper-V and new linux integration tools
- How to Fix “Transaction log for database ‘VIM_VCDB’ is full” errors
- How to change from ACPI Multiprocessor HAL back to ACPI Uniprocessor HAL in Windows 2003
- AD Integration for ESXi 4.1
- vCenter converter with Hyper-V import
- Serial Port handling in ESXi 4.1
- Four memory optimization techniques available in vSphere 4.1
- Activating remote access via SSH in ESXi4.1
- vSphere Compatibility Matrixes
- 150 new features or enhancements in vSphere 4.1
- Personalized install of VMware tools
- VMware tools download from VMware Website
- How to change virtual SCSI controler
- Microsoft's patch for .NET breaks VI client connection
