Renamed VMware Tools components and automatic installation

With the release of vSphere 6.0 and a recent update for the 5.5 VMware Tools on May 8th 2015 (9.4.12 build 2627939), VMware also changed the Windows VMware Tools installer slightly by renaming some vShield-related components:
VMware ESXi 5.5, Patch ESXi550-201505402-BG: Updates tools-light

The vShield Endpoint drivers are renamed as Guest Introspection Drivers and two of these drivers, NSX File Introspection Driver (vsepflt.sys) and NSX Network Introspection Driver (vnetflt.sys), can be installed separately now. This allows you to install the file driver without installing the network driver.

If you’ve been using custom automated installations of the VMware Tools like me then you might have to adjust the installer command for newer tools versions.

The old Windows VMware Tools component list looked like this:
(You can get the software script that displays detailed components information here.)

C:\install>cscript software.vbs "VMware Tools" F
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

---Features in product {5DB26083-3561-4205-9D14-BFE56F2F091E}---
PVSCSI {Drivers} = Local
VMXNet {Drivers} = Local
VMXNet3 {Drivers} = Local
VSS {Drivers} = Local
Perfmon {Toolbox} = Local
TrayIcon {Plugins} = Local
Microsoft_x86_Dll {Common} = Local
Common = Local
Drivers = Local
MemCtl {Drivers} = Local
Mouse {Drivers} = Local
MouseUsb {Drivers} = Local
SVGA {Drivers} = Local
VMCI {Drivers} = Local
Toolbox = Local
Plugins {Toolbox} = Local
Audio {Drivers} = Uninstalled
BootCamp {Drivers} = Uninstalled
Hgfs {VMCI} = Uninstalled
VShield {VMCI} = Uninstalled
Unity {Toolbox} = Uninstalled

With these components, I used the following installer line for an unattended installation:

VMware-tools-9.4.10-2092844-x86_64.exe /v /qb-! REINSTALLMODE=vomus ADDLOCAL=All REMOVE=Hgfs,WYSE,Audio,BootCamp,Unity,VShield REBOOT=ReallySuppress

Note: I’m using the /qb-! option that will perform an automatic installation while still showing basic installer progress bars. This is in order for users (usually VM owners) to be able to track the process and see if anything went wrong while still not having to manually select/click anything. The Tools package accepts basic Windows installer switches. For a completely silent automatic installation, replace /qb-! with /qn.

However, the new 6.0/latest 5.5 Tools have these slightly different components:

C:\install>cscript software.vbs "VMware Tools" F
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

---Features in product {5A16DD24-E486-4347-9D44-9555ABD5B1C5}---
PVSCSI {Drivers} = Local
VMXNet {Drivers} = Local
VMXNet3 {Drivers} = Local
VSS {Drivers} = Local
Perfmon {Toolbox} = Local
TrayIcon {Plugins} = Local
Microsoft_x86_Dll {Common} = Local
Common = Local
Drivers = Local
MemCtl {Drivers} = Local
Mouse {Drivers} = Local
MouseUsb {Drivers} = Local
SVGA {Drivers} = Local
VMCI {Drivers} = Local
Toolbox = Local
Plugins {Toolbox} = Local
Audio {Drivers} = Uninstalled
BootCamp {Drivers} = Uninstalled
Hgfs {VMCI} = Uninstalled
FileIntrospection {VMCI} = Uninstalled
NetworkIntrospection {FileIntrospection} = Uninstalled
Unity {Toolbox} = Uninstalled

The installation will quit with an error if you use the old component names with the newer VMware Tools installer, so these have to be adjusted accordingly:

VMware-tools-9.4.12-2627939-x86_64.exe /v /qb-! REINSTALLMODE=vomus ADDLOCAL=All REMOVE=Audio,BootCamp,FileIntrospection,Hgfs,NetworkIntrospection,Unity REBOOT=ReallySuppress

 

Getting the latest VMware Tools

I’m using dedicated single-file installers from the public VMware Tools Repository, but the above also works with the setup.exe on the VMware Tools ISO CD that is mounted into the GuestOS when you install/update VMware Tools through the host.
This method is handy since the VM owners can update the VMware Tools themselves without needing to access the vSphere infrastructure via a Client.

You can get the latest and greatest, as well as all older VMware Tools versions from VMware directly from this repository without having to download or even install ESXi patches (though you should definitely do that regularly).
I recommend everyone to use the latest Tools VMware has published regardless of your ESXi/vSphere version. As you can see in the official VMware Product Interoperability Matrixes, running newer VMware Tools versions on older ESXi hosts is fully supported:

VMware Tools Support

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s