How to update VMware ESXi 6.7 to 6.7 Update 1

To go along with the newly released VMware vCenter 6.7 Update 1 release, comes VMware ESXi 6.7 Update 1 as well.

As you might expect with an Update 1 release there are a number of patches, fixes and new additions with ESXi 6.7 U1. If you haven’t already seen, check out the release notes here.

Below are two ways to easily upgrade your ESXi 6.0-6.7 hosts to ESXi 6.7 U1 using the command line or by using VMware Update Manager.

However, before upgrading any of your VMware ESXi hosts, you should have already upgraded your VMware vCenter Server Appliance to 6.7 Update 1.

If you are running VCSA 6.5 you can find instructions on how to upgrade VCSA 6.5 to 6.7 U1 as well.

How to update ESXi 6.7 to 6.7 Update 1 via command line

  1. Place the ESXi 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:
    upgrade esxi allow http firewall

    esxcli network firewall ruleset set -e true -r httpClient
  4. Type the following to download and upgrade to ESXi 6.7 U1
    upgrade esxi update esxi 6.7 u1

    esxcli software profile update -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.7.0-20181002001-standard
  5. After the update has finished disable the HTTP firewall rule by typing:
    upgrade esxi block http firewall

    esxcli network firewall ruleset set -e false -r httpClient
  6. Finally, reboot the ESXi host to complete the upgrade.
    reboot

Note: Once the reboot is completed, I would also recommend disabling SSH on the host for security purposes.

How to upgrade VMware ESXi 6.0-6.7 to ESXi 6.7 U1 using VMware Update Manager (VUM)

You will need the ESXi 6.7 U1 ISO, so download that now if you haven’t already.

  1. First log into your VCSA and click on Update Manager.
    upgrade esxi 6.7 vum
  2. Next click on ESXi images and then IMPORT.
    upgrade esxi 6.7 import image
  3. Browse to the location where you saved the ESXi 6.7 U1 ISO.
    upgrade esxi 6.7 upload image
  4. Once the import completes, select the new image and click on New Baseline.
    upgrade esxi 6.7 new baseline
  5. Give your new baseline a name and description and ensure the new ESXi 6.7 U1 image is selected and click on Finish.
    upgrade esxi 6.7 baseline details
  6. Now we need to attach the new baseline to our hosts. I’m going to add the baseline to the Cluster by selecting the Cluster (#1), then going to the Updates tab (#2), clicking on Host Updates (#3) and finally Attach (#4).
    upgrade esxi 6.7 attach baseline
  7. Select the newly created baseline that you created from above and click on Attach.
    upgrade esxi 6.7 attach baseline cluster
  8. Next click on the Overview link in VUM and then click on Check Compliance.
    upgrade esxi 6.7 vum check compliance
  9. Once the compliance scan finishes, it’s time to actually do the ESXi 6.7 U1 upgrade. From the Updates tab, click on Host Updates, select the baseline and then click on Remediate.
    upgrade esxi 6.7 vum remediate
  10. Accept the EULA and review the host that’s about to be upgraded. If everything looks good, click on Remediate.
    upgrade esxi 6.7 vum remediate confirm

That’s it!

At this point VUM will move any VM’s off of the host (if DRS is enabled) and put the host into maintenance mode and start the upgrade and reboot the host automatically.

If you wish you can also schedule the upgrades via VUM if you don’t wish to remediate them right away.

Similar Posts

  • VMware Site Recovery Manager 8.2 – No more Windows

    VMware has just announced the release of Site Recovery Manager 8.2. There are a number of new items in SRM 8.2, such as enhancements to the HTML5 user interface, support for vSphere 6.7 Update 2, but most notably is Site Recovery Manager 8.2 virtual appliance!

    No more Microsoft Windows license needed! The SRM 8.2 virtual appliance runs on the Photon OS distro, which is similar to what the vCenter virtual appliance has been running on for years now.

    Read More “VMware Site Recovery Manager 8.2 – No more Windows”

  • VMware Update Manager U3e upgrade failing? Un-install it!

    VMware Update Manager U3e error

    I was recently upgrading a VMware environment from vCenter Server Update 3b to Update 3e and during the scheduled change I had also planned on upgrading VMware Update Manager to Update 3e and ran into the following error:

    VMware Workstation unrecoverable error: (vthread-3)
    GetProcAddress: Failed to resolve ENGINE)load_aesni: 127
    You can request support.

    Looking for a possible solution at the VMware Knowledge Base came back with no results and to error message wasn’t overly useful either with “VMware Workstation unrecoverable error: (vthread-3)” as Workstation wasn’t installed on this server.

    Read More “VMware Update Manager U3e upgrade failing? Un-install it!”

  • How to install VMware Workstation 10 on Linux Mint 17.1

    vmware workstation 10 linux mint

    Two goals that I would like to achieve this year is to learn how to program (likely Python) as well as learn more about Linux. So last week I completely wiped my HP laptop that used to run Windows 7 Pro and installed Linux Mint 17.1. However, I had a nested ESXi lab within VMware Workstation when I was running Windows and wanted to do the same on my new Linux install.

    I found this wasn’t just as simple as downloading an .exe and running the file, like it is in Windows. There are a few dependiences that are needed first, below is the steps I took to install VMware Workstation 10 on Linux Mint 17.1.

    Read More “How to install VMware Workstation 10 on Linux Mint 17.1”

  • VMware vSphere 7 announced

    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”

  • Another CBT bug found in VMware ESXi 6.0

    VMware

    VMware just published KB 2136854 regarding a new bug found in ESXi 6.0 that causes virtual machine backups, which use Changed Block Tracking (CBT), to be inconsistent. VMware says the cause of the issue is this:

    This issue occurs due to an issue with CBT in the disklib area, this causes the change tracking information of I/Os that occur during snapshot consolidation to be lost. The main backup payload data is never lost and it is always written to the backend device. However, the corresponding change tracking information entries which occur during the consolidation task are missed. Subsequent QueryDiskChangedAreas() calls do not include these missed blocks, hence a backup based on this CBT data is inconsistent.

    Read More “Another CBT bug found in VMware ESXi 6.0”

  • VMware vCenter Server 5.5.0a update released

    VMware has released an update to vCenter 5.5 Server. The new updated, numbered 5.5.0a doesn’t appear to add any new features but instead focus on squishing a number of bugs in the 5.5 version – mostly around vCenter Single-Sign-On and the vSphere web client.

    Issues resolved with this release are as follows:

    1. Attempts to upgrade vCenter Single Sign-On (SSO) 5.1 Update 1 to version 5.5 might fail with error code 1603
    2. Attempts to log in to the vCenter Server might be unsuccessful after you upgrade from vCenter Server 5.1 to 5.5
    3. Unable to change the vCenter SSO administrator password on Windows in the vSphere Web Client after you upgrade to vCenter Server 5.5 or VCSA 5.5
    4. VPXD service might fail due to MS SQL database deadlock for the issues with VPXD queries that run on VPX_EVENT and VPX_EVENT_ARG tables

    Read More “VMware vCenter Server 5.5.0a update released”

Leave a Reply to Mike Tabor Cancel reply

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

4 Comments