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

Using compatibility matrix to avoid plug-in compatibility issues (55788)

Last Updated: 9/3/2018Categories: InformationalTotal Views: 8250Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

Plug-in incompatibility can result in client failures

Cause

Third-party plug-ins may be incompatible with certain versions of the vSphere Client or the vSphere Web Client. The Compatibility Matrix allows the end user to control whether a plug-in will deploy on specified client versions

Resolution

To disable and enable plug-ins from deploying on the vSphere Client or the vSphere Web Client, you must edit the compatibility-matrix.xml configuration file. You can locate the file in one of the following directories:

Location of the compatibility-matrix.xml Configuration File:

vSphere Environment Setup

vSphere Client

vSphere Web Client

vCenter Server for Windows

C:\ProgramData\VMware\vCenterServer\cfg\vsphere-ui

C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client

vCenter Server Appliance

/etc/vmware/vsphere-ui

/etc/vmware/vsphere-client

You can define your compatibility rules by inserting a <PluginPackage> element inside the <pluginsCompatibility> element for each plug-in.

For Example:

<Matrix>
<pluginsCompatibility>
<PluginPackage id="com.vmware.example" version="2.7.5" status="incompatible"/>
...
<PluginPackage id="" version="" status=""/>
</pluginsCompatibility>
</Matrix>

The <PluginPackage> element contains the following attributes:

id - The string ID of the plug-in that you want to prevent from deploying or explicitly declare as compatible with current version of the vSphere Client or the vSphere Web Client.

version - The version of the plug-in that you want to prevent from loading. The version is a string in any of the following format:

Version: An exact version, e.g. 2.7.3, 3.5.3, etc. The format allows for maximum of 4 dotted numbers.

Interval: [0, 6.4] or [6.5, 7.0) or (7.5, ). As seen you can use empty strings to mark infinity values. I.e in the example above from v7.5 to infinity.

status - The rule that you want to be applied for the plug-in. The status can be:

incompatible - The plugin is incompatible. Either cannot deploy at all, or if deployed causes us a lot of grief.

compatible - The plugin is compatible, which in other words means: it is expected to work and we are not aware of any major issues (not that there may not be any - simply we don't know them).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Server Appliance を 6.0\6.0a\6.0b から 6.0 U3g にアップグレードすると rpm の更新中にハングする。 (56625)

Results 1-2 of 2

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.7

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant