Upgrading VMware App Volumes to 2.11 Step by Step

Following on my previous blog post announcing the release of App Volumes 2.11 and the release notes, here is the upgrade process as promised.

In version 2.11 you can still cannot upgrade directly, the process has not changed and you are required to manually remove previous versions of App Volumes before installing the latest version (2.11).

First make sure you have downloaded the media from your My VMware portal

Upgrade the App Volumes Manager

Be sure to organise a maintenance window for the upgrade so users are not affected.


1. Detach all App Stacks and Writable Volumes before the upgrade

2. Take a snapshot or backup of the App Volumes server

3. Note the ODBC settings on the App Volumes server – IMPORTANT make sure you know the SQL database connection credentials

4. Create a backup of the App Volumes SQL database

Upgrade Steps

1. Uninstall previous versions of the App Volumes Manager using the Programs and Features applet

You have the option to unmount all attached volumes if you forget to do this in the prerequisites

2. Install the new version of App Volumes

Mount the App Volumes ISO

Navigate to the Installation folder and run setup.exe

Click Next

Accept the License Agreement

Select install App Volumes Manager and click Install

Wait for the App Volumes Manager Installation Wizard to load and click Next

Select Connect to an existing SQL Server database.

* If you are not upgrading and installing for the first time you can choose to install a local SQL Express database but do your homework on the limitations. It is best practise to have you database on a separate SQL server but not everyone has one available. SQL Express is meant for small deployments and is fine for demo’s and POC’s

Enter your local or remote database Name and credentials to connect to it and click Next

* Do not check the box to overwrite the database if you are performing the upgrade.

Choose the Network Ports (select defaults unless required to change) and click Next

Choose the local location to install App Volumes Manager to and click Next

Click Install.

The installation will take 5 – 10 minutes. Click Finish once its complete.

To confirm App Volumes Manage has upgraded successfully. Open App Volumes Manager by double clicking the desktop shortcut.

You might see the message ‘Waiting for App Volumes Manager servers to start up’, when opening the Manager for the first time

Wait for the App Volumes services to start and then close the browser and try again.

Login to App Volumes Manager and you will see the Version number has changed at the bottom of the web page and also you should see all your existing App Stacks and data linked via the database.

Next we need to upgrade the App Volumes agent on your provisioning computer and/or Gold Images

Upgrade the App Volumes Agent


1. Make sure you have upgraded the App Volumes Manager first

2. Detach any App Stacks or Writable Volumes that are attached to the machine you are updating the agent on.

3. Login to the machine with an account that does not have any App Stacks or Writable Volume assignments.

Upgrade Steps:

Uninstall previous versions of the App Volumes Agent using the Programs and Features applet

You will be asked to restart the machine

After the restart mount the ISO and run setup.exe from the installation folder

Click Next

Accept the License Agreement

Choose Install App Volumes Agent

* At this point you may receive an error regarding a missing Microsoft Security Update KB3033929. Download and install this update and restart machine, then restart the wizard again.

Enter the fully qualified domain name of your App Volume Management server/ Leave the port as default unless you’ve changed it.

Review the settings and click Install and then Finish once the Wizard is complete.

You will then be prompted to restart the machine. Once its rebooted, login to the machine with an account an App Stack or Writable Volume assigned to test the upgrade has been successful and the user receives the assignments.

Finally, you will then need to recompose your virtual desktop pools.

Leave a Reply

Your email address will not be published. Required fields are marked *