Download Vmware Tools 10.0.12

[Cesar Sergeantson]

Similarto what Rod mentioned above, you can look into Veeam ONE as a monitoring and reporting tool for your virtual machines. Feel free to check it out: Free IT Monitoring and Reporting Tool - Veeam ONE Community Edition

@ Rickatron and Kristen: I do have Veeam One (trial license) installed. The result of me stopping the VMware tools service on a specific VM did not trigger a specific alert (out of the box configuration). It only registered this under task/events same as vCenter. I am sure that I can customize an alert but for the moment I will leave third party tools aside.

Hey all, been a MS junkie my whole life and decided to escape ?

(but I need to do this in baby steps so that I can keep on working...)

I run VMWare on my machine and just installed Solus Budgie 4.1. Went to install the VMWare Tools (the ones that launch from VMWare itself), but no joy. I kept getting an error about the init directories, not being able to locate the directory rc0.d/.

I actually searched the drive and couldn't find any of these rcxx.d directories.

I'll look into it and try it, but I feel this is something that should just work. Leave me to play with it for a bit, but otherwise, regretfully as I've read LOTS of good things about SOLUS, I'll need to look at another linux flavour.

maddogdean I previously used the repo package on 3 separate Solus 4.1 Budgie machines running on an ESXi host. I'd first recommend the commands listed by SuperJC710e If that doesn't work, reboot the VM. Also you said in your first post "tools are inoperative." Can you be more specific about which tool was inoperative?

Leandros_Adigard

Thanks for the advice and sorry not to be clear. The tools that are inoperative (or specifically the one I need) are the ability to resize the VMWare window. It always defaults back to whatever the hard setting as in Displays > Resolution.

Note: With the other Linux OS's I've run in VMWare, I am able to dynamically able to resize the display by dragging the corner of the window

Also, the VMWare Tools allows for drag & drop of files to and from the host - this isn't working.

Dear forum users,

I carefully read each post vs my vmware folder shareing problem under Solus xfce OS and finally I get SHAREFOLDER works as describes the follows:

It is confirmed that after install open-vm-tools, the daemon as service would be start with the system startup, but no shared folder though I've setup a win10 folder namely QFTPsvrRoot at vmware configuration tab. At the /usr/bin of Solus, I found a routine called vmware-hgfsclients and executed with a result of the shared folder name QFTPsvrRoot. At the stage, I found Solus already got Win10 folder, and what I have to do is to make it accessable at the Solus. So, try another routine at /usr/bin namely vmhgfs-fuse by typing vmhgfs-fuse --help, and then a short help context appears. I did accordinly as "sudo -S vmhgfs-fuse .host:/QFTPsvrRoot /mnt/hgfs -o allow_other -o nonempty -o auto_unmount" provided a hgfs folder hgfs was created under /mnt. After this, QFTPsvrRoot folder is ready at /mnt/hgfs. So, I modified the statement line as "echo [root passwd] sudo -S vmhgfs-fuse .host:/QFTPsvrRoot /mnt/hgfs -o allow_other -o nonempty -o auto_unmount".

As systemd is a complete new kernel module other than sysV, vmware tools is no longer support for the guest OS, and instead open-vm-tools is suggested by vmware. Actually, one may just install xf86-video-vmware package in the guest OS terminal, the Solus screen will then works fine.

What issue are you seeing, what is it you are trying to achieve? There are options in the policy that will allow you to add exceptions, but it helps to understand what you are trying to achieve and what Lockdown is preventing.

When I have to upgrade vmware tools and I load the ISO installer to upgrade them Lock Down blocks the MSI. I am just seeing if anyone else has worked through this? Does Lock Down block all ISO's loaded virtually as a CD-ROM?

I do not understand why it works directly after installing the VM and then it does not work anymore after restarting the machine ( after the restart I have the vmware-tools script in the /etc/init.d/ folder )

But I still have the problem that it does not work anymore if I restart the computer (without doing anything after the installation only direct reboot) and as you see in my Question I cant get it to run.

Should I necropost or not, but after adding this line guest tools seems to be installed, mouse is grabbed and a vmware- tools are avaliable, but screen is not resizing, as well as fit guest now option is doing nothing

I have a Nixos install with plasma without any changes

Hi,

Just trying to understand if vmtools installation is a requirement to be able to build a VMs on ESXi. I can understand it when DHCP IP address is in use then to be able to connect back VM IP should be somehow exctracted but what about static IPs? Even when I build a Linux VM with static IP and ssh_host defined packer doesnt use it. This is different from Hyper-V when ssh_host with static IP is working without I install hyperv-daemons.

In my case I had to install vmtools, since I have not found any other solution. If you dont want to use vmtools another workaround might be is just to use Vmware Workstation to build the image, you can configure Vmware HW version for compatability and at the end export image to OVF. In Vmware Workstation I was able to build images with static IP and ssh_host.

Hope it helps.

Thank you for your response. In your case, how do you run the vmtools installation?

I have tried several ways to run the vmtools installation on Debian 10 and CentOS 8 and I have not been able to get it to work.

for centos7 I used ks.cfg file with dhcp or static IP and then part of the %post I used yum -y open-vm-tools to install vmtools package and systemctl to enable it, then after packer reboots the VM it can extract IP and use it to connect by ssh.

I just downloaded, installed, and configured iLO Amplifier Pack version 1.30 which is the newest. We want to use the Amplifer Pack to add our HPE servers into Infosight. This downloads as an OVA file that can be pulled into ESXi. I pulled it into ESXi 6.7 Update 1 and when completed it said that this VM did not have VMWare Tools installed.

VMWare's best practice is to have VMWare Tools installed on all VMs. I have loaded quite a few pre-made VMs into VMWare via OVA files. Typically the makers of the appliance (OVA) file install VMWare Tools before packaging up the VM. It appears there is no way for the end user to install VMWare Tools because you cannot get to the unix/linux command line for this product. Why doen't HPE have VMWare Tools already installed?

For every other OVA file I have pulled into ESXi, vmware tools has already been installed by the maker of the OVA or in one case I was able to get to the linux command line and install vmware tools myself

The iLO Amplifier Pack is an advanced server inventory, firmware and driver update solution that enables rapid discovery, detailed inventory reporting, firmware, and driver updates by leveraging iLO advanced functionality. The iLO Amplifier Pack performs rapid server discovery and inventory for thousands of supported servers for the purpose of updating firmware and drivers at scale.

Request for integrating VMware tools will have to be made to the Developers. There may be plans to integrate the VMware tools in the iLO Amplifier pack in future based on the requirement, however there is no ETA on it for now.

What design criteria would exclude installing VMWare Tools? VMWare recommends that all VMs have VMWare Tools installed. The vmxnet3 driver and pviscsi controller have better performance than the E1000 driver and LSI Logic Parallel controller that the Amplifier Pack uses. For this reason alone I would think HPE would want to include VMWare Tools with the Amplifier Pack.

VMware Tools is a suite of utilities that enhances the performance of the virtual machines guest operating system and improves management of the virtual machine. Without VMware Tools installed in your guest operating system, guest performance lacks important functionality.

While virtual machines do run without VMware Tools installed, they run much more smoothly with VMware Tools installed, in part because they can use VMware-specific drivers (like vmxnet3) instead of having to use emulated hardware ones. This leads to better performance, less virtualization overhead, less drain on the host, and better management of the virtual machine.

The VMware site says "VMware Tools is a suite of utilities that enhances the performance of the virtual machines guest operating system and improves management of the virtual machine. Without VMware Tools installed in your guest operating system, guest performance lacks important functionality. Installing VMware Tools eliminates or improves these issues...Although the guest operating system can run without VMware Tools, many VMware features are not available until you install VMware Tools." =en_US&cmd=displayKC&externalId=340

I want to perform a backup and replication of the VM, using Veeam. When VMware tools are installed, the VM can be quiesced, so that the backup/replica is in a consistent state, should I ever need to use them.

I have the same config as topic starter. I also would like to backup the FortiMail VM using Veeam, therefore the use of VMWare tools is a necessity. Also on behalf of the topic starter I would like to repeat the question: are there any guidelines as to how to install VMWare tools on the Fortimail VM?

3a8082e126