VMware Tools Upgrade Using Lifecycle Manager

This is a post to show how to do a VMware tools upgrade using Lifecycle Manager.

Download the latest release of VMware Tools release from Customer Connect VMware portal

How to download VMware tools from Customer Connect

Link to download

Then login

Import the Update to vCenter using Lifecycle Manager portal

  • on vCenter click on Lifecycle Manager:

  • Click in Components and check if the version you need to deploy is available under components:

  • To add the new version, click on Lifecyle Manager Actions and click on import updates:

  • Upload the offline depot corresponding to the version you want to install, which you’ve downloaded from customer connect (check step 1):

  • it might take some time to vCenter to upload the file and make it available, so take your time and go grab a cup of coffee in the meantime.

  • Double check if the version is now available on the Lifecycle Manager component depot:

  • After this we will create a new baseline and attach it to specific hosts/cluster. (Step 3)

 

Create a new Baseline on Lifecycle Manager (if you use a Cluster image, go to step 5):

  • Click on Baselines tab, New and click on Baseline:

  • Give it a name and specify the version of the VMware tools you are going to upgrade and make sure you select Patch as the content for the baseline, click next:

  • Uncheck Automatically Update this baseline with patches that match the following criteria, click next:

  • Deselect Show only rollup updates, and filter for the VMware tools versions you need to update:

  • Click Next and finish the Baseline creation.

Now that we have the baseline created, we will apply that to a host, the same baseline can also be applied to a Cluster:

  • After attaching the new Baseline we’ve recently created, select the Host and go to Updates tab, Baselines and check Compliance:

  • After attaching the baseline and checking for compliance, the baseline we’ve recently created will show as non-compliant:

  • Select the baseline and click on Remediate, to apply the changes to the hosts. As this is a Live remediation, this is non disruptive and do not require the host to be rebooted.
  • After the remediation and installation of the patch on the host, it will show as compliant:

Add a new component to a Cluster Image:

  • Select the cluster and go to Updates tab:

  • While editing the image, select add components:

  • Select the VMware tools Upgrade and add it to the Image:

  • Click Save to close editing the Image, this will run a compliance check on all hosts within the Cluster.

 

Now we will need to install this component to the Cluster:

  • The upgrade of the VMware tools on the Host is non disruptive as it is a live remediation.
  • On the cluster image under updates, click on run pre check to check image compliance with the host:

  • Pre-check will show that the host is not compliant and needs to be remediate:

  • Click on Actions and then Remediate:

  • After the remediation the host/cluster will have the latest version of VMware Tools installed. Next step we will upgrade the VMware tools on multiple VM’s.

 

To Upgrade VMware Tools on Multiple VM’s:

  • Click on the Cluster, under Updates tab, select VMware Tools and click on Check Status:

  • After checking the Status of the VM’s within that Cluster, select the VM’s and click on Upgrade to Match Host:

  • Keep in mind that you can change the behavior of what will happen with the VM under Lifecycle manager, Settings and VM’s:

  • This can also be changed under the remediation process of the VMware Tools upgrade:

  • After the Upgrade is complete you can see the VM shown as Compliant.
  • If the VMware tools upgrade fails, please follow this procedure:

Check connectivity of the VM’s after the VMware Tools Upgrade:

  • You can check if the VM’s are reachable using a simple PowerShell script
  • Check your monitoring system for any alerts.
  • Double check vCenter for any errors or recent events.

Some Useful links:

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *