Yah, that XP VM should run the client fine. Hopefully your system has the necessary processor requirements to run that version of Virtual PC (I think Microsoft really screwed up on that requrement, especially since previous Virtual PC versions do not require CPU virtualization assist???)

Not to be "that guy" but shouldn't someone from VMware tried the VI client on a Windows 7 PC? I know it's in beta (RC actually) but not to test it at all is rather silly.

I guess I'll have to use my Windows XP in Unity mode to test out the new software. If anyone figures out a work around please post it.

Mike

There has been a mass exodus from Vista to Windows 7 going on since the beta was released back in February. The fact that the vSphere client doesn't work in Windows 7 is very surprising. Most of the techs in my office are running Windows 7 and this is a major issue for us. I know we have alternatives like using XP mode and such (using a non RC OS), but I'm assuming the fix should be simple. Yes....I'm basing this on the fact that other than drivers I've only run into a handful of applications that work in Vista but not Win7. Of those handful a couple were able to run once UAC was disabled.

I know this is the first day of the "official' release, but I know VMWare is aware of the issue. When I did a search for this issue I seen some old posts in the beta community, but I can't read them because I'm not authorized.

I guess we are all stuck in a holding pattern until VMWare gives us some guidence.

Please hurry!

I'd like to get it working, too...

Seems like XP Mode is the way to go.

Hope there's an update, soon.

I was able to hit the vCenter server just fine to download the client, but I did get the Certificate error in IE8 on my system. My XP VM has IE8 and I was able to ignore the Cert issue just fine. It's possible there is something inherent in Win7 that's different, but I'm open to anything at this point. Also of note, the upgrade breaks our Xendesktop server as well (but I think that's an SDK compatibility issue and not SSL).

Unfortunately it doesn't look like a certificate trust issue or some other network communications-related stuff. According to Network Monitor, vSphere client actually does not even try to talk to server. So it has to be some local compatibility problem. Unresolved dependencies or something like this...

The funny part here is that vCenter Server 4.0 itself works perfectly on Windows Server 2008 R2 RC (which is the same OS actually as Windows 7).