A: More than anything the decision to change VMware Tools to a 'Security Patch' in Protect's scans is based on the fact that it is a requirement to have the latest version of VMware Tools installed on guest operating systems to be able to use the full functionality of patching hosted VM's using Protect, especially offline VMs or templates.

Since this is a requirement for Protect's features to work - we consider these updates important enough to be included in Security patches.

However, you can get an easy overview by looking at my ESXi Patches site which summarizes all updated VIB packages of every ESXi (5.x and 6.0) patch and provides links to all those KB articles.

As examples you will find that the release notes of the VMware Tools embedded in ESXi 6.0 U1 are in KB2124717, and the release notes of those embedded in ESXi 5.5 U3 are in KB2110233.

Making version 10.0 available as a "stand-alone" download with its own Release Notes page is supposed to change this.

But, well, the original assumption is wrong: For every updated VIB package of ESXi VMware publishes a dedicated KB article that describes the updates.

And that is also true for the tools-light VIBs that represent the embedded VMware Tools package of ESXi.

You can consider these KB articles release notes, but VMware makes them really hard to find.A: VMware Tools assessment in v Sphere is comparing against the local version on the hypervisor the VM resides on. Often, it will help if you perform a Hypervisor bulletin scan and deployment to correct these inconsistencies.As long as your patch definitions in Shavlik Protect are up to date the scan information from Protect should be correct in this regard. The VMware Tools versions should be backward compatible with all product supported versions.VMware has to make it backward compatible since there may be mixed hypervisor versions on the same v Center and DRS can move VMs from one host to another.We recently downloaded ESX 3.5 U4 and would like to begin testing and then deploying to production servers.