VMware vSphere

 View Only
  • 1.  custom ESXi ISO?

    Posted Oct 31, 2018 04:21 AM

    i just noticed the ESXi customization recently, and realized that some vendors such as HPE are doing this.

    however i don't know much about this so i would like to seek some answers to clarify my doubts.

    1. what is the typical scenario to customize the esxi? to install drivers and VIBs? to optimize performance?

    2. can the "communitysupported" VIBs be inserted to esxi iso?

    3. can the existing VIBs that already embedded in the official ESXi be removed to create a custom ESXi?

    sorry for the dumb question:smileyconfused:



  • 2.  RE: custom ESXi ISO?

    Posted Oct 31, 2018 06:47 AM

    Hello,

    Noting that the difference between normal ESXi package and the customized (per example for HPE) is that the customized one contains additional drivers and features compatible with the hardware (if you heard about HPE SPP per example, it is a package of all HPE HW contains drivers and firmware).

    So using this customized package you will avoid any failure during the installation first, then you avoid problems with all devices and peripherals attached to this servers. also it will be much easier to configure/control/monitor servers with HPE tools embedded in this package.

    And using this ISO package, you can use the HPE Intelligent provisioning to customize the array, increase the performance.

    Please consider marking this answer "CORRECT" or "Helpful" if you think your question have been answered correctly.

    Cheers,

    VCIX6-NV|VCP-NV|VCP-DC|

    @KakHassan

    linkedin.com/in/hassanalkak



  • 3.  RE: custom ESXi ISO?

    Posted Oct 31, 2018 02:28 PM

    Since you asked about HPE, this thread talks a bit about the importance of a custom build:

    HP DL 360p + ESXi 6.X = Failure to launch

    You know how every branded desktop has their custom Windows installs, that come bundled with custom apps and drivers?

    And then there are folks who just like to format a hard drive and put a regular oem install of Windows and leave the Device Manager littered with yellow exclamation marks..

    Same can be said for ESXi builds.

    Not everyone uses HPE, Dell, Lenovo, so anyone that builds their own Supermicro server, must certainly use the generic vanilla build of ESXi and really know what they are doing for VMware drivers for chipsets, raid controllers, physical adapters, etc.

    I have always used HPE, not because I believe they are the best, but simply because they have always supplied Windows Server custom builds, ProLiant service packs that fill your desktop with apps galore. Had they never made HPE ESXi, then surely I would stop my trek with HPE.

    When I install HPE ESXi, it installs straight out of the box on a default install, and within 10 minutes I have it joined to my vCenter and I start deploying templates on it. I don't spend a whole paid day searching for any other extra software that I don't even know about and must learn if they are needed or not.

    The folks at HPE and their building full of interns do all this for me, so I don't have to.

    Just to give you an idea of "drivers" installed:



  • 4.  RE: custom ESXi ISO?

    Posted Oct 31, 2018 05:11 PM

    1. what is the typical scenario to customize the esxi? to install drivers and VIBs? to optimize performance?
    -- We use a customized ISO for installations as you can add latest drivers and patches.  This saves time in the long run as you don't have to update the host once it's installed.  We're a Cisco UCS shop and I'll start with the Cisco base ISO and update the drivers to the latest supported version and update with the patches and I'm good to go.

    2. can the "communitysupported" VIBs be inserted to esxi iso?

    -- Yes

    3. can the existing VIBs that already embedded in the official ESXi be removed to create a custom ESXi?

    --Yes, I have done this also before.  If you're doing network installs this can greatly speed up the installation time.  VMTools package is about have of the space. We repoint our VMtools to a different datastore so we have control on when VMtools versions get updated.  You can also remove unneeded drivers.

    This can all be built using powershell.  This link should get you pointed in the right direction

    https://blogs.vmware.com/vsphere/2017/05/apply-latest-vmware-esxi-security-patches-oem-custom-images-visualize-differenc…