Creating an AppStack with VMware App Volumes

This post serves as a continuation of my previous post:

Installing and performing initial configuration of VMware App Volumes Manager http://terenceluk.blogspot.com/2015/11/installing-and-performing-initial.html

… to demonstrate how to create an AppStack once you have VMware App Volumes deployed in your environment.

Prerequisites

1. In order to create an AppStack, you’ll need a virtual machine to mount an empty AppStack to capture the application that is being installed.  With this in mind, you can either use a plain vanilla Windows install with no applications installed on it to avoid conflicts or, which I have found to be the better option, use the master image that you’ll be mounting the AppStacks on.  The reason why the latter appears to work better is because if you had Microsoft Office installed on your master image, it’s better to the master image to deploy an AppStack with Visio.  Not doing so caused all sorts of problems for me when attempting to mount a Visio AppStack to the master image. 
2. You will need to deploy the App Volumes agent on the virtual machine that you will be using to create an AppStack.  If you are using your master image then this would not be a problem because it would need the agent to have AppStacks mounted onto it.

Step #1 – Install the App Volumes agent onto the virtual machine used to create the AppStack

Begin by logging onto the virtual machine that you will be using to create a new AppStack and launch the VMware App Volumes installer:

Proceed through the wizard:

Select Install App Volumes Agent:

Type in either the IP address or FQDN of the App Volumes Manager server:

Complete the installation:

Restart the virtual machine:

Step #2 – Create the new AppStack

Log onto the VMware App Volumes Manager administration console, click on Volumes and then AppStacks, then click on Create AppStack:

Fill in the appropriate fields as such:

Selecting Perform in the background will allow you to continue through the creation immediately while selecting Wait for completion would keep you on the screen until the empty AppStack is created:

A summary of the empty AppStack that is ready to be provisioned will be displayed:

Proceeding to click on the Provision option will bring you to the following screen that allows you to search for the virtual machine to mount the AppStack and deploy the new application:

Hitting the search button with nothing filled out in the Find Provision Computer text box will list all the virtual machines with the agent installed that the App Volumes Manager can detect:

Select the virtual machine prepared in step 1 and click on Provision:

Confirm the provisioning:

Note the new AppStack created:

Reviewing the settings of the virtual machine selected will show that a new hard disk has been mounted to it and this is the hard disk where the new application files will be redirected:

Step #3 – Install the application

Proceed and log onto the virtual machine with the empty AppStack mounted and you will see the following message displayed:

App Volumes

You are now in provisioning mode.

Click OK only after you have completely installed all applications you wish to provision to this AppStack.

Proceed to install the application and once completed, click on the OK button in the prompt:

The following message will be displayed:

Installation complete? System will reboot

Click YES to finish and reboot computer.

Or Click No to continue provisioning.

Proceed by clicking on the Yes button then OK:

The following message will be displayed once you have logged in after the restart:

Provisioning successful (exit code 0)

Click OK, then return to the App Volumes Manager to assign the AppStack.

Note that the settings of the virtual machine should show that the hard disk 2 has been removed:

Navigating back to the App Volumes Manager will show that the AppStack is now ready to be assigned:

Proceed with clicking on the Assign button then searching for the user or group you want to assign the AppStack to:

What’s also worth noting is that you can also limit which computer this AppStack can get attached to regardless of whether it is assigned to the user or group specified:

Select the desired option:

The AppStack is now assigned:

If the AppStack is assigned immediately, you should be able to see a new hard disk attached to the virtual machine that the assigned user is logged on:

Logging onto the virtual machine should also show that the application is available: