Update Manager does a great job of patching hosts and updating VMware Tools, but what’s actually going on under the covers?
Update Manager uses APIs to talk to each ESXi host to perform remediation tasks.
***You need to make sure that this Datastore/folder is a shared datastore accessible by each host that will be using this Host Profile***. Once you have your Host Profile created the Host Profile, you can attach it to a cluster or an Auto Deploy rule and you are good to go.
if all vm’s have the same admin account or an Admin AD account, use that…
Tools Upgrade Policy = “manual” Get-View -View Type Virtual Machine | foreach # Get all Virtual Machines that have the “windowsguest” attribute in Extension Data. Guest Family, and that are powered on $windows = Get-View -View Type Virtual Machine | where # Foreach virtual machine from the results, run “restart-service” within the guest **Note the username and password will need to be updated.
What this means is that Update Manager will use whichever version of VMware tools is installed locally on each host, unless that host is using a shared product Locker.
VUM uses whatever configuration the host has, it does not have a Tools repository or additional logic to point to some other location.
and that VMware is now shipping VMware tools outside of the v Sphere releases. Since we are restarting the VMTools service, this command will come back with an error, however if you check the windows logs you’ll see the command functions properly and this error is only because the Tools connection is being reset during the command execution (this is normal when running the restart-service VMTools command) By default, ESXi includes VMware Tools under the /product Locker folder (which is actually a Symlink to the location on it’s local storage.. When running ‘ls –n’ you will see that product Locker (cyan) just points to /locker/packages/5.5.0 (dark blue meaning the path exists. ‘ls –n /product Locker’ will return only that line and be a little easier on the eyes for those who are not as familiar with unix.
Since then, we have received a lot of feedback from the community, customers, and internal folks alike. Inside of the given folder are two other folders: “floppies” and “vmtools” these contain all necessary ISOs and files to allow VMware tools to be installed and updated on each supported VM on the host.
Click the Green “Add” button to add an additional advanced option.
In the Advanced Option drop-down box, select “Configure a fixed option”. Product Locker Location” and the value of the option should be “/vmfs/volumes/” in my case it was /vmfs/volumes/CPBU_PM_PMM1/product Locker.
***NOTE*** this can be tweaked to look for specific VMs or groups of VMs Get-View -View Type Virtual Machine | foreach #you can then disable this and set it back to the default value with this: $Config = New-Object VMware. This is because Invoke-VMScript uses VMtools to invoke the command in the guest.