I will begin by logging into the vSphere Client and check the current version of VMware Tools running on my VM. In my vSphere 6.7 lab environment I will be upgrading VMware Tools on a Windows 2012 server VM via the vSphere Client (HTML5) which is considered a manual upgrade. The status bar of the VM displays a message when a new version is available. The guest OS checks the version of VMware Tools when you power on a Virtual Machine (VM).
Vmware tools for esxi 6.0 download install#
VMware Tools can be upgraded manually, via vSphere Update Manager, PowerCLI, or by configuring virtual machines to check and install newer versions of VMware Tools when they reboot. Although a guest operating system can run without VMware Tools, we suggest to always run the latest version of VMware Tools in your guest operating systems to access the latest features and updates. VMware Tools is a set of services and modules that enable several features in VMware products for better management of, and seamless user interactions with, guests operating systems. I mention caution because upgrading the VM Compatibility version may not always be necessary to perform unless specific features are needed. Although both of these components hold much value for virtual machines (VM) when upgraded, caution should always be at the forefront of upgrading the VM Compatibility version. VMware Tools and Virtual Machine Compatibility comes in at Step 4 when upgrading a vSphere environment. In part 4 of the vSphere Upgrade Series we will cover Upgrading VMware Tools and VM Compatibility. Part 3 guided usthrough preparing vSphere Update Manager (VUM) by creating an Upgrade Baseline and using that baseline to remediate our vSphere 6.0 Update 3 ESXi hosts to vSphere 6.7. In Part 2 we upgraded vCenter Server & migrated VUM from vSphere 6.0 Update3 to 6.7. We began in Part 1 of this blog series by reviewing our prerequisites & compatibility, gathering our data. Welcome back to the vSphere Upgrade Blog for the next piece of our Upgrade Journey.
0 kommentar(er)
