As I discussed in my previous blog post, Understanding VCF Express Patches (EPs), Express Patches are designed to deliver security fixes as soon as they become available. As a by-product of this faster release cadence, important product fixes can also be delivered much sooner, rather than waiting months for the next scheduled release.
For a quick refresher, Express Patches (EPs) are released, versioned, and applied on a per-component basis as needed and do not require a specific installation sequence. The latest version of each component is always cumulative and includes all previously released fixes.
Earlier this week, we released several VCF component Express Patches, ranging from 9.1.0.0200 through 9.1.0.0400. Internally, we refer to this coordinated set of component updates as EP2 or the July EP, even though each Express Patch is released, versioned, and applied independently.
- ESX 9.1.0.0200
- vCenter 9.1.0.0200
- vSAN 9.1.0.0200
- NSX 9.1.0.0200
- SDDC Manager 9.1.0.0400
- VCF Operations 9.1.0.0400
- VCF Automation 9.1.0.0200
- VCF Download Tool 9.1.0.400
EP2 demonstrates exactly why a faster software release cadence matters. It includes a number of important product fixes that address issues that have prevented some customers from successfully upgrading, along with a few UI enhancements that I think many customers will appreciate as they begin their VCF 9.1 journey.
While rolling out EP2 into my lab and reviewing the release notes, I wanted to share a few of the highlights that stood out to me.
Note: Since this is the first EP release that contains a VCF Management Services (VCFMS) runtime update, make sure the Depot Service is up before applying a patch, since it is dependent on pulling the update and it would make sense to patch that service first, then underlying VCFMS runtime, which hosts all services before applying the rest in any order you wish.
