Tag Archives: App Volumes

VMware App Volumes 2.9 Installation – Part 2

In part 1, we completed the Volumes Manager installation. Let’s complete its configuration in this part 2.

Tristan said in his document to restart the Windows server, so I’m going to do that. Once done, launch the App Volume icon from Windows Server desktop. You get a browser based wizard like the one below:


Click on the Get Started button, and you will see the licensing screenshot below. I will just use the evaluation license for now, as it’s easy to add it later on. Click Next button once you are done.


The next screen is AD integration. App Volume requires AD integration, and this screen is where you specify it. In real Production environment, where best practices must be applied:

  • specify your LDAP Base. My lab has only a few hundreds objects, so I will leave it blank.
  • create a service account for App Volume.


The next screen allows you to specify the AD group that can administer App Volumes. Since I already have an EUC Admin in my AD, I’d use that.


The next screen shows the vCenter integration. App Volume works well with Citrix also. There is no screen to integrate with Horizon View, as the integration is done at vCenter level. Specify a service account that will do the integration. In my case, I’ve created an ID called app-volume. This makes tracking easier in vCenter or Log Insight, as I can see the ID.

You can directly connect to ESXi Host, as shown below. I’ve put the text “do not use this” in the ESXi user name as I think you should always interface via vCenter. This makes operations easier.


Click Save button. You get the screenshot like this. You can add multiple vCenter Servers, useful in active/active Horizon View setup.


The next part is Storage. In the case of VSAN, there is only 1 datastore. You can change the folder names and path. I’ve left them as default value so you know what the default values are.


By default, the following templates are created

  1. User Installed Applications (UIA) Only
  2. User Profile Only
  3. UIA and User Profile

These templates can be copied (and resized from their 10 GB default size) as necessary to support individual use-cases or storage scenarios.


Click the Upload button. You get a confirmation like this below. The lab already has some writetable volume as my colleague created 2 writeable volumes a few weeks back.


Click Next. You are essentially done configuring App Volumes Manager.

The next part deals with AppStack. This is what the screenshot looks like.


The next part is logically a separate component, so I will cover them in separate blog to mark the separation. I will cover this in Part 4, as we need to install a few more items first, before we can move to AppStacks. So let’s move to Part 3 to install the Agent and View Broker.

VMware App Volumes 2.9 Installation (with Horizon View integration)

I will try to complement a great document titled VMware App Volumes 2.5 Deployment Guide, written by EUC expert Tristan Todd. I highly recommend you read his document first before reading mine.

What I use

  • Windows 2012 R2 with latest service pack and update. The manual listed .Net 3.5 Framework, I’m using 4.5 and did not encounter issue.
  • Windows 7. With no application installed. This is the desktop master image, where you install the applications. You can use 1 VM for multiple AppStack, but not at the same time.
  • Horizon View. I’m using version 6.0.1, which is compatible with App Volume 2.9.

For details, review the compatibility here.

The overall installation to deployment involves 3 main stages, which are:

  1. Install and Configure
    • You mostly work with the App Volumes Manager.
    • Overall Flow is:
      • Install Volumes Manager, Agent and View Broker.
      • Configure Volumes Manager.
  2. Capture
    • You mostly work with the App Volume Provisioning VM.
    • Repeat for each application.
  3. Provision

Install and Configure Steps

To begin the install, mount the ISO file to the Windows server VM that you have prepared earlier. I’ve prepared Windows 2012 R2. From there, launch the setup.exe as shown below.


The wizard will launch. Overall, I found it quite straight forward.


Notice by default it chooses the Agent, and not the Manager. Click on the Manager.


The installer comes with MS SQL Express. I’m going to choose this option.


It took around 5 minutes to install it. There is no detailed progress bar. After a few minutes, the following dialog was shown.


I’m going with the default, so I’m not changing the settings. I clicked Next button, and the following screenshot was shown:


It looks logical, so I will go with the default. I clicked Next button, and now it lets you specify the destination.


Again, I’m not changing it. I don’t see a point in changing it. Clicking Next button begins the installation. It took around 10 minutes, with the last step (running script files) took a good 5 minutes.


At the end, you are presented with the screen below:


That completes the App Volumes Manager installation. We have not done any configuration. I will cover it here.