{"id":14218,"date":"2015-11-10T10:00:05","date_gmt":"2015-11-10T09:00:05","guid":{"rendered":"http:\/\/nolabnoparty.com\/en\/?p=14218"},"modified":"2023-07-16T11:25:00","modified_gmt":"2023-07-16T09:25:00","slug":"vmware-tools-10-deployment-with-vum","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vmware-tools-10-deployment-with-vum\/","title":{"rendered":"VMware Tools 10 deployment with VUM"},"content":{"rendered":"

\"deployvmwaretools01\"<\/p>\n

To deploy VMware Tools 10 in your environment, the procedure differs from previous release because since September 2015 new versions are released as separate package outside the ESXi updates.<\/p>\n

\n
\n
\n

Despite the big benefit of having new features available without waiting for new ESXi updates, raise a problem of how to deploy new VMware Tools<\/strong> to all the virtual machines of the network and how to keep them up-to-date<\/strong>.<\/p>\n

 <\/p>\n

Keep VM Tools up-to-date<\/h2>\n

If your environment has different hosts versions, each ESXi will have a different VM Tools version stored in its local repository (by default \/locker\/packages\/<version><\/em>).<\/p>\n

If a virtual machine is hosted on a ESXi 5.5, for instance, and the VM Tools are updated to that release, moving the VM to a different host (i.e. ESXi 5.5 upd3) it will show the message:<\/p>\n

VMware Tools is outdated on this virtual machine<\/p><\/blockquote>\n

To deploy new VM Tools releases and to get rid of the warning message, you should create a shared repository<\/strong> reachable by all your ESXi hosts, save latest VM Tools <\/strong>that are always compatible back to all previous versions and then perform the update as you normally do after each ESXi upgrade.<\/p>\n

To achieve this goal, for each host of your network you need to modify the UserVars.ProductLockerLocation<\/strong> item that identifies the VMware Tools directory<\/strong>. By default this directory is present on each ESXi host and can be modified to point to a shared datastore. Changing the UserVars.ProductLockerLocation<\/em> value you can centralize<\/strong> the VM Tools deployment.<\/p>\n

 <\/p>\n

Get latest release<\/h2>\n

From VMware website download latest release of VMware Tools<\/a>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools02\"<\/p>\n

\n
\n
\n

Select the needed package then click Download<\/strong>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools03\"<\/p>\n

Unzipping the downloaded .zip package, the two folders extracted contain the files used to install and update<\/strong> VMware Tools:<\/p>\n

\n
\n
\n

floppies<\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools04\"<\/p>\n

\n
\n
\n

vmtools<\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools05\"<\/p>\n

 <\/p>\n

\n
\n
\n

Create a shared datastore<\/h2>\n

From VMware vSphere Client, go to Home > Inventory > Datastore and Datastores Clusters<\/strong> and select the storage on which you want to create a shared folder. Go to Summary <\/strong>tab and click Browse Datastore<\/strong>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools06\"<\/p>\n

\n
\n
\n

Click on the Create a new folder<\/strong> icon and enter a folder name (i.e. upd_vmtools<\/em>). Click OK<\/strong> to create the folder.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools07\"<\/p>\n

\n
\n
\n

The new folder is created in the selected storage. Select Upload icon > Upload Folder<\/strong> to save the VMware Tools to the storage.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools08\"<\/p>\n

\n
\n
\n

Select the folders to upload (floppies, vmtools<\/em>) then click OK<\/strong>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools09\"<\/p>\n

\n
\n
\n

The folders have been uploaded successfully.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools10\"<\/p>\n

\n
\n
\n

From the vSphere Web Client, connect the ESXi and go to Manage > Settings > Advanced System Settings<\/strong> and select the UserVars.ProductLockerLocation<\/strong> option. Click Edit<\/strong> to modify the path.<\/p>\n

\"deployvmwaretools11\"<\/p>\n

\n
\n
\n

Enter the new path<\/strong> in the format:<\/p>\n

\/vmfs\/volumes\/<shared datastore>\/<product locker folder><\/p>\n

i.e.<\/strong> \/vmfs\/volumes\/ts421_lun06_raid5\/upd_vmtools<\/p><\/blockquote>\n

then click OK<\/strong>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools12\"<\/p>\n

The new path<\/strong> has been saved.<\/p>\n

\"deployvmwaretools13\"<\/p>\n

Put the host in Maintenance Mode<\/strong> then reboot.<\/p>\n

\"deployvmwaretools14\"<\/p>\n

\n
\n
\n

When the host has been rebooted, exit the Maintenance Mode. Repeat same procedure<\/strong> for all the other hosts on the network.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools15\"<\/p>\n

SSH\u00a0the ESXi as a root\u00a0and check if the productLocker folder<\/strong> points to the shared storage previously configured.<\/p>\n

\n
\n
\n

# cd \/productLocker\/<\/span>
\n# ls -l<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools16\"<\/p>\n

 <\/p>\n

Update VMs<\/h2>\n

When all the hosts have been configured with the new path, when selecting a virtual machine\u00a0the system will notify<\/strong> the availability of a new VMware Tools version.<\/p>\n

\"deployvmwaretools17\"<\/p>\n

Before the upgrade, check the VMware Tools release installed in the selected VM right clicking the VM icon and selecting About VMware Tools<\/strong>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"deployvmwaretools18\"<\/p>\n

Click on\u00a0Update VMware Tools<\/strong>\u00a0link.<\/p>\n

\"deployvmwaretools19\"<\/p>\n

Select Automatic Upgrade<\/strong> and click Upgrade<\/strong> button to proceed.<\/p>\n

\"deployvmwaretools20\"<\/p>\n

VM Tools are being installed.<\/p>\n

\"deployvmwaretools21\"<\/p>\n

The new version has been installed successfully.<\/p>\n

\"deployvmwaretools22\"<\/p>\n

Checking the selected VM once again, the VM Tools have been updated to latest release<\/strong>.<\/p>\n

\"deployvmwaretools23\"<\/p>\n

The new version is now ready for deployment.<\/p>\n

 <\/p>\n

Upgrade VM Tools with VUM<\/h2>\n

Using VUM it's possible to schedule the VMs update<\/strong> allowing the administrators to quickly deploy latest VMware Tools release.<\/p>\n

From vSphere Client, go to Home > Inventory > VMS and Templates<\/strong>, select Update Manager<\/strong> tab and click the Attach<\/strong> option. Select VMware Tools Upgrade to Match Host<\/strong> baseline and click on Attach<\/strong>\u00a0button.<\/p>\n

\"deployvmwaretools24\"<\/p>\n

Click Scan<\/strong> to check the VMs status.<\/p>\n

\"deployvmwaretools25\"<\/p>\n

 <\/p>\n

Power cycle upgrade<\/h4>\n

To perform the upgrade on power cycle<\/strong>, click VMware Tools upgrade settings<\/strong>.<\/p>\n

\"deployvmwaretools26\"<\/p>\n

Select the VMs you want to be upgraded during power cycle<\/strong> then click Apply<\/strong>.<\/p>\n

\"deployvmwaretools27\"<\/p>\n

If you check the VM settings (i.e. w12r2-dc01<\/em>), the Tools Upgrades<\/strong> field is set to perform the upgrade before each power on<\/strong>.<\/p>\n

\"deployvmwaretools28\"<\/p>\n

 <\/p>\n

Schedule the upgrade<\/h4>\n

From Update Manager<\/strong> tab,\u00a0click Remediate<\/strong>.<\/p>\n

\"deployvmwaretools29\"<\/p>\n

Select the VMs to upgrade then click Next<\/strong>.<\/p>\n

\"deployvmwaretools30\"<\/p>\n

Select Schedule upgrade at specific time<\/strong> option then\u00a0specify the time to perform the upgrade. Click Next<\/strong> to continue.<\/p>\n

\"deployvmwaretools31\"<\/p>\n

Enable or disable the option to take a snapshot<\/strong> before remediation if you want the rollback option<\/strong>.<\/p>\n

\"deployvmwaretools32\"<\/p>\n

Click Finish<\/strong> when ready to proceed.<\/p>\n

\"deployvmwaretools33\"<\/p>\n

At scheduled time<\/strong>, the selected virtual machines are upgraded.<\/p>\n

\"deployvmwaretools34\"<\/p>\n

When the process completes, the VMs\u00a0run with\u00a0latest VM Tools\u00a0release.<\/p>\n

\"deployvmwaretools35\"<\/p>\n

Performing a new Scan<\/strong>, the upgraded VMs are now reported as Compliant<\/strong>.<\/p>\n

\"deployvmwaretools36\"<\/p>\n

With\u00a0VUM, administrators can perform a massive VM Tools deployment<\/strong> in a quick and automatic way.<\/p>\n

\"firma\"<\/p>\n","protected":false},"excerpt":{"rendered":"

To deploy VMware Tools 10 in your environment, the procedure differs from previous release because since September 2015 new versions are released as separate package outside the ESXi updates. Despite the big benefit of having new features available without waiting for new ESXi updates, raise a problem of how to deploy new VMware Tools to all the virtual machines of the network and how to keep them up-to-date.   Keep VM Tools up-to-date If your environment has different hosts versions, each ESXi will have a different VM Tools version stored in its local repository (by default \/locker\/packages\/<version>). If a virtual <\/p>\n","protected":false},"author":3,"featured_media":14219,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2701],"tags":[1552,1627,699,1579],"class_list":["post-14218","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-deployment","tag-tools","tag-vmware-en","tag-vum","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/14218","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=14218"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/14218\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/14219"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=14218"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=14218"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=14218"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}