Yes, I'm alredy using %ProgramFiles(x86)%. here are my files:

VpxClient.exe.config:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.net>
<connectionManagement>
<clear/>
<add address="*" maxconnection="8" />
</connectionManagement>

</system.net>
<appSettings>
<add key = "protocolports" value = "https:443"/>

</appSettings>
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
</configuration>

VpxClient.cmd:

SET DEVPATH="%ProgramFiles(x86)%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib"
"%ProgramFiles(x86)%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"

See error in attach.

Thank You in advance.
Bye

You need to remove the quotes when you set the value of the DEVPATH environment variable. In other words, change

SET DEVPATH="%ProgramFiles(x86)%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib"

to

SET DEVPATH=%ProgramFiles(x86)%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib

Let me know if that helps.

Fernando Tubio

I've been waiting months for this! Thanks!

I am running Windows 7 RC1 x64 - Here is the content of my batch file that works just fine

@echo Off
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"

The config file you have is the same as mine, I believe the wildcard value does not work the same as it does in x86 - I tried several times to simply change directory using wildcards with no luck - so I just simply defined the exact path and it works like a charm

Tony

That is BESIDES the point, Windows 7 will be supported in ESX 4.0 as an OS, won't it? So OBVIUOSLY they knew about it why it DOESN'T work (I don't care to hear that it's BETA, we know its BETA) what is rediculous that the NEW product was released with Windows 7 on the table..

So it should be AT LEAST supported, the previous version of VI Client works fine, and as someone else pointed out, it's not like they completely re-wrote Windows 7, Vista Works, why not Windows 7. It's a continuing example VM Ware doesn't know how to leverage a ... gee ... USER COMMUNITY?!?

Your config file should read as such

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.net>
<connectionManagement>
<clear/>
<add address="*" maxconnection="8" />
</connectionManagement>
</system.net>
<appSettings>
<add key = "protocolports" value = "https:443"/>
</appSettings>
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
</configuration>

Also you will need to insure that you have copied the "System.dll" as mentioned from the OP message -

Read the post from the 1st entry and insure you have the .Net framework dll placed in the folder he stated

I can send you my files directly if need be.

Here is my config file - with luck it will allow it to be attached

Interestingly the problem also appears for ThinApp packaged versions of the vSphere client when run in Windows 7