I was sure my config file was identical to yours but still had an error. It ran but after entering the IP address/Host name, user/pwd I would get an error stating that I needed to enter a valid host name. used your attached file and that did the trick.
Thanks for your hep
Considering that those companies that actually own a Class A subnet (GEGE, Level3, HP, Xerox, Apple, DoD, Army, Xerox, UK MOD, you name them) are also large customers of VMware products (ok, probably Apple is not), fixing a Class A Subnet may seem a trivial issue to fix, but does have a potential large impact.
Copying the DLL and creating this batch file worked great on my windows 7 install. One thing though .... make sure you remove the "s around the SET PATH= variable, otherwise you won't see all the available plug-ins. I just found this out while taking the What's New class and there was a lab walking you through the Storage Views tab which I didn't have, but now I do
Thanks again for the fix Fernado!
I discovered an interesting thing (that may or may not help the VMware team locate the problem) ...
On a Vista machine that was in-place upgraded to Windows 7 RTM, the VI 2.5 client (used to manage my old VMware Server 2.0 install) installed and ran without issue. (It was uninstalled at the request of the Win7 Compatibility Wizard)
After installing the vSphere client, it stopped working.
Since I made a copy of the Launcher folder from the VI2.5 install, I tried running it from there again and Launcher worked for the Server 2.0 but since the older launcher doesn't know how to interpret the client.xml file from vSphere, it did not work w/ ESX 4.
From a cursory look at the changes to the Launcher, it appears that the following has changed:
1) Removal of the open source libeay.dll and ssleay32.dlls
2) Addition of VI.Utils.dll
I'm guessing that they started using one of the System functions to either bootstrap the loading of the VI.Utils.dll or to make calls through System.Web to handle the SSL encryption.
On another more important note: The ESX Update Manager for vSphere also fails in Windows 7 RTM and attempts to use the client work-around failed.
I have created a powershell script that does most of the work for you with getting the vSphere client running on Windows 7. It's posted over on my site with a nice rundown of what exactly it's doing. Basically it edits the config file for you, copies over the system.dll needed, creates the launcher batch file with the devpath setting, and then creates a shortcut on your desktop. Hopefully this will help some people that may be confused by the steps outlined here.
Hi, thanks for your post. It's very helpful
looks like the different .net framework may cause this problem.
And due to the different version, the compability won't help in this case.
I tested this and it work on Windows 7 Professional x86 (6.1.7600)
Which should be the official(MSDN) version.
BTW, with your permission, I will post your solution on my blog with your name and this link. thanks.
I have attached a zip file that includes everything for the 64bit version, all you need to do is to unzip it to c:\Program Files (x86)\VMware\Infrastructure\
There is a link that I modified in the path above that you can put on your desktop to use.
Thanks for the workaround
Thanks. That zip file worked fine on Windows 2008R2 also!
Thank you Fernando for your solution!! Works like a charm!! Thank you very much!
Note -- for the Update Manager to also work you just need to copy C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe.config to C:\Program Files\VMware\Infrastructure\VIUpdate 4.0\VIUApp.exe.config. Works fine assuming you've done the workaround to get the VIClient working.
Rick (Bucks, UK)
Matthew, I just updated the script to include fixing up the vsphere host update utility as well so you dont have to copy over config files or anything. It also adds a desktop icon for the launcher for that as well now.
I updated using your zip file and the vSphere Client starts fine but the update client crashes saying VIupdate has stopped working, windows is checking for a solution.
Don, could you be more specific please?
What architecture are you using? (32 or 64 bit?)
Did you click the provided shortcut to start it or did you start it manually?
Exactly what did you do to start it?
Screenshots would help as well.