Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Tools Interactive upgrade fails when "isolation.tools.autoInstall.disable"= "TRUE". (56396)

Last Updated: 2/20/2020Categories: TroubleshootingTotal Views: 34993Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Symptoms

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.

Cause

The advanced setting "isolation.tools.autoInstall.disable = TRUE" will block communication to the virtual machine regarding the VMware Tools installation.

Impact / Risks

When this advanced configuration is set to "TRUE" VMware Tools must be installed manually.

Resolution

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 VM

Connect to the host the VM is running on via SSH

Find 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 VM

Right click the affected VM and select Edit Settings...

Select VM Options

Expand Advanced > Configuration Parameters

Select EDIT CONFIGURATION...

Set the value of key isolation.tools.autoInstall.disable to FALSE

Select Ok

Related Information

vSphere 6.5 Security Configuration Guide

https://blogs.vmware.com/vsphere/2017/06/secure-default-vm-disable-unexposed-features.html

https://blogs.vmware.com/vsphere/2017/04/vsphere-6-5-security-configuration-guide-now-available.html

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

Related Versions:

VMware vSphere ESXi 6.5

VMware vCenter Server 6.5.x

Take Our Survey

Support Assistant