...
Updating VMware Tools using either the Automatic or Interactive option fails with the error "The required VMware Tools ISO image does not exist or is inaccessible. vix error code = 21001.The advanced configuration "isolation.tools.autoInstall.disable = "TRUE" has been added to the virtual machine. The vmware.log contains the following errors: 2018-04-25T13:22:28.018Z| vmx| I125: ToolInstall: Tools installation failed due to isolation setting.
The advanced setting "isolation.tools.autoInstall.disable = TRUE" will block communication to the virtual machine regarding the VMware Tools installation.
When this advanced configuration is set to "TRUE" VMware Tools must be installed manually.
This is expected behavior when this advanced configuration is set to "TRUE". Both Automatic and Interactive tools upgrades will fail. Per the vSphere 6.5 Security Configuration Guide, this advanced configuration is no longer required in vSphere 6.5. Check the vSphere 6.5 Security Configuration Guide for more details.To disable this setting:Edit the vmx file of the VM: Power down the affected VMConnect to the host the VM is running on via SSHFind the vmx file of the VM using the below command: find /vmfs/volumes -iname *.vmx open the vmx file in your preferred editor and remove the entry below: isolation.tools.autoInstall.disable = "TRUE" Use the vSphere Client: Power down the affected VMRight click the affected VM and select Edit Settings...Select VM OptionsExpand Advanced > Configuration ParametersSelect EDIT CONFIGURATION...Set the value of key isolation.tools.autoInstall.disable to FALSESelect Ok
vSphere 6.5 Security Configuration Guidehttps://blogs.vmware.com/vsphere/2017/06/secure-default-vm-disable-unexposed-features.htmlhttps://blogs.vmware.com/vsphere/2017/04/vsphere-6-5-security-configuration-guide-now-available.html
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.