Exciting Updates to the VMware Certification…

Exciting Updates to the VMware Certification…

The VMware Certification Program is proud to announce exciting changes to make it more accessible, flexible, and valuable for all participants. Our mission is to empower individuals to validate their skills and knowledge while ensuring that our customers have access to a highly qualified […]


VMware by Broadcom, Social Media Advocacy

Useful Links for VMware by Broadcom Day 2…

Useful Links for VMware by Broadcom Day 2…

While today, May 6th, 2024 marks the completion of the “Day 2” transition where VMware’s backend system has been migrated to Broadcom’s backend system, it may still take a few days for all the new systems to fully settle with such a large migration project. There are also some planned post-Day […]


VMware by Broadcom, Social Media Advocacy

Resolving Privilege Issues in vCenter Server 8.0U2

Introduction

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:

  1. Log in to the vSphere Client with a user account that has administrative privileges.
  2. Navigate to Administration > Roles.
  3. Select the VsmSvcRole and click on EDIT.
  4. In the pop-up window, navigate to Sessions > View and stop sessions.
  5. 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