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

Replacing the Software Image Profile with an OEM specific one within the same vSphere Version (67959)

Last Updated: 4/2/2020Categories: How toTotal Views: 8871Language:
JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

An ESXi host has been installed with the standard VMware Image Profile, while vendor recommendations are to use the platform specific OEM Custom ISO for installation.

Purpose

To ensure that all OEM specific hardware drivers, plugins and other 3rd party modules are available and are not conflicting with each other, OEM specific Installation ISOs should be used whenever possible.

However, it can happen that a host has been installed with the standard VMware ESXi Installation ISO instead.

This can be rectified without a re-installation (which would add additional work required from saving and restoring the configuration).

This article showcases the required steps and commands.

Impact / Risks

Performing these steps requires an ESXi reboot for every host where the profile will be modified.

Since the list of installed VIBs and their interdependencies will be modified, there is a risk of running on older / non VMware Compatibility Guide listed drivers after the reboot. This needs to be manually verified and if need be, rectified against the HCL again.

Resolution

The below example steps will be using the HPE ESXi 6.5 U2 installation iso. The variable parts in the commands will be marked Bold and Italic.

Obtain the ESXi Installation Offline Bundle for the specific OEM and upload it to a datastore accessible by the hosts that need re-imaging.

Note: Due to the size, /tmp/ usually will not work.

From the ESXi Shell, query the depot zip file for the available profiles:

For example:

esxcli software sources profile list  -d /vmfs/volumes/cs-tse-h74_1/update-from-esxi6.5-6.5_update02.zip

Name                              Vendor        Acceptance Level
--------------------------------  ------------  ----------------
ESXi-6.5.0-20180501001s-no-tools  VMware, Inc.  PartnerSupported
ESXi-6.5.0-20180502001-no-tools   VMware, Inc.  PartnerSupported
ESXi-6.5.0-20180502001-standard   VMware, Inc.  PartnerSupported
ESXi-6.5.0-20180501001s-standard  VMware, Inc.  PartnerSupported

If multiple profiles are available, pick one of them according to your requirements. Usually the OEM Image Profiles contain only a single configuration profile.

Perform the installation of the image profile:

For example:

esxcli software profile install -d /vmfs/volumes/cs-tse-h74_1/update-from-esxi6.5-6.5_update02.zip -p ESXi-6.5.0-20180502001-standard --ok-to-remove
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed:

Notes:

The offline bundle zip file from the above example can be replaced with any OEM ISO as long as it comes in the correct format.

Applying the software profile within the same ESXi version (e.g. 6.5 U2 -> 6.5U2) should not cause any trouble.

Moving from a lower update to a higher Update (6.5 U1 -> 6.5U2) also should not cause problems. However, notice the VIB list - esxi-base and other kernel modules are not included. This is not considered host-patching/upgrading.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

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

KB
•
外部 MS SQL データベースを使用する vCenter Server 6.x から vCenter Server Appliance 6.x/7.x への移行のステージ 2 で「Error while disabling jobs: disable_jobs(cur_odbc, con_odbc, args.rdbms)」と表示される (67697)

KB
•
証明書を置き換えるために Certificate Manager を起動できない (67660)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant