Trying to install VMWare Workstation Player 12.1.1 on a Linux Host (Linux Mint Debian Edition 2) running on an old Dual-Xeon MacPro I can install it successfully and I can also run a Windows guest (Windows 10-64Bit) as a VM.
But if I try to install VMWare tools, I get the following message : "No componenet found on update server".
I guess this is realted to 12.1.1 version of Workstation player.
Because if I downgrade to Workstation Player 12.1.0 and ope the same VM with that one, I can install VMWare tools flawlessly...
Anyone else getting this ?
P.S. : sorry if this has been discussed multiple times already, but a quick look on discussion titles doesn't seem to talk about this...
same here, but on Debian Jessie host and Windows 7 32-bit guest.
Downgraded back to Player 12.1.0 build-3272444, and the error message is gone.
The latest VMware Tools which version 12.1.0 installs is 10.0.5.
Thanks for confirming that I am not the only one in this situation 🙂
Well, Linux Mint Debian Edition is also Jessie based 🙂
So there are two options I guess :
- VMWare forgot to put the VMWare tools on it's server or the link is not correct ;
- we did something wrong when installing in Debian...
I'll do some test and will post back if I find something.
Replying to myself.
After a hard Linux crash (why on earth did I decided to mess with GPU drivers ?) I reinstalled a new Linux system.
Still Debian, but I decided to go adventurous and took the "Strectch" branch, aka "Debian Testing"... which comes before SID (unstable).
I downloaded VMWare Workstation Player 12.1.1 again and installed Windows 10.
After it was done, I tried to install the VMWare tools.
AND IT WORKED 🙂
Info about the product says : 12.1.1 build-3770994...
So maybe check if there's a new really minor build ?
Or maybe the VMWare tools have now been made available on VMWare server ?
Anyways, it's working as it should now 🙂
I've just reinstalled the Player 12.1.1 using the same installer as before, and now the VMware tools were successfully downloaded (version 10.0.6).
So I think the issue was somewhere on VMware servers.