I was taking screenshots as I did a fresh install of the client. Used your zip file, and blogged as I went. Worked great first try. It has also continued to work since then. It seems to be a bit hit and miss for others..I will keep an eye on this thread and update my blog as needed to make things more clear or change instructions.
modmaven.wordpress.com
So I got it working. Unfortunately, it was user error. Thanks to Fernando for hammering the DEVPATH variable point.
On my Win 7 Ultimate RC pc, I had the "start_viclient.bat" setting the DEVPATH to ProgramFiles(x86)/VMware...This doesn't work so well if your system is freakin 32 bit.
I had reversed the batch files when copying them to my 32 bit Win 7 install and my 64 bit Win 7 install. DUH. So both didnt work because the DEVPATH variabe was getting set to a path that didn't exist.
All works perfectly. Thanks for posting the zip file. I can finally use Win 7 and launch the vSphere client. Thanks for everyone's help!
I also discovered something last night, I can't connect to my 3.5 hosts using this hack. It tries to download the older vi client. I can connect from the new client to a 3.5 host on Vista, but not W7.
Hello,
I have the same problem, "run as administrator" does not help:
Installed on W7 RTM 64bit host, vSphere client 4.0.0-162856 works only with the ESX 4.0.0-171294 server.
For ESX 3.5 server, ESX 3.5i server, and vmware server 2.01, it tries to download the older vi client.
I use your viclient_fix.zip, vSphere client 4.0 was installed as administrator.
Oliver
I'm running it just fine. Installed vSphere 4 on Windows 7 Ultimate and everything is working. Been running it since the RTM was available last month.
vSphere version 4.0.0.7797.
HiLimbaugh,
where can I download the latest vSphere Client Version? Could you please upload your version that is working on Windows 7?
Does this Version also support ESX 3.5 Hosts?
Regards - Willi
Awesome! Was hoping there wouldn't be too many hoops to jump through for Win 7. I however installed the VI Client on my D: drive so I had to modify the script just a bit and I'm not using the variables to define the paths. Also thought I'd add this for people that don't like the DOS box sticking around after launching it. I have the last two lines of my batch file (CMD file) set like so:
CD /D "D:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher"
START VpxClient.exe
The CD /D command changes drives if needed and goes to the path specified, then the start command starts up the VI Client while allowing the batch file to complete its run and it closes out the window it was running in. Then you're left with only your VI Client running and no extra dos window.
Thanks to everyone on this! Seems too easy and I'm surprised VMWare doesn't have an update to address this just yet..
