VMware Communities: Message List - vsphere client on Windows 7 rc

Re: vsphere client on Windows 7 rc

Innuendo — Sat, 21 Nov 2009 10:40:55 GMT

Ok, my issue surely is due to the way I installed it.

I tried to install it above the "modified" installation, which doesn't work then.

So to make it work, you surely have to unistall everything (let's hope it's enought) or even rebuild your system (!!!).

By the way my bad, seems to be working with 7 / 2008 R2 now.

Re: vsphere client on Windows 7 rc

Photubias — Fri, 20 Nov 2009 13:35:50 GMT

I had a Windows 2008 R2 x64 with the reported error and did NOT perform the workaround.Instead, I uninstalled vSphere Client and installed build 208111 from vSphere Client.

Everything is working like a charm, and this thread may be locked now.

I'll try to directly link the url here but if it does not work, please try to download ESXi from vmware.com and in the download page choose the new vSphere client binary.
Link

Thanks for rewarding answers!

Greetings,

Photubias

Re: vsphere client on Windows 7 rc

Mr-E — Fri, 20 Nov 2009 13:20:54 GMT

Hi, I have downloaded the new client this morning and installed onto a recently (Monday) rebuilt Windows 7 x64 build and I have to say, everything appears to be working so far. I have received no error pop-ups while connecting either to VC 2.5 or to and ESXi 4 (free) box.

Will continue playing and come back with any issues experienced.

Regards

Mr-E

Re: vsphere client on Windows 7 rc

Innuendo — Fri, 20 Nov 2009 11:02:01 GMT

Doesn't seem to fix anything so far, can someone confirm or infirm ?

Just upadted my client and nothing changes, still failing to launch without modification.

Plain sad from VMware if you ask me. Very sad.

Re: vsphere client on Windows 7 rc

emm1 — Fri, 20 Nov 2009 10:47:34 GMT

Do you have an URL where I can download the client?

Re: vsphere client on Windows 7 rc

tsd_david — Fri, 20 Nov 2009 08:09:26 GMT

vCenter Server 4 Update 1 released!! (both with ESX 4, ESXi 4, vSphere Client)

Re: vsphere client on Windows 7 rc

DSeaman — Thu, 19 Nov 2009 02:23:37 GMT

Yes I find it amazing VMware is so slow to support W7 and 2008 R2. They RTM'd MONTHS ago and have been available to businesses since August. 95% of the VMs are Windows so more timely suport from the market 'leader' should be expected.

Re: vsphere client on Windows 7 rc

pviqueira — Wed, 18 Nov 2009 17:37:49 GMT

It is incredible that vmware has not yet released a version for windows 7. maybe the best option is to think in Xen or HypeV.

Re: vsphere client on Windows 7 rc

ric9887 — Fri, 13 Nov 2009 14:27:47 GMT

I have found that I had 2 different versions of system.dll

2.0.50727.4927

2.0.50727. 3053

I found that version 2.0.50727. 3053 worked, while the other version still gave the parsing problem for clients.xml. No idea exactly where each version came from, but if you arehaving problem even after setting the environment variable, changing the config file and copying the file, then check the exact version of this file.

I can not believe they have not released a version of Infrastructure manager which works nicely with Windows 7.

Re: vsphere client on Windows 7 rc

firefox111 — Fri, 13 Nov 2009 13:56:11 GMT

Thank you. But how do I get to that fix? Where is it?

Re: vsphere client on Windows 7 rc

PFSpfs — Thu, 12 Nov 2009 15:49:11 GMT

I get a:

Window Title
VpxClient

Main Instruction
VpxClient has stopped working

Content
Windows can check online for a solution to the problem.

[V] View problem details Check online for a solution and close the program Close the program

What can I do????

Re: vsphere client on Windows 7 rc

amitjoshi — Wed, 11 Nov 2009 18:28:18 GMT

Fernando's fix works perfectly on Windows 7 Enterprise x64. Thanks for your help!

Re: vsphere client on Windows 7 rc

firefox111 — Sun, 08 Nov 2009 12:58:52 GMT

I am running Win7 retail. vsphere client still does not run on Win7. "Error parsing the server "192.168.0.240" "clients.xml" file...."

Re: vsphere client on Windows 7 rc

JasonVITE — Thu, 05 Nov 2009 13:22:33 GMT

I had to edit the Vsphere.cmd to this:

SET DEVPATH=C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib
"C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"

Not sure if that was any big difference but if you need to simply copy and paste that might help... Thanks a lot for the original post

Re: vsphere client on Windows 7 rc

fcollin — Tue, 03 Nov 2009 12:03:28 GMT

Unfortunately XP mode is only possible if your computer supports intel VT or the AMD equivalent. If for some reason your bios locks that option or you have an older computer this is not a valid workaround.

Re: vsphere client on Windows 7 rc

DoranceMC — Mon, 02 Nov 2009 06:26:04 GMT

thanks for solve that problem

Re: vsphere client on Windows 7 rc

tnolan — Fri, 30 Oct 2009 21:55:13 GMT

jamesrichter wrote:This did not work on my system. I'm running Windows 7 Ultimate and the only 'compatibility' option was a wizard where I did select XP SP3, and it still generates the same error message for clients.xml.

If you use my powershell script it will set this up for you and you
wont have to use compatibility mode which is slow in my experience.
Hope this helps!

http://www.tinyint.com/index.php/2009/09/04/vsphere-client-on-windows-7/

Re: vsphere client on Windows 7 rc

jamesrichter — Fri, 30 Oct 2009 21:23:35 GMT

x86. I understand there is a workaround, but it seems crazy that VMware isn't support a client OS with their vSphere client. I understand it's a .NET issue with a .dll but that doesn't seem something un-correctable.

Re: vsphere client on Windows 7 rc

TGW69 — Fri, 30 Oct 2009 21:19:05 GMT

Windows 7 Ulitmate x86 or x64? did you check the following workaround? http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 this is proven to work on 64bit.

Re: vsphere client on Windows 7 rc

jamesrichter — Fri, 30 Oct 2009 20:12:22 GMT

This did not work on my system. I'm running Windows 7 Ultimate and the only 'compatibility' option was a wizard where I did select XP SP3, and it still generates the same error message for clients.xml.

Re: vsphere client on Windows 7 rc

CarnageHimura — Fri, 30 Oct 2009 00:13:23 GMT

Tonym89, Your process has working perfect to me, Thak you!!!

Re: vsphere client on Windows 7 rc

tsd_david — Mon, 26 Oct 2009 19:07:41 GMT

TGW69 wrote:
I have seen many workarounds for this issue. The best one that I have seen with full detailed instructions is on the following site.

http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7

Dear TGW69,

It is a good method! I set on my Windows 7 Enterprise x64 RTM, works and no batch file need. Thanks!

-david

Re: vsphere client on Windows 7 rc

Jeshurunsa — Mon, 26 Oct 2009 18:02:26 GMT

This worked for me on Windows 32 bit platform :-

1. Install Vspehere Client 4.0.0 on Windows 7

2. Right Click on Shortcut on Desktop and select compatibility

3. Select Checkbox and run th program in compatibility mode for Windows XP3

4. Click Ok

5. Run Vsphere Client

Re: vsphere client on Windows 7 rc

TobiasKracht — Mon, 26 Oct 2009 17:36:00 GMT

My mistake, I didn`t note, that I used it as addition to fix with DEVPATH. Sorry )

StarWind Software R&D
http://www.starwindsoftware.com

Re: vsphere client on Windows 7 rc

rcustersp — Mon, 26 Oct 2009 17:34:10 GMT

Mine does not work with WCF installed. I installed both the http and non-http versions. No luck.

Re: vsphere client on Windows 7 rc

TobiasKracht — Mon, 26 Oct 2009 17:09:32 GMT

I`ve just found that it 100% works without any problems if install WCF in Windows components.

StarWind Software R&D
http://www.starwindsoftware.com

Re: vsphere client on Windows 7 rc

JamesSykes — Fri, 23 Oct 2009 09:38:26 GMT

Comon Vmware pull your finger out. Windows 7 has been RC forever now and it's not released. This client should have been here a long time ago.

Re: vsphere client on Windows 7 rc

TGW69 — Thu, 22 Oct 2009 21:27:26 GMT

I have seen many workarounds for this issue. The best one that I have seen with full detailed instructions is on the following site.

http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7

It does include the system.dll file that is needed to run as well. I have not had any issues with the client after making these changes.

Re: vsphere client on Windows 7 rc

HaTaX — Sun, 11 Oct 2009 22:41:37 GMT

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..

Re: vsphere client on Windows 7 rc

seans — Fri, 09 Oct 2009 17:59:51 GMT

The powershell script worked like a charm for me. Many thanks.

Re: vsphere client on Windows 7 rc

KingAlex23 — Thu, 08 Oct 2009 02:34:56 GMT

GodSpeed Fernando that worked like a charm.

"Bad .NET, bad...."

Re: vsphere client on Windows 7 rc

darko011 — Sun, 04 Oct 2009 21:23:50 GMT

thanks for this zip

Re: vsphere client on Windows 7 rc

WilliHDT — Sat, 03 Oct 2009 09:33:26 GMT

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

Re: vsphere client on Windows 7 rc

oli116 — Fri, 02 Oct 2009 10:50:15 GMT

Has anyone tried connecting to Server 2.1, ESX 3.5, or ESXi 3.5? This does not work for me, only connecting to ESX 4.0 with vShere Client 4.0 works.

Re: vsphere client on Windows 7 rc

Limbaugh — Wed, 30 Sep 2009 15:54:57 GMT

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.

Re: vsphere client on Windows 7 rc

oli116 — Mon, 28 Sep 2009 10:21:18 GMT

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

Re: vsphere client on Windows 7 rc

evanism — Sun, 27 Sep 2009 14:42:31 GMT

Brilliant Zip, worked a treat.

Re: vsphere client on Windows 7 rc

Guy Chapman — Tue, 22 Sep 2009 08:21:28 GMT

If I could award points for this I would. You just saved me a massive amount of work, Fernando. Thanks.

Guy

Re: vsphere client on Windows 7 rc

GlenR — Mon, 21 Sep 2009 18:35:25 GMT

That's very possible, the first thing I do is disable UAC so I don't run into issues like this

Re: vsphere client on Windows 7 rc

donfrank — Mon, 21 Sep 2009 18:21:28 GMT

Makeing progress. If I click on the start_viupdate.bat file I get the error. If I run as Administrator, it works fine. Is there a premission problem?

Don

UPDATE: I went to the shortcut for vSphere Update Client and went to the properties and selected run as Administrator. Now it works fine.

Re: vsphere client on Windows 7 rc

GlenR — Mon, 21 Sep 2009 14:35:25 GMT

Glad to hear you got it working Rob.

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.

GlenR

Re: vsphere client on Windows 7 rc

robshaw22 — Mon, 21 Sep 2009 04:33:52 GMT

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!

Re: vsphere client on Windows 7 rc

modmaven — Sun, 20 Sep 2009 22:32:06 GMT

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

Re: vsphere client on Windows 7 rc

ftubio — Sun, 20 Sep 2009 21:53:12 GMT

For the error "VpxClient (or Vi Update) has stopped working", this is typically a sign that the DEVPATH environment variable is pointing to a location that does not exist. You should double-check that the variable is being set to an existing folder that contains the System.dll file (from a non-Windows 7 machine).

For the error "Error parsing the server "192.x.x.x" "clients.xml", this usually means that either the configuration file is missing the <runtime> section that enables developmentMode or that the System.dll file is not present in the folder where DEVPATH is pointing. In other words, the folder exists but you have failed to copy the file into it.

My suggestion is to troubleshoot this by opening a command prompt and typing in the commands in the batch file. After setting the DEVPATH environment variable, type CD %DEVPATH%, which should change the current directory to the folder where you placed the System.dll file. If you get an error, it means that you are not setting the path correctly. Next, you can run DIR to make sure that the System.dll file is in the correct location.

Good luck.

Fernando Tubio

Re: vsphere client on Windows 7 rc

donfrank — Sun, 20 Sep 2009 21:05:32 GMT

I have reinstalled and then applied your "patch" as instructed. I get the same issue as before. The Update client fails. I am using your shortcuts in the directory and not any from the desktop. I also tried to execute the update bat file directly.

Re: vsphere client on Windows 7 rc

robshaw22 — Sun, 20 Sep 2009 20:58:31 GMT

I installed the viclient from the ESXi host on Win 7 RC Ultimate. Unzipped the latest zip file. Launched viclient via the batch file and the client launches, but with the original errors. Weird. "Error parsing the server "192.x.x.x" "clients.xml" file. Login will continue, contact your system administrator." Followed by "The type initializer for "VirtualInfrastructure.Utils.HttpWebRequestProxy" threw an exception."

I may be sticking with my XP VM to run the client . but I am not giving up just yet.

Re: vsphere client on Windows 7 rc

GlenR — Sun, 20 Sep 2009 20:55:28 GMT

Please try the included shortcuts instead, they are installed to the same directory you unzip to.

Glen Rhea – GeoStor Administrator
Arkansas Geographic Information Office - Putting Arkansas on the Map
1 Capitol Mall
2nd Floor 2B 900
Little Rock, AR 72201
501.683.2719 Tel
501.682.6077 Fax
glen.rhea@arkansas.gov<mailto:glen.rhea@arkansas.gov> (Email)
http://www.geostor.arkansas.gov (Web)
Twitter<http://www.twitter.com/kirrilian> | Facebook<http://www.facebook.com/glen.rhea> | LinkedIn<http://www.linkedin.com/in/glenrhea> (Social Media)

Re: vsphere client on Windows 7 rc

robshaw22 — Sun, 20 Sep 2009 20:47:44 GMT

I do not have Visual Studio installed. I am trying the new zip file on both Win 7 RTM and on Win 7 RC Ultimate. I'll let you know what happens.

Re: vsphere client on Windows 7 rc

robshaw22 — Sun, 20 Sep 2009 20:43:36 GMT

Sorry it took so long to respond. I used the original shortcut on the desktop, but modified it to run the batch file in the target "start_viclient.bat".

Re: vsphere client on Windows 7 rc

GlenR — Sun, 20 Sep 2009 08:09:49 GMT

I just triple checked the zip file on a fresh install of W7 (my laptop) with a fresh install of the viclient and everything worked as expected. I did find an issue with the Update batch file, that has been fixed and included with this post.

Do either of you have Visual Studio installed?

Never mind, I think I just figured it out by accident. Are both of you using the provided shortcuts or are you using the one on your desktop? I just found out that if you click the original unmodified shortcut on the desktop the app will crash just like both of you described.

GlenR

Re: vsphere client on Windows 7 rc

GlenR — Sun, 20 Sep 2009 07:34:24 GMT

Thanks modmaven, were you able to implement this without any issues? I'm not sure what is causing the crash issue and I looked on your blog and everything seemed to be correct, just wondering if you followed those same instructions as well.

GlenR

Re: vsphere client on Windows 7 rc

ITFocus — Sun, 20 Sep 2009 07:25:23 GMT

I've just installed for the second time, 'Windows 7 x64', and as before, worked perfectly..

Nigelh

Re: vsphere client on Windows 7 rc

GlenR — Sun, 20 Sep 2009 06:55:44 GMT

I have the exact same setup as you Rob and I'm not really sure what is causing this for you and Don. Does anyone else have any ideas what might be causing this issue?

GlenR

Re: vsphere client on Windows 7 rc

robshaw22 — Sun, 20 Sep 2009 03:39:08 GMT

I also cannot launch the vi client after using the zip file. Same error as donfrank. I extracted the zip file and changed the vi client target to run start_viclient.bat.

Error:

Followed these instructions:

http://modmaven.wordpress.com/2009/09/16/how-to-get-a-vsphere-client-working-on-a-windows-7-rc-or-rtm-machine/

System is Win 7 Enterprise RTM code 64 bit. Build 6.1.7600 Build 7600.

ESXi 4.0.0 host server build 171294. Latest build release to date. Downloaded vi client directly from host.

Re: vsphere client on Windows 7 rc

modmaven — Wed, 16 Sep 2009 17:36:20 GMT

Nice one GlenR! That works great. I have linked to this forum giving you credit, etc. and added a blog post with a step-by-step here...

http://modmaven.wordpress.com/2009/09/16/how-to-get-a-vsphere-client-working-on-a-windows-7-rc-or-rtm-machine/

Re: vsphere client on Windows 7 rc

donfrank — Mon, 14 Sep 2009 22:52:17 GMT

When you say the latest VI 4, do you mean the one from the ESXi server
after it's installed, dated around 5/09?

Don Frank CEO
Open Technologies

donfrank@opentech.biz

Sent from my iPhone

On Sep 14, 2009, at 6:20 PM, "GlenR" <communities-emailer@vmware.com

Re: vsphere client on Windows 7 rc

GlenR — Mon, 14 Sep 2009 22:19:54 GMT

I just uninstalled, reinstalled the latest VI 4, and then ran the zip file, both apps open fine. I am unable to replicate this issue so I don't know what to tell you other than maybe reinstall and try again.

GlenR

Re: vsphere client on Windows 7 rc

donfrank — Mon, 14 Sep 2009 22:07:27 GMT

I have windows 7 64 bit. I clicked the provided shortcut.

Re: vsphere client on Windows 7 rc

GlenR — Mon, 14 Sep 2009 21:42:25 GMT

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.

GlenR

Re: vsphere client on Windows 7 rc

donfrank — Mon, 14 Sep 2009 21:08:54 GMT

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.

Re: vsphere client on Windows 7 rc

tnolan — Wed, 09 Sep 2009 01:02:49 GMT

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.

Re: vsphere client on Windows 7 rc

Staggerleib — Tue, 08 Sep 2009 21:18:40 GMT

Follow the below link for a PowerShell script that does all you need it to do... My compliments to

http://www.tinyint.com/index.php/2009/09/04/vsphere-client-on-windows-7/

Matthew Leib

Re: vsphere client on Windows 7 rc

RickEveleigh — Tue, 08 Sep 2009 20:20:50 GMT

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)

Re: vsphere client on Windows 7 rc

Jainesh — Mon, 07 Sep 2009 00:11:35 GMT

Thank you Fernando for your solution!! Works like a charm!! Thank you very much!

Re: vsphere client on Windows 7 rc

VidarK — Sun, 06 Sep 2009 22:14:24 GMT

Thanks. That zip file worked fine on Windows 2008R2 also!

Re: vsphere client on Windows 7 rc

GlenR — Sun, 06 Sep 2009 04:07:50 GMT

I've updated the zip file to include the workaround for the update client as well.

All you need to do is to unzip it to c:\Program Files (x86)\VMware\Infrastructure\

Glen

Re: vsphere client on Windows 7 rc

GlenR — Sun, 06 Sep 2009 03:47:05 GMT

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

Glen

Re: vsphere client on Windows 7 rc

chjquest — Sat, 05 Sep 2009 21:56:47 GMT

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.

Thanks again!!

BTW, with your permission, I will post your solution on my blog with your name and this link. thanks.

Re: vsphere client on Windows 7 rc

tnolan — Fri, 04 Sep 2009 22:37:43 GMT

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.

http://www.tinyint.com/index.php/2009/09/04/vsphere-client-on-windows-7/

Re: vsphere client on Windows 7 rc

RColbert — Sat, 29 Aug 2009 07:53:48 GMT

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.

-Robert

Re: vsphere client on Windows 7 rc

RagingOtter — Fri, 28 Aug 2009 22:34:02 GMT

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!

Re: vsphere client on Windows 7 rc

evrens — Fri, 28 Aug 2009 22:32:01 GMT

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.

Re: vsphere client on Windows 7 rc

mkremer — Fri, 28 Aug 2009 16:46:29 GMT

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

Re: vsphere client on Windows 7 rc

ConstantinV — Fri, 28 Aug 2009 07:08:58 GMT

When I use it in this way it freezes and hangs about every 30 minutes. Helps only restart of it.

StarWind Software Developer

Re: vsphere client on Windows 7 rc

RParker — Thu, 27 Aug 2009 20:36:16 GMT

Need to note, in some time you will face with lagging.

Define: "lagging"?

I don't see a problem other than the annoyance of having to use this work around, it works identical to native way....

Re: vsphere client on Windows 7 rc

ConstantinV — Thu, 27 Aug 2009 14:09:23 GMT

Need to note, in some time you will face with lagging.

StarWind Software Developer

Re: vsphere client on Windows 7 rc

sjha — Thu, 27 Aug 2009 06:14:08 GMT

I used the workaround provided by Fernando (one for May 24, 2009 8:38 PM) to setup vSphere Client 4.0 on Windows 7 32 bit RTM version few days back. Thanks Fernando, it worked like a charm.

The command-line windows does annoy you though. I would rather like for VMWare to release a windows 7 compatible version of vSphere Client so that one doesn't have to take these manual steps.

Re: vsphere client on Windows 7 rc

jeffalford — Wed, 26 Aug 2009 23:45:51 GMT

64bit Windows 7 Enterprise RTM. The suggestions in this thread worked perfectly. I just did the last one because the cmd prompt annoyed me as well. Many thanks!!!

Re: vsphere client on Windows 7 rc

DSeaman — Mon, 24 Aug 2009 02:25:39 GMT

Given they released an update for vCenter to fix a class A subnet problem, which I think is pretty rare, the glaring problem of W7/2008R2 still exists. Pretty unresponsive if you ask me. The fix can't be THAT difficult!

Re: vsphere client on Windows 7 rc

emm1 — Sun, 23 Aug 2009 22:58:53 GMT

Why does it take VMWare so long to update their products? (N)

Re: vsphere client on Windows 7 rc

AndersNolberger — Fri, 21 Aug 2009 14:36:30 GMT

I have now successfully started the host update utility on a Windows 7 Ultimate 64 RTM. I followed the instructions for the vSphere Client and copied the .config file to the update folder and renamed it to VIUApp.exe.config and and also changed the relevant rows in the cmd file. Everything appears to work. I have not done an update since my ESXi is up to date but no errors when downloading or adding host.

Thanks for this workaround!

Re: vsphere client on Windows 7 rc

Davita — Fri, 21 Aug 2009 03:01:38 GMT

I haven't tried using the host update utility yet, I'm sure someone else may have already tried using it with Win7 - hopefully they can chime in and shed some light on it for you.

Re: vsphere client on Windows 7 rc

D.Rock — Thu, 20 Aug 2009 18:12:33 GMT

I'm curious Davita, can you use the host update utility with this procedure. The "developer mode" method did not eliminate any host update utility problems i came accross. I still get a few errors when I try to run it that are similar to the errors I received before I configured my client for developer mode.

Re: vsphere client on Windows 7 rc

Davita — Thu, 20 Aug 2009 17:36:09 GMT

I tried the procedure above and at first it didn't work. I'm running Windows 7 RTM 32-bit.

The procedure above works, however, before you install the vSphere client, right-click on the installation executable and select troubleshoot compatibility. It will recommend that it runs in Windows XP SP2 compatibility mode. Apply those changes, then run the executable. Once you do that and it installs, perform the steps above and it will work.

Re: vsphere client on Windows 7 rc

brettcarr1 — Wed, 19 Aug 2009 20:46:18 GMT

If anybody is interested unsurprisingly the same problem also exists on Windows Server 2008R2.

Also does anybody know if/when VMWARE will support customisation of Windows Server 2008R2 from a template, I tried building as 2008 and applying a customisation but it doesn't work.

Brett

Re: vsphere client on Windows 7 rc

jefferai — Wed, 19 Aug 2009 19:15:05 GMT

atbnet wrote:
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.

Same problem on Windows 7 RTM.

Consider this a complaint.

Re: vsphere client on Windows 7 rc

ftubio — Mon, 17 Aug 2009 14:58:02 GMT

tcutts wrote:

into_311 wrote:

I am hoping Vmware can release a product update to fix this issue. I'm not excited about changing around dll's and making changes to .net that I might forget to change back later....
You're not changing the system installed .Net. You're only giving the vSphere client its own local copy of the older .Net DLL, so it's a fairly safe change, isn't it?

Tim

This is correct, provided you use the batch file to set the environment variable. Other posters in this thread mention setting DEVPATH in control panel, which does work too, but this means that any .NET program could potentially load assemblies from the vSphere client Lib folder. Of course, for this to happen they would have to have development mode enabled as well.

Incidentally, I got tired of having an additional command prompt window open every time I used the client so I now use a slightly modified batch file from what I originally proposed.

SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
SET PATH="%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\";%PATH%
start /B VpxClient

It now launches the application and then goes away.

Fernando Tubio

Re: vsphere client on Windows 7 rc

AsherN — Fri, 14 Aug 2009 15:34:49 GMT

It's not a rewrite, likely just a recompile against the new DLLs.

Re: vsphere client on Windows 7 rc

D.Rock — Fri, 14 Aug 2009 13:09:13 GMT

You're not changing the system installed .Net. You're only giving the vSphere client its own local copy of the older .Net DLL, so it's a fairly safe change, isn't it?

Tim

Very true, I just copied the good DLL from my vista box to the lib directory. Once that's done the scripts tell vmware to use the dll that's located in the lib directory. Very safe indeed, but I do wonder if VMware can repackage that same DLL with the next version, or if they will have to rewrite the client all together. Probably safer to make a new one i guess.

Re: vsphere client on Windows 7 rc

tcutts — Fri, 14 Aug 2009 12:10:14 GMT

into_311 wrote:

I am hoping Vmware can release a product update to fix this issue. I'm not excited about changing around dll's and making changes to .net that I might forget to change back later....

You're not changing the system installed .Net. You're only giving the vSphere client its own local copy of the older .Net DLL, so it's a fairly safe change, isn't it?

Tim

Re: vsphere client on Windows 7 rc

mbell98 — Thu, 13 Aug 2009 03:55:35 GMT

The client gets launched by executing the .cmd file. It sets the path then calles the client executable.

Re: vsphere client on Windows 7 rc

tsd_david — Thu, 13 Aug 2009 03:52:44 GMT

How you launch the vSphere Client? it should launch with parameter shown before.

As well as use batch file to launch it.

Re: vsphere client on Windows 7 rc

mbell98 — Thu, 13 Aug 2009 03:49:39 GMT

Thanks so much for the solution, Fernando!

Re: vsphere client on Windows 7 rc

GTMK — Wed, 12 Aug 2009 10:03:54 GMT

I've got it... there were (probably through cut & paste) some non-ASCII characters in the VpxClient.exe.config...

Georg.

Re: vsphere client on Windows 7 rc

GTMK — Wed, 12 Aug 2009 09:44:31 GMT

Hmm. I don't get it to work, I always get the message "Configuration system failed to initialize". I have a W7 Enterprise x64, the system.dll is from a W2K3 R2 (x86). Any ideas?

Georg.

Re: vsphere client on Windows 7 rc

JetJaguar — Tue, 11 Aug 2009 20:08:57 GMT

Awesome. Worked for me on Win7 Enterprise 64 RTM. I just have to right click the short cut and run it as administrator.

Thank you very much for the instructions!

Re: vsphere client on Windows 7 rc

D.Rock — Tue, 11 Aug 2009 19:49:21 GMT

I found that if I use this in command prompt it works fine, other users of Windows 7 Professional RTM with UAC off may find this useful as well:

setx devpath "c:\program files (x86)\vmware\infrastructure\virtual infrastructure client\launcher\lib\"

SETX is a more robust version of the set command.

Re: vsphere client on Windows 7 rc

jdiekert — Tue, 11 Aug 2009 09:51:23 GMT

After turning on development mode i get the message "Configuration system failed to initialize", when trying to log in.

Any Idea why?

Thanks in advance.

Jens

Re: vsphere client on Windows 7 rc

tsd_david — Fri, 07 Aug 2009 10:36:33 GMT

Development mode is work on Windows 7 RTM 7600 with out reboot!

Re: vsphere client on Windows 7 rc

Innuendo — Wed, 05 Aug 2009 07:21:15 GMT

RParker wrote:

With Win 7 going RTM on Aug 6, when can we expect a fix for the vSphere client?

well A) VM Ware isn't Microsoft, just because Microsoft has a NEW product release doesn't infer that VM Ware has to support it. B) you CHOSE to use Windows 7, the VI Client works on Vista, XP, 2003. So if you don't want to use the work around, then that is the alternative.

Also releases for new products are not known in advance, we will ALL know at the same time, which is about a day before they come out.

A) lol, yes it does. You meant LEGALLY ? Well, LEGALLY, many things can be ignore since you don't have to follow the market rules...but if you want to survive, you have to follow these rules. VMware have no choice at all : they have to fix this problem for both Seven and 2008 R2 asap (incredible it isn't done yet if you ask me).

B) ppl using Seven aren't chosing the market rules I just dealt with. Many companies started to use Vista and deploy it on their noetwork with the ton of problems everybody is aware of. Now those companies don't want to step back to a 10 years old OS and would like to try the "Vista R2" (real Seven name) which is meant to fix most of the problems (and it fixes them, we all tried it hard time). Don't think everyone chose to use Seven, you are obviously not right here.

Now, the alternatives still exist and the fact XP or even Vista (and server versions of them) are working with new client is still a good work around. But I fail to understand why VMware isn't fixing this right now, this is plain stupid. Sooooo long before you can install client on x64 systems...well, how long before Seven will be supported ?

Very hard to understand why a so tiny change (and IT IS a tiny change, every dev can state here easily) isn't done yet.

Regards.

RParker wrote:

With Win 7 going RTM on Aug 6, when can we expect a fix for the vSphere client?

Also releases for new products are not known in advance, we will ALL know at the same time, which is about a day before they come out.