vCenter version build number and vSphere Client version mismatches
search cancel

vCenter version build number and vSphere Client version mismatches

book

Article ID: 380386

calendar_today

Updated On:

Products

VMware vCenter Server VMware vCenter Server 7.0 VMware vCenter Server 8.0

Issue/Introduction

  • The version in the vSphere Client UI and the build number in vCenter are different.

  • After upgrading or patching vCenter Server to a new release, different version numbers may appear in the VAMI and the vSphere Client under the 'About VMware vSphere' tab.

  • The following information appears on the vCenter Server VAMI Summary page (https://<VC_FQDN>:5480):
  • The vSphere Client displays a different version of vCenter Server under the About VMware vSphere tab.
  • To confirm the vSphere client version, run the following command: rpm -qa | grep vsphere-ui

  • The command to check the vCenter version from command line: vpxd -v

Environment

VMware vCenter Server 7.x
VMware vCenter Server 8.x

Cause

The vCenter Server Appliance (VCSA) comprises two main sets of services:

  1. Core Server Services: These manage the overall vSphere infrastructure, including hosts, VMs, storage, and networking.
  2. Authentication Services: These handle identity management, such as SSO (Single Sign-On), which integrates with Active Directory or other identity providers.

Among the Core Server Services, the vSphere Client stands out as a web-based HTML5 interface for connecting to and managing vSphere instances. It's essential to note the following:

  • The vCenter version and build number represent the appliance itself, including all its internal components.
  • The vSphere Client version and build number, however, are specific to the web-based interface and can differ from the vCenter version.

This discrepancy is expected behavior rather than a defect, primarily due to two reasons:

  1. The vSphere Client is an independent component, and its updates do not always align with vCenter Server releases.
  2. The Client Package doesn't always receive new code with every release. This ensures that minor or unrelated vCenter updates do not unnecessarily affect the client interface.

By decoupling these components, Broadcom ensures greater flexibility and stability in managing and updating the vSphere environment.

Resolution

  • The vCenter build number and the vSphere Client UI refer to two different components.
  • The details displayed in the VAMI and the console indicate the version of the vCenter Server. However, the vSphere Client is a component that facilitates the web console.
  • If no changes are made to the vSphere Client package, the minor version remains unchanged in subsequent releases. It changes only if there is a major version update or a specific change to the individual package.

Additional Information

The behavior is also observed in vCenter version 8.x.