6 list the configuration options available for updating the os
Note that there is no mechanism for VMs running on v Sphere to and learn about new versions of VM Tools – only the VM to host relationship is relevant.This explains why a VM may suddenly complain about having out of date VM Tools after migrating from one host to another – the destination host has a more recent version in the product locker.We have covered looking at new aspects of v SAN 6.7 as well as v Sphere 6.7 and the process of installing v Center Server as well as Installing and Upgrading ESXi server.Let’s now take a look at the process to upgrade an existing v Center Server (6.5 in this case) up to v Center Server 6.7 and the process involved to do that.VMware has made the upgrade process for v Center Server dead simple with the ISO installer utility and the process really hasn’t changed from the one we saw with the 6.5 upgrade.In this post, we will cover Upgrading to VMware v Center Server VCSA 6.7 and take a walk through the process from start to finish.Recall from the previous post that there are three types of VM Tools – the familiar Tools ISOs for all supported operating systems, plus two additional offerings in the form of binary packages for Linux.There are several ways to initiate VM Tools updates from v Sphere or from within a guest.
If the host has a newer version, the VM is considered out of date.
A previous article provides an overview of the three types of VM Tools.
Recall that each ESXi host has a storage location for VM Tools installers, which is a configurable option and visibly referenced by the /product Locker symlink.
The first connectivity configuration that is made is connecting to the source VCSA appliance that you want to upgrade.
In my case in the home lab test environment, I have a test VCSA 6.5 U1g appliance that I am going to upgrade to VCSA 6.7.