- How to hot-extend VMDK disk over 2 TB with vSphere 7.0 - Fri, May 22 2020
- VMware vSAN 7 Capacity Reporting improvements - Wed, May 13 2020
- VMware SRM 8.3 and vSphere Replication 8.3 - Wed, May 6 2020
Since several releases of VMware vSphere and ESXi, VMware Tools have been separate from the rest of the software suite. As a result, the updates for VMware Tools occur more often.
Admins can deploy a new version of VMware Tools via vSphere Update Manager (VUM) since there is a download as a vSphere installation bundle (VIB).
For smaller installations or individual ESXi hosts, it is also possible to copy the files directly to your host via secure copy protocol (SCP). You can use WinSCP, a popular freeware solution for this job. We'll show you a how-to procedure with screenshots at the end of the post.
Since the previous version, 10.3.0, VMware drivers have been available through Windows Update and Windows Server Update Services (WSUS) to minimize the reboots. All drivers usually built in are available outside of the VMware Tools package itself. VMware has made this switch because of both the VMCI driver available and others like the PVSCSI and VMXNET3 drivers as well.
What's new in VMware Tools 11.0? ^
- VM Tools now have better integration with the Microsoft Update Service. Updated drivers (pvscsi, vmxnet3, and vmci) are available through the same service for Windows Server 2016 and Windows Server 2019. This means Microsoft Update Service will push the new version of these drivers rather than through a VM Tools update.
- Upgraded compiler for VMware Tools drivers to Microsoft Visual Studio 2017.
- Added support for additional driver for AppDefense, so this component has now two drivers. This allows upgrading the AppDefense module without a reboot, and as such, keeping the system protection on.
- A new AppInfo service now publishes information about running applications inside the guest. AppInfo collects the information about running applications inside the guest and publishes the information to a guest variable, which the administrator can query.
- There is also a new capability for a guest admin to control automatic upgrades and add or remove features via a config file. VMware Tools uses a configuration file called conf to configure different operations such as logging, upgrading, entering guest info, and so on. Admins can configure VMware Tools by editing the tools.conf file. An interesting fact is that if you modify the conf file, the changes are immediate as VM Tools checks the config file every five seconds. Check the VMware documentation for a location of this config file in the operating system you're using in your VM.
- New support for GDI hardware acceleration in the WDDM 1.1 driver.
Download: you can download this from https://www.vmware.com/go/tools.
Note: The latest version of VMware Workstation 15.5 and Fusion 11.5 are bundled with the latest versions of VMware Tools v11.0.
How do I check the version of VMware Tools on my ESXi host? ^
For Windows systems: from the console or a remote desktop session, open VMware Tools from the Taskbar and click About.
Or, from the directory located at C:\Program Files\VMware\VMware Tools\ run the command:
Here is the view from the lab.
For Linux systems: From the console, run the vmware-toolbox command from the terminal and click About.
If you want to determine the vmware-tools version, run this command:
Installing or upgrading VMware Tools 11.0 ^
When installing or upgrading VMware Tools 11, you'll notice it installs Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, and 2019 as a prerequisite.
If you are running Windows systems with these components already installed, the installer directly installs the new version of VMware Tools 11.0.
However, when this is not the case, it will install the Visual C++ redistributable first, which makes the installation process much longer.
You can anticipate this by "pushing" the libraries via WSUS if your organization is using them.
How to install VMware Tools 11.0 on an individual ESXi host ^
Each ESXi has a directory called ProductLocker. By default, VMware Tools are stored in this folder. You can change this default behavior so you can have a shared location for VMware Tools. In this way, you only update the latest version in a single location. It's quite interesting if you are running a large cluster of 30 or more hosts; you only need to update this component once. But this configuration is outside the scope of this post.
Let's just simply show which tool to use and how to update a single ESXi host with the latest VMware Tools.
One of the tools we like is a popular freeware tool called WinSCP. You can download this software from this link.
After installing it, connect to your ESXi host and enable SSH. The ESXi host has to have SSH enabled and SSH allowed in the firewall.
Make sure you enable the SCP service on your ESXi host. You can do this after logging in. Go to Manage > Services. Then select the SSH service called "TSM-SSH" and click on Start to start the SSH service.
Now I assume you have already installed WinSCP on your system. If so, start the software, and then connect to your ESXi host via the SCP protocol and provide your root credentials.
And then accept the RSA key details at the first connection. You'll receive a window with a prompt like this one.
After clicking Yes, you'll get the default two-pane window where you can see the ProductLocker folder.
Once you open that folder, you'll see that there are two subfolders:
If you check the VMtools folder you'll see all the ISOs contained within the VMware Tools package you downloaded are there.
Simply copy and replace the older versions of the files.
Final words ^
VMware Tools are important, so keeping them up to date is definitely one of the first good practices that every admin should implement as soon as possible. To maintain VM Tools across a large vSphere infrastructure, the best practice is probably using VUM because you can download a VIB, which you can push to the hosts via the VMware preferred way to maintain the vSphere infrastructure.
For smaller to medium-sized installations, the shared folder way I mentioned will work as well. This small how-to article is useful for really small environments.