Upgrading your VMware vCenter Server is a crucial part of maintaining a secure and efficient virtualization environment. In this guide, we’ll walk through the process of upgrading a vCenter Server using VMware Lifecycle Manager (vLCM), highlighting each key step with screenshots and best practices.
🔍 Step 1: Verify Current Build Number
First, log in to the vSphere Client and navigate to the Summary tab of your vCenter Server. Here, verify the current Build Number and check for any available updates. The latest patch or ISO can be downloaded from the Broadcom support portal.
💾 Step 2: Take a Snapshot (Pre-Upgrade Backup)
Before proceeding, take a snapshot of the vCenter Server VM. While this is a short-term backup, it provides a rollback option if anything goes wrong during the upgrade.
📦 Step 3: Upload and Mount the ISO
-
Download the latest vCenter Server ISO from the Broadcom portal.
-
Upload it to a datastore.
-
Edit the vCenter VM settings, navigate to the CD/DVD Drive, and mount the ISO file.
-
Ensure “Connected” is checked.
🧭 Step 4: Begin Upgrade via Lifecycle Manager
Login to the vCenter Server to be upgraded, then go to:
Menu > Lifecycle Manager > Updates > Upgrades
The mounted ISO should be detected automatically. Select it and click Next to begin.
✅ Step 5: Confirm Backup and Pre-checks
If you’ve already taken a snapshot or backup, acknowledge this step. Lifecycle Manager allows you to run Pre-Checks before proceeding, which ensures the system is ready for the upgrade.
⚙️ Step 6: Upgrade the Lifecycle Manager Plug-in
To orchestrate the upgrade properly, you may need to update the vLCM plug-in. Once updated, the UI will reload.
On the same upgrade plug-in, source pre-check run is required before proceeding to next step. The recommended version of vCenter server life-cycle Manager plugin is installed and ready to support the update process.
Click Run Pre-Checks.
Click next to proceed with Configure Target Appliance.
Configure the target appliance that will be deployed during the upgrade process, Click Configure Target Appliance.
🛠 Step 7: Configure Target Appliance
-
Click Configure Target Appliance.
-
Accept the EULA and join CEIP if preferred.
-
Provide the source vCenter details, such as IP/FQDN, credentials, and accept the SSL certificate.
-
Choose to deploy the new appliance in the same location as the source.
-
Set a temporary VM name, root password, and network settings.
🧠 Tip: Ensure DNS records for the temporary hostname and IP are properly configured.
The target location for deployment must be a vCenter Server where the new vCenter Appliance will be deployed. In this case, I chose to deploy it in the same location as the source vCenter. For the Deployment Type, select “Same Configuration”—this will automatically retrieve and apply the current configuration to the new appliance, simplifying the setup process.
Next, under VM Appliance Details, specify a temporary VM name for the new vCenter Server (the name will typically include the target version) and set a root password. Click Next to continue.
In the Network Settings section, provide a temporary IP address, FQDN, DNS settings, and select the appropriate VM network portgroup. Make sure to click Next once completed.
⚠️ To prevent network-related issues during deployment, ensure that DNS records are created for both the temporary hostname and IP address.
In the review page review configuration for new vCenter and click Finish.
📋 Step 8: Review and Initiate Upgrade
On the review screen, validate all configuration details and click Finish to proceed.
The upgrade consists of two stages:
-
Prepare – Deploys the new vCenter and replicates data.
-
Switchover – Transfers services from the old to the new appliance.
Choose Automated Switchover for a smoother process. The full upgrade may take 40–50 minutes.
Once SwitchOver process is completed You will see the message vCenter server is upgraded to new version and navigate to the vSphere client.
🆕 Step 9: Post-Upgrade Validation
After the upgrade, you’ll be redirected to the new vSphere Client interface. Perform sanity checks:
-
Log in to the new vCenter Server.
-
Verify the Build Number and version.
-
Ensure all hosts, clusters, and VMs are visible and healthy.
Step 10: Cleanup and Finalize
-
Delete the old vCenter VM (powered off state) from disk.
-
Rename the newly deployed VM to match your naming convention.
-
Perform Storage vMotion to align disk names with the updated VM name.
✅ Conclusion
Upgrading your vCenter Server using vLCM is streamlined and efficient when done with proper planning and safety checks like snapshots and pre-upgrade validations. This method ensures minimal downtime and a seamless transition to the latest features and security patches provided by VMware and Broadcom.
Useful Aticles
Backup VMware vCenter server using SMB protocol
VMware vCenter server backup error Path not exported by the remote filesystem
Configure the VMWare Update Manager Proxy Settings using vSphere Web Client
CREATE VIRTUAL DATACENTER AND ADD ESXI HOST ON VCENTER SERVER
ADDING AND ASSIGNING VSPHERE LICENSES IN VCENTER SERVER AND ESXI
ADDING AND CONFIGURING VMWARE VSPHERE VCENTER SSO ACTIVE DIRECTORY AS LDAP SERVER
Configuring a vCenter PSC Single sign-on Active directory Integrated windows authenticatio
