Release date: February 7th 2022
Welcome to my VMware App Volumes series.In this session I will describe how I upgraded the VMware App Volumes Agent in my template to v. 2111. I start out by downloading the installation media from VMware Customer Connect
As I’ve gone over to using MDT to create templates, I will update the App Volumes Agent in the Deployment Share and run through the task sequence to create a new template. Before I begin, I open the task sequence and can see that it has found the 184.108.40.206 agent in the Deployment Share.
I close the Deployment Workbench MMC before I continue. To update the App Volumes Agent in the Deployment Share, I will first delete the existing agent from the Deployment Share
Next, I copy the new VMware App Volumes Agent msi-file to the “AppVolumesAgent” folder in the Deployment Share. It is important to make sure that the executable isn’t blocked by Windows Security, therefore I right-click the msi-file, select Properties and tick the Unblock box, if it exists. This also applies to the other executable files under the “D:\DeploymentShare\VMware” folder.
When I now open the Deployment Workbench MMC, the new App Volumes Agent will be identified correctly
Finally, I update the deployment Share, before I run through a task sequence and push the new template to my desktop pool. In scenarios with persistent desktop pools, I would advice using “silent install” upgrades, as described by VMware here: Upgrade App Volumes Agent Silently
This completes my upgrade of the VMware App Volumes Agent. My next logical step would now be to upgrade the VMware App Volumes Templates, this I have posted here:
VMware App Volumes Product Page
VMware App Volumes planning, deployment etc.
Disclaimer: Every tips/tricks/posting I have published here, is tried and tested in different it-solutions. It is not guaranteed to work everywhere, but is meant as a tip for other users out there. Remember, Google is your friend and don’t be afraid to steal with pride! Feel free to comment below as needed.