After upgrading my vCenter Server to the latest vSphere 7.0 Update 1, I was unable to see ESXi 7.0 Update 1 Image. When I attempted to sync the updates I got the error “Download patch definitions task failed while syncing depots. Error: ‘integrity.fault.HostPatchInvalidVendorCode’.” Seeing as the error mentioned the depots, navigate to Menu->Lifecycle Manager and then select the Settings tab and then Patch Setup. ...
With the release of vCenter 7 Update 1, VMware introuced the vCLS (vSphere Clustering Service). More information can be found here. The Insufficient Resources Error Looking at the error details it looks like it is looking for a feature called cpuid.mwait Root Cause: EVC on the vCLS VMs Reviewing the VMX file it seems like EVC is enabled on the vCLS VMs. I didn’t want to enable EVC on the whole cluster so I wanted to do it only on the specific VMs. ...
I recently ran in to an issue where I had to re-register my NSX server with vIDM. The ask was to extract the Thumbprint from vIDM. The command I ran to extract it was: echo -n | openssl s_client -connect hostname:443 2>/dev/null | openssl x509 -noout -fingerprint -sha256 This can be used across multiple products where the Thumbprint needs to be extracted
I’ve ran recently in to an issue where I couldn’t perform an update from the admin UI, in order to get up and running I executed the following from a ssh shell. I was luky enough to find the documentation here /usr/lib/applmgmt/support/scripts/software-packages.py install --url Some of the additional options that could be used software-packages stage --url software-packages install --staged I like to perform the update from the command line because it gives me additional information that I might not be able to see in the UI ...
I recently ran in to an issue where the vCenter server appliance update timed out. Rebooting the vCenter server brought the server back up but I was unable to log in to the administration section due to an Update installation in progress error Doing some research I found that there is a file that holds this information fount at /etc/applmgmt/appliance/software_update_state.conf At this point all I had to do was edit the file using vi ...
This historical lab example shows how I updated an ESXi 7.0 host from the command line when I could not use the UI. Broadcom has retired the original public depot, so its executable URL has been removed and the preserved example below uses an offline-bundle variable. ESXi 7 also reached End of General Support on October 2, 2025. Prepare the Host and Enter Maintenance Mode Broadcom’s current esxcli patching procedure requires the ESXi host to be in maintenance mode before esxcli software profile update. ...
As I was installing\upgrading my lab environment to ESXi 7.0 I received an error that the CPU was unsupported. As per the release notes vSphere 7.0 release notes my CPU is no longer on the compatibility list. Since this is a lab environment I wanted to continue using my current hardware. It goes without saying that this method should not be used in a production environment. To allow the legacy CPU all I had to do is boot up from the ISO, on the boot Menu I pressed TAB or Shift + O and added allowLegacyCPU=True option as seen in the screenshot below ...