as you said since Windows 7 is still in RC, you may have a tough time finding support. I've attached the compatibility matrix just in case
Use Windows XP Mode for Windows 7:
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
While the XP mode provides a temporary solution it better not last long as trying to manage the console of Virtual Machines through another VM causes a hell of alot of mouse control problems that quickly get very frustrating.
Seems to me that Windows 7 should have been tested and working long before now, its not like its a complete re-write of the operating system.
But then again, Virtual Center and the VIC were never vmware's strong point and obviously that trend is going to continue.
As Troy says this does not work on Windows 7 yet, and I would not expect it to / complain as Windows 7 is not yet RTM anyway.
Andy, VMware Certified Professional / VMware vExpert Award 2009
Help, Guides and How Tos http://www.vmadmin.co.uk/
If you found this information useful please award points using the buttons at the top of the page accordingly.
(Apologies if this is posted twice. I had some trouble with the editor and may have accidentally posted the message while editing it.)
Here's a possible workaround for this problem.
1. Obtain a copy of %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll from a non Windows 7 machine that has .NET 3.5 SP1 installed.
2. Create a folder in the Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory (%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib).
3. In the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a <runtime> element and a <developmentMode> element as shown below. Save the file.
<?xml version="1.0" encoding="utf-8"?>
3. Create a batch file (e.g. VpxClient.cmd) in a suitable location. In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file. For example,
SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
"%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"
4. (Optional) Replace the shortcut on the start menu to point to the batch file created in the previous step. Change the shortcut properties to run minimized so that the command window is not shown.
You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.
Note that this workaround bypasses the normal .NET Framework loading mechanism so that assembly versions in the DEVPATH folder are no longer checked. Handle with care.
Instead of creating a batch file to load it I set a DEVPATH environment variable instead.
That might not work for everyone though, it depends on whether you have used the developmentmode trick for any other .net applications.
Sure. You can globally set the DEVPATH variable but I prefer to do it where it has the least impact. Besides, I don't trust myself to remember the change in a few months (days?) time and this reduces the chance that I will have some left over changes in my configuration.