WineHQ

VMware vSphere Client

VMware vSphere Client 4.1

Application Details:

Version: 4.1
License: Retail
URL: http://www.vmware.com
Votes: 2
Latest Rating: Bronze
Latest Wine Version Tested: 1.7.5

Maintainers: About Maintainership

Free Download VMware vSphere Client 4.1.0

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Installer Client application launches

What does not

Unable to connect to server - connection times out

Workarounds

What was not tested

use of application as unable to connect to server

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowUbuntu 13.10 "Saucy" i386 (+ variants like Kubuntu)Oct 28 20131.7.5Yes Yes BronzePeter 
ShowUbuntu 12.10 "Quantal" amd64 (+ variants like Kubuntu)Oct 23 20121.5.15Yes Yes SilverThomas Hood 
ShowArch LinuxOct 18 20121.5.15Yes Yes Silveran anonymous user 
ShowUbuntu 11.04 "Natty" i386 (+ variants like Kubuntu)May 17 20111.3.20Yes No GarbageThomas Hood 
ShowUbuntu 9.10 "Karmic" amd64 (+ variants like Kubuntu)Apr 07 20111.3.17Yes No GarbageThomas Hood 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs

HowTo / Notes

New release
VMware has released version 4.1 Update 1 which has not yet been tested. VMware has released version 5.0 but I was unable to get it installed on an amd64 Ubuntu natty system.

Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

dotnet 2.0sp1
by Peter on Monday October 28th 2013, 14:53
If you're having trouble with the installations for the various dotnets, I had to use the latest version here: winetricks.googlecode.com/svn/trunk/src/winetricks and not the current one that Ubuntu has which is from July
Crashes on Arch-Linux x86-64
by Bar Hofesh on Sunday May 19th 2013, 11:06
Managed to download & install, managed to run, when trying to connect I get an error message: "vSphere Client could not conect to "x.x.x.x"
The server could not interpret the communication from the client"

in the terminal i get this:

"fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program
to use LAN connection/winsock instead!
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
fixme:ras:RasConnectionNotificationW (0xffffffff,0x274,0x00000003),stub!
err:rpc:I_RpcReceive we got fault packet with status 0x80040155
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
p11-kit: couldn't load module: /usr/lib32/pkcs11/gnome-keyring-pkcs11.so: /usr/lib32/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:crypt:CertAddCertificateLinkToStore (0x1cdd48, 0x1cdbc0, 00000004, (nil)): semi-stub
fixme:crypt:CRYPT_RegControl CERT_STORE_CTRL_AUTO_RESYNC: stub
err:ole:CoInitializeEx Attempt to change threading model of this apartment from
multi-threaded to apartment threaded
fixme:crypt:CRYPT_RegControl CERT_STOR"
Console not working
by Benjamin Fras on Friday October 19th 2012, 18:06
I've installed everything as described above and got it working so far on my Ubuntu 12.04 x64 machine.

Everything seems to work fine, except for the console. It remains dark even though it says "vmrc console has successfully reconnected vmware".

Any ideas?
RE: Console not working
by Thomas Hood on Saturday October 20th 2012, 17:53
I tried following the instructions on an amd64 system and got nowhere. Can you please list the steps you took to get vSphere Client installed and running on an amd64 system? Please mention version numbers.
--
Thomas Hood
RE: Console not working
by Benjamin Fras on Sunday October 21st 2012, 4:19
I downloaded the most recent winetricks first and then installed .net 2.0, 2.0 SP1, 3.0, ie6:

winetricks dotnet20
winetricks dotnet20sp1
winetricks dotnet30
winetricks ie6
winetricks winxp

Next I got the vsphere 4.1 package (build 799345) from my esxi server and installed it by using wine 1.4.1. Installation went fine without any errors.

First start of vSphere failed while I tried to connect to the server. I did some debugging and found following error:

couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so

After some troubleshooting I installed libgnutls-dev and upgraded my wine to 1.5.15 using the wine repository.

That's it. Now I can connect to my server and everything works except for the console. This is annoying but not a show stopper as there is a workaround. You can use the native linux vmware-vmrc from the vmware-player or vmware-server instead.
RE: Console not working
by Thomas Hood on Sunday October 21st 2012, 16:15
Thanks very much for the help.

Running 64-bit Ubuntu 12.10 Desktop on a ThinkPad X220 I installed wine1.5 and winetricks. I ran "winetricks dotnet20" and it printed the following.

------------------------------------------------------
Please download dotnetfx.exe from download.cnet.com/Microsoft-NET-Framework-Redistributable-Package-x86/3000-10250_4-10726028.html, place it in /home//.cache/winetricks/dotnet20, then re-run this script.
------------------------------------------------------

The provided URL addresses a download site for the x86 version of .Net, dotnetfx.exe. I downloaded this and put it in /home//.cache/winetricks/dotnet20 and ran "winetricks dotnet20" again. Up popped a dialog box saying "This product is not supported on a 64-bit operating system. Setup will now exit."

What did you do differently?
RE: Console not working
by Benjamin Fras on Sunday October 21st 2012, 16:34
Please check, if the following package is installed:

ii wine1.5-i386:i386 1.5.15-0ubuntu1 Microsoft Windows Compatibility Layer (32-bit support)

Maybe this why you can't install dotnet.
RE: Console not working
by Thomas Hood on Monday October 22nd 2012, 8:05
Yes, wine1.5-i386:i386 is installed here.

Did you also download what was described as the "x86" version of the .NET runtime, with file name 'dotnetfx.exe'?
--
Thomas

$ dpkg -l wine\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Arch Description
+++-===========================================-====================================================================================
un wine (no description available)
un wine-amd64 (no description available)
un wine-gecko (no description available)
ii wine-gecko1.7:amd64 1.7-0ubuntu1~ppa1~preci amd64 Microsoft Windows compatibility layer (embedded web browser)
ii wine-gecko1.7:i386 1.7-0ubuntu1~ppa1~preci i386 Microsoft Windows compatibility layer (embedded web browser)
un wine-i386 (no description available)
un wine-mono (no description available)
ii wine-mono0.0.4 0.0.4-0ubuntu1~ppa1 all Microsoft Windows compatibility layer (.NET compatibility)
un wine1.0 (no description available)
un wine1.2 (no description available)
un wine1.2-gecko (no description available)
un wine1.3 (no description available)
un wine1.3-gecko (no description available)
un wine1.4 (no description available)
un wine1.4-amd64 (no description available)
un wine1.4-i386 (no description available)
ii wine1.5 1.5.15-0ubuntu1 amd64 Microsoft Windows Compatibility Layer (Binary Emulator and Library)
ii wine1.5-amd64 1.5.15-0ubuntu1 amd64 Microsoft Windows Compatibility Layer (64-bit support)
ii wine1.5-i386 1.5.15-0ubuntu1 i386 Microsoft Windows Compatibility Layer (32-bit support)
ii winetricks 0.0+20120912 amd64 Microsoft Windows Compatibility Layer (winetricks)
ii winexe 1.00-0openpcf2~oneiric amd64 Remote Windows command executor
RE: Console not working
by Thomas Hood on Monday October 22nd 2012, 13:59
By starting with

WINEARCH=win32 winecfg

I was able to follow the given procedure and successfully install vSphere Client 4.1.
RE: Console not working
by Thomas Hood on Monday October 22nd 2012, 15:38
And finally after several attempts ending in various different error conditions I was able to start vSphere Client, connect and use it. I can confirm what was reported above, that it mostly works. Thanks again for your help.
Requires dotnet30
by Vince Marsters on Sunday August 22nd 2010, 5:46
To run vSphere Client 4.1 when installed you will also need to install dotnet30 using winetricks
Back