Highlighted
Enthusiast
Enthusiast

vsphere client on Windows 7 rc

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

0 Kudos
211 Replies
Highlighted
Immortal
Immortal

as you said since Windows 7 is still in RC, you may have a tough time finding support. I've attached the compatibility matrix just in case

http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf

0 Kudos
Highlighted
Immortal
Immortal

Use Windows XP Mode for Windows 7:

http://community.winsupersite.com/blogs/paul/archive/2009/04/24/secret-no-more-revealing-virtual-win...

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
Highlighted
Enthusiast
Enthusiast

A reasonable solution apart from that Windows 7 is already running in a VM on my mac. Running a VM in a VM to manage some VM's just doesn't seem like a goo idea Smiley Happy

Brett

0 Kudos
Highlighted
Immortal
Immortal

Smiley Happy

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
Highlighted
Virtuoso
Virtuoso

While the XP mode provides a temporary solution it better not last long as trying to manage the console of Virtual Machines through another VM causes a hell of alot of mouse control problems that quickly get very frustrating.

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.

But then again, Virtual Center and the VIC were never vmware's strong point and obviously that trend is going to continue.

0 Kudos
Highlighted
Immortal
Immortal

there are many threads open regarding the inability to run the vSphere Client on Windows 7..... The bottom line is no matter what you do, it won't work.

http://communities.vmware.com/thread/211081

0 Kudos
Highlighted
Expert
Expert

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.

http://www.vmadmin.co.uk/resources/36-virtualcenter/148-vsphereclientserrxml

Andy, VMware Certified Professional / VMware vExpert Award 2009

Help, Guides and How Tos

If you found this information useful please award points using the buttons at the top of the page accordingly.

Andy Barnes VCP / VCA-DT / MCITP:EA / CCIA Help, Guides and How Tos... www.VMadmin.co.uk If you found this information useful please award points using the buttons at the top of the page accordingly.
0 Kudos
Highlighted
Contributor
Contributor

(Apologies if this is posted twice. I had some trouble with the editor and may have accidentally posted the message while editing it.)

Here's a possible workaround for this problem.

1. Obtain a copy of %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll from a non Windows 7 machine that has .NET 3.5 SP1 installed.

2. Create a folder in the Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory (%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib).

3. In the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a <runtime> element and a <developmentMode> element as shown below. Save the file.

<?xml version="1.0" encoding="utf-8"?>

<configuration>

...

<runtime>

<developmentMode developerInstallation="true"/>

</runtime>

</configuration>

3. Create a batch file (e.g. VpxClient.cmd) in a suitable location. In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file. For example,

SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib

"%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"

4. (Optional) Replace the shortcut on the start menu to point to the batch file created in the previous step. Change the shortcut properties to run minimized so that the command window is not shown.

You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.

Note that this workaround bypasses the normal .NET Framework loading mechanism so that assembly versions in the DEVPATH folder are no longer checked. Handle with care.

Fernando

0 Kudos
Highlighted
Enthusiast
Enthusiast

That works a treat - thanks Fernando!

0 Kudos
Highlighted
Enthusiast
Enthusiast

Instead of creating a batch file to load it I set a DEVPATH environment variable instead.

That might not work for everyone though, it depends on whether you have used the developmentmode trick for any other .net applications.

0 Kudos
Highlighted
Contributor
Contributor

Instead of creating a batch file to load it I set a DEVPATH environment variable instead.

That might not work for everyone though, it depends on whether you have used the developmentmode trick for any other .net applications.

Sure. You can globally set the DEVPATH variable but I prefer to do it where it has the least impact. Besides, I don't trust myself to remember the change in a few months (days?) time and this reduces the chance that I will have some left over changes in my configuration.

Regards,

Fernando Tubio

0 Kudos
Highlighted
Contributor
Contributor

Thanks! That worked like a charm!

0 Kudos
Highlighted
Contributor
Contributor

this doesn't work for me. I'm using windows 7 rc0 ultimate x64... I've changed vsphere.exe.config but when I launch vsphere.cmd I get usual error "the application stop working"...

Any advice?

Thank You

0 Kudos
Highlighted
Contributor
Contributor

If you are using x64, replace all references to %ProgramFiles% with %ProgramFiles(x86)% in the steps that I described previously. Let me know if that helps.

Fernando Tubio

0 Kudos
Highlighted
Contributor
Contributor

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

VpxClient.exe.config:

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

0 Kudos
Highlighted
Contributor
Contributor

Can anybody possible upload such a system.dll file to a fileexchange síte ?

0 Kudos
Highlighted
Contributor
Contributor

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

0 Kudos
Highlighted
Contributor
Contributor

ok ,I've removed quotes and run as administrator. now it works. Thanks again for your support!

bye

0 Kudos
Highlighted
Contributor
Contributor

I've been waiting months for this! Thanks! :smileygrin:

0 Kudos