vsphere client on Windows 7 rc

[brettcarr1]

Has anybody managed to get the vsphere client working on Windows 7, it installed fine but when I try and login to an esx server, I get an error:

Error Parsing the server "192.168.1.10" "clients.xml" file Login will continue contact your system administrator

Clicking ok gives me another error

The type initializer for "VirtualInfrastrcture.Utils.HttpWebRequestProxy" threw an exception

Clicking ok returns me to the login dialogue.

I know Windows 7 isn't released yet but as it's so close I would of thought vmware would of tested it.

Brett

[mealan]

I had to make a BAT file and use run as admin on it, but it works great for windows 7rc x64!

thanks for the help!

[Tonym89]

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

[RParker]

Seems to me that Windows 7 should have been tested and working long before now, its not like its a complete re-write of the operating system.

Seems backwards doesn't it? I have been complaining about this for 2 years, it seems VM Ware doesn't care to include those of us that use this stuff DAILY to test. Makes no sense whatsoever, which would lead one to believe VM Ware isn't interested in TRULY making their products ready, they just care about getting them out, quantity > quality in VM Ware small minded view of the world.

[RParker]

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.

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?!?

[brettcarr1]

Maybe I'm missing something somewhere.

I have this in my config file:

and this in my batch file:

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

but when I run the client (from the batch file and try to connect I get:

Could not connect, please enter a valid server name.

Brett

[Tonym89]

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.

[brettcarr1]

I have the DLL file in place can you send me your config file, I think that is where the problem is.

[Tonym89]

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

[brettcarr1]

Thanks, the config file did the trick, all working now

Brett

[oschistad]

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

[KamiCrazy]

What environment are you using to package the vSphere client using ThinApp?

If the environment you are using already has the .Net Framework installed during the pre-scan then ThinApp is not going to package the needed System.dll required for vSphere to work under Windows 7 because it cannot detect that file has changed.

There are two approaches I would take with ThinApp.

1) After installation use the great workaround provided above. Place the required System.dll and modify the config file. Then modify your DEVPATH environment variable. Once you have made these customisations continue with post-scan in ThinApp and build the package. ThinApp should detect these changes and include them in the package.

2) Build the package on Windows without .Net. Proceed to install .Net after pre-scan so that it can detect the new system system files and include them during post-scan.

[itsupportzagat]

We decided to forego the whole batch file process and set a system variable for 7 x64:

DEVPATH C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Lib

Then it worked fine from launching from the vSphere Client icon.

[CA13]

Thank you for the workaround.. Using Virtual Win XPin 7 RC was my previous one.. and getting vSphere thin client to work there was much more work and useless obfuscation!

[Tonym89]

Your correct - I added the Dev path as a system variable and the original icon works without having to batch it out.

For anyone interested to know the 7137 build runs the vSphere client without the redraw slowness I experienced in the 7100 build, thought it was my video card initially.

(7137 build is not "officially" out by the way)

[oschistad]

Actually I have to modify my previous statement; The RC version of the vSphere client has the client.xml issue when thinapped. But when I build the GA version, it actually crashes at launch when run from Windows 7.

I packaged the app from a WinXP SP3 box with only security hotfixes, and in the capture I did an install of .Net 3.5 (which contains all the older versions), J# (manually) and the vSphere client itself. The resulting package was around 1GB in size

The thinapp runs fine from windows XP but dies on launch in windows 7.

[Tonym89]

apologies for asking what is probably obvious for most of you here, but when you say the "ThinApped" what is and how are you creating this? I am assuming its a packaged hosted app - am I correct in thinking that this would be used in integration mode in XPM under 7?

I simply use the solution posted here to run it natively under 7 x64

Tony

[oschistad]

Well, ThinApp is the VMware product formerly known as ThinStall, which is an application virtualization solution. It does not rely on a virtual machine to run the apps, but instead isolates the application from the underlying OS and presents a virtual filesystem and API to the code running inside. It uses a sandboxing mechanism similar to that found in java, but not quite the same thing.

Of course I could just install the vSphere client locally and be done with it, but packaging it as a thin application makes it portable and install-less, and allows it to run on any windows PC as long as I have the binaries on disk somewhere. Except, as it turns out, on Windows 7

[Tonym89]

That is awesome!, I am way to new to have not to have known about that. I have fully migrated our ESX Hosts and Management infrastructure over to ESX4 / vSphere and something like this would be IDEAL for some of our canned applications for remote users

Researching this now

HUGE THANKS

[oschistad]

Glad to have been of service - I am a big fan of the technology myself

[kdonofrio]

i am unable to get mine working. It is on win7 32 bit. I get the following errors. I have attached them.