How to upgrade ESXi 6.5 to ESXi 6.7

VMware

VMware released ESXi 6.7 a little while ago, but it’s only been here recently have I started deploying it in my home and work lab environments. Below are two ways to easily upgrade your ESXi 6.5 hosts to ESXi 6.7 using the command line or by using the VMware ESXi offline bundle.

How to update ESXi 6.5 to 6.7 via command line

  1. Place the host you are about to upgrade into Maintenance Mode.
  2. Now SSH into the host using PuTTY (or any other SSH client/terminal).
  3. Type the following command to open the firewall for outgoing HTTP requests: 
    esxcli network firewall ruleset set -e true -r httpClient
  4. Type the following command to upgrade to the latest ESXi 6.7 Build 9484548 (latest as of writing) 
    esxcli software profile update -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.7.0-20180804001-standard
  5. After the update has finished disable the HTTP firewall rule by typing: 
    esxcli network firewall ruleset set -e false -r httpClient
  6. And finally, reboot the ESXi host to complete the upgrade. 
    reboot

Once the host comes back online, remove it from Maintenance mode and you’re good to go. It also wouldn’t hurt to also disable SSH when you’re done, for security purposes.

Tip: To view a list of all available ESXi profiles type the following in your SSH session:

esxcli software sources profile list --depot=https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

How to upgrade VMware ESXi 6.5 to ESXi 6.7 using an Offline Bundle

Using the offline bundle works similar in the way of the command line but saves you from having to re-download the upgrade file for each VMware ESXi host. This is nice when you have more than just a couple hosts or limited bandwidth.

  1. First download the ESXi 6.7 offline bundle zip file.
    VMware ESXi 6.7 offline bundle
  2. Upload the VMware-ESXi-6.7.0-8169922-depot.zip file to a datastore that is accessible by all your host(s).
    VMware ESXi 6.7 datastore
  3. Next place the host you plan on upgrading into Maintenance Mode.
  4. SSH into your host using PuTTY (or other client/terminal).
  5. Type the following command, replace “DATASTORE” with the name of your datastore you uploaded the VMware-ESXi-6.7.0-8169922-depot.zip file to. 
    esxcli software vib update -d /vmfs/volumes/DATASTORE/VMware-ESXi-6.7.0-8169922-depot.zip
  6. Once the above completes reboot your host by typing: 
    reboot

Once the host has rebooted, take it out of Maintenance Mode and move on to your next host. That’s it!

Similar Posts

  • VMware vSphere 7 announced

    VMware
    0 Comments

    VMware vSphere 7

    Some pretty big news coming out of VMware today. The announcement of VMware vSphere 7 to become available May 1, 2020! One of the biggest item coming out of this news so far is that vSphere 7 will come in two options.

    The first being vSphere 7 as we all have known it to be for years and then the second being vSphere 7 with Kubernetes which will be available through VMware Cloud Foundation and is a new generation of vSphere for containerized applications.

    Other notables is that the flash based vSphere client is FINALLY no more! From here on out, only the HTML 5 will exist. vCenter Server on Windows will also finally be put to rest and new deployments of vCenter server will be done using the tried and tested vCenter Server Appliance (VCSA) based on PhotonOS linux.

    Read More “VMware vSphere 7 announced”

  • How to fix “SRA command discoverArrays failed” in SRM with RecoverPoint

    VMware
    2 Comments

    Recoverpoint SRA command discoverArrays failed

    We’ve ran into an issue trying to get VMware SRM and SRA 2.2.0.3 along with EMC Recoverpoint 4.1.2 to communicate with one another and would receive this error in SRM:

    SRA command discoverArrays failed. Failed opening session for user to site mgmt IP.

    Please see server logs for further details.

    After some digging around a bit and talking with the Storage Team and EMC we found out that this is due to the SRA’s using HTTP by default and Recoverpoint 4.1.2 does not accept HTTP, but instead only accepts HTTPS or port 443. The steps below is how to get everything to default HTTPS and then communication will resume.

    Read More “How to fix “SRA command discoverArrays failed” in SRM with RecoverPoint”

  • How to upgrade vCenter server appliance

    VMware
    2 Comments

    Prior to VMware vCenter Server Appliance 6.x, upgrading or patching vCSA was as simple as a few button clicks in the appliance UI. Gone are those days, as VMware has replaced the appliance UI with a DCUI and the web based install wizard during setup.

    The good news is, upgrading or patching the vCSA 6.x is still pretty simple via the command line!

    Read More “How to upgrade vCenter server appliance”

  • Easy ESXi 5.5 upgrade via command line

    VMware
    17 Comments

    ESXi 5.5 was just released general availability (GA) on Sunday (9/22) and I’m itching to upgrade the home lab to run the latest version with all it’s goodies. I wanted to try upgrading my hosts without having to go through the same process that I followed setting up ESXi on the NUC in the first place, injecting custom NIC drivers, etc.

    Enter the command line…

    1. Move all VM’s from the host and then put the host into Maintenance Mode.
    2. Go to the Configuration tab > Security Profile and Enable SSH under Services.
      ssh enabled
    3. Under Firewall, enable httpClient (outbound http).
      httpClient enable
    4. Open PuTTY (or other SSH client) and SSH into your host.

      5. Read More “Easy ESXi 5.5 upgrade via command line”

  • VMware ESXi 5 fails to install on Intel NUC, “No Network Adapters” error

    Home Lab
    0 Comments

    If you use the VMware ESXi 5 ISO image and try to install it on an Intel NUC you’ll receive the following error during the install.

    No Network Adapters

    No network adapters were detected. Either no network adapters are physically connected to the system, or a suitable driver could not be located. A third party driver my be required.

    Ensure that there is at least one network adapter physically connected to the system before attempting installation. If the problem persists, consult the VMware Knowledge Base.

    The “No Network Adapters” on the Intel NUC error message during the ESXi install is because VMware removed a number of drivers (non-enterprise drivers) from their ESXi 5.x image and in order to use the Intel NUC as an ESXi host you need to create a customized ESXi image with the NIC drivers added to the image.

    Read More “VMware ESXi 5 fails to install on Intel NUC, “No Network Adapters” error”

  • Thank you VMware Community!

    VMware
    0 Comments

    VMware vExpert 2014

    So far, 2014 has been a very rewarding year for a number of reasons, two of which has happened in just a week or two span. First, Eric Siebert (@ericsiebert) announced on March 27th, this years results of the 2014 Top VMware & Virtualization Blog voting. My first year entered into voting and made it to 71st place! A huge thanks goes out to not only Eric but just as much so to everyone who voted for me!

    To top it off, yesterday VMware announced 2014’s first quarter VMware vExpert list. While vExpert isn’t a technical certification or even a general measure of VMware expertise. The VMware judges selected people who were engaged with their community and who had developed a substantial personal platform of influence in those communities. There were a lot of very smart, very accomplished people, even VCDXs, that weren’t named as vExpert this year. VMware awarded this title to 754 people this year and on that list of many impressive names you’ll find yours truly, Michael Tabor!

    I’m both honored and humbled by both lists. It’s a great feeling to be recognized by not only my peers through the voting in the Top vBlog but also by VMware themselves through the vExpert title.

    So again THANK YOU very much to the entire VMware community, a spectacular community indeed, and congratulations to everyone else that made the Top vBlog and vExpert lists!

Leave a Reply to RODRIGO TRALESKI Cancel reply

Your email address will not be published. Required fields are marked *

10 Comments

  2. Hello,
    I have esxi running remotely on commodity hardware. Unfortunately, the esxi web interface does not even show me the board type.
    Will the upgrade procedure check hardware support or do I risk having a dead server after upgrade?

    Reply

  4. Does this same process apply if vCenter is installed.? Do you simply update each host manually and it won’t break anything with vCenter? I’ve never done a upgrade to existing setup with vCenter, only fresh setups.

    Reply

  5. Whoops. It doesn’t seem to see my datastores any longer and all the machines have been renamed to two digit numbers. Looks like I’ve got a bunch of work ahead of me. :(

    Reply

    1. It’s happened with me too! I don’t whether this procedure is correct. For my luck, I’m doing that on the test machine.

      Reply

  7. Sometimes when you updates old version you get the error “Could not find a trusted signer.”
    Why – ask VMWare ?!

    Solution – try with esxcli –no-sig-check

    Reply