VMware vRealize Automation 8.0.1 – Hotfix 3 Released

Reading time: 2 minutes
It seems like it was just a few days ago that I was posting that vRealize Automation 8.0.1 Hotfix 2 was available. In reality, it was precisely 15 days ago. Nevertheless, on April 16, 2020, VMware released the third hotfix for vRealize Automation 8.0.1. Hotfix 3 (20 days after Hotfix 2) including seven fixes for Provisioning, the Service Broker, and vRealize CodeStream. The hotfix can be installed using vRealize Suite Lifecycle Manager 8.

Getting Started with vSphere 7.0 Lifecycle Manager

Reading time: 9 minutes
In the early days of VMware ESX and VirtualCenter Server (now called vCenter Server), patching and upgrading ESX hosts was a manual and challenging task that required a significant amount of time from a virtual administrator to complete. This process included manually staging patch files as well as executing install and reboot commands to each ESX host. To simplify virtual infrastructure management, in 2007, VMware introduced a new feature with VMware VirtualCenter Server 2.

VMware vRealize Automation 8.0.1 - Hotfix 2 Released

Reading time: 3 minutes
On March 27, 2020, VMware released the second hotfix for vRealize Automation 8.0.1. Included in it are sixty-three fixes for items relating to the Provisioning, vRealize Orchestrator (vRO), vRealize CodeStream, and Virtual appliance/clustering. The hotfix can be installed using vRealize Suite Lifecycle Manager 8.0.1. It is recommended to install vRealize Suite Lifecycle Manager 8.0.1 Patch 1 before installing vRealize Automation 8.0.1 Hotfix 2 (Build For complete details on the items that have been resolved with this hotfix, review the VMware KB article Cumulative Update for vRealize Automation 8.

ESXi Upgrade - Software or system configuration of host is incompatible

Reading time: 2 minutes
While attempting to upgrade my ESXi hosts to the latest vSphere 7.0 release, I ran into the following error on all of the hosts in my home lab: The upgrade has VIBs that are missing dependencies. Remove the VIBs or use Image Builder to create a custom upgrade ISO image that contains the missing dependencies, and try to upgrade again. While the error message gives you a pretty good idea of what might be causing the issue, for the life of me, I couldn’t think of what VIBs it could be referring to.

VMware vSphere 7.0 Now Available

Reading time: 5 minutes
Today, the highly anticipated VMware vSphere 7.0 release is now available for download. With it comes many new features and enhancements that I hope to write about in the near future. Until then, there are several items that you should be aware of before you begin upgrading your environments. What’s New in vSphere 7.0 There are so many new features in vSphere 7.0 that a dedicated blog post would be required to cover them all.

14 / 19


Get Notified of Future Posts

Follow Me

LinkedIn Icon
Twitter/X Icon
Threads Icon
RSS Icon

Recent Posts