Prior to upgrading VMware Cloud Foundation (VCF) you may experience a precheck error notifying you that an expected ESXi host bundle is missing. In this blog I will explain this error and how to get around it.
Tuesday, April 30, 2024 | 12:00 PM – 1:00 PM (CT) | Part 1: Introducing vSphere Foundation: The Enterprise Workload Engine. In this session, learn how VVF can boost operational efficiency, increase workload performance and improve your security posture.
Upgrading to the latest version of any software can sometimes introduce unexpected challenges. For administrators of VMware vCenter Server 8.0U2, one such issue is the appearance of privilege-related warnings in the vSphere Client. These warnings can cause concern but can be managed with the right steps.
Symptoms
After upgrading to vCenter Server 8.0U2, administrators may encounter the following warning in the vSphere Client’s Events tab: “Privilege check failed for user VSPHERE.LOCAL\vmware-vsm-… for missing permission Sessions.TerminateSession.”
This warning is flagged when the system checks the permissions associated with the VsmSvcRole role assigned to the solution user account.
Cause
The core of this issue lies in the permissions set for the VsmSvcRole. Despite having several default privileges, it lacks the “Sessions.TerminateSession” permission, which is crucial for certain administrative operations within the vSphere environment.
Immediate Workaround
Until VMware releases an update to address this issue, administrators can manually adjust the role permissions to prevent these warnings. Here’s how to implement this workaround:
Log in to the vSphere Client with a user account that has administrative privileges.
Navigate to Administration > Roles.
Select the VsmSvcRole and click on EDIT.
In the pop-up window, navigate to Sessions > View and stop sessions.
Click SAVE to apply the changes. Ensure the role’s privileges now include the ability to terminate sessions.
This adjustment does not require any service restarts, making it a straightforward fix that can be implemented immediately.
Long-Term Resolution
VMware has acknowledged the issue and is working on a resolution to be included in a future software update. More info VMware KB 94967
I recently got a question from our field inquiring about the minimum vSphere privileges that would be required to either install or remove a patch (VIB/Component) from an ESXi host. The customer was interested in using PowerCLI and specifically the ESXLI interface to automate the installation […]
VMware added a method to reset a locked/forgotten root pass without the need for restarting the appliance and having to go into GRUB to boot into single user mode. […]
This is the third part of a series of blogpost related to the NSX technology, relative version 4.xYou can find other blogpost from this series here: – Part 1 NSX […]
Hello There, Recently , we faced an issue in our NSX-T envrironment running with 3.2.x version. We saw below error message while running the pre-check for NSX upgrade to 4.x version. “Edge node 31c2a0ba-e10a-48eb-940d-85f1e48c811f vmId is not found on NSX manager” […]
In this blog post, we’ll dive into the common pitfalls and challenges that users face when trying to upgrade vCenter with vCHA enabled. We’ll discuss the potential causes of the failure, troubleshooting tips, and possible solutions to get your upgrade back on track.
I’m proud to present the latest VMware Cloud Foundation posters. Back by popular demand, the posters are done in a dark format (my personal favorite) and a light format. Each poster features the art of what’s possible with VMware Cloud Foundation 5 Private Cloud Platform.