Install and Configure App Volumes Manager
We need to download App Volume ISO file from VMware first. Next we mount this file in App Volume server, from new drive navigate to Installation folder and right-click Setup and choose Run as Administrator.
In Installation Wizard click Next on first window and accept License agreement on second and click Next
Select which component we want to install now, in this case select Install App Volumes Manager and click Next
App Volume Manager Installation Wizard will be present to us, click Next to continue
App Volume Manager can use SQL DB on this same server or connect to Existing DB on remote server. In this scenario we will use SQL Express version installed at same server. When selecting SQL Express App Volume will start installing SQL server using batch and installation files included in App Volume download
After SQL Express installation finish we will be presented with Database Server window, for SQL Express all setting are pre selected. This same window is present if Connect to existing SQL Server was made. Specify DB server and authentication method as well DB name. Click Next when finished
App Volume required HTTP and HTTPS ports to be open, default ports are input already, change to different value if needed. Click Next to continue
App Volume Manage features is pre selected, depend of deployment requirements change Installation path. Click Next to continue
Click Install to begin installation. Click Finish.
App Volumes Manager after installation need to configure, to do this open https://ipaddress_of_app_vol_mgr in Web Browser. Welcome to App Volume Manager page will display, click Get Started to begin.
First we need to input License information, click Edit and Browse to License file save location. Click OK to upload
App Volumes uses Active Directory to assign App Stacks to users or group. Type Active Directory Domain Name: example.local.
Type Domain User name and password, this user need to have Read-only access. Under Trusted Domains type username and password of trusted domain which you want to allow assigning App Stacks, Click Next to test Active Directory access
Specify Active Directory group which contain users responsible for administering App Volume Manager.
Something from my observation if administrator account have space in username example: Sebastian Two it cannot logon to App Volume Manager.
After specifying AD group, click Next
At Machine managers we need add vCenter server to be able add App Stacks to Virtual Machines. Type Host name, username and password. Click Save to test connection
When App Volumes can talk to vCenter it can detect Datastore managed by vCenter. Specify default location for AppStacks and Writable Volumes. Click Upload Prepackaged Volumes to start the upload process
Before Upload process can start App Volumes Manager will ask for ESX host credential to have access to selected datastore and to convert volumes to thin format. Select one of the ESX hosts and type username and password. Selected which volumes we want to upload and click Upload to start the process.
That’s completes the initial setup process.
Install App Volumes Agent
VMware App Volume Agent sharing same Setup installation file as App Volume Manager. When starting Setup file skip 3 first steps and choose Install App Volumes Agent, click Install
At App Volumes Agent Installation Wizard click Next to continue
Type App Volume Manager Address and Port, click Next
At Ready to install click Install to begin installation. After installation finished we will be prompt to restart machine.
Administer AppStacks according to a deployment plan:
Create/Edit an AppStack
Provision an AppStack
Assign users/groups/computers to AppStack
To create new AppStack, after login to App Volumes Manager click Volumes > AppStacks and click Create AppStack. Specify Name of new AppStack, storage and path, Select Temple which you want to use for this application. Default application template is 20GB in size which is a lot more what application and software required to. VMware provides good KB article how to Creating a new App Volumes AppStack template VMDK smaller than 20 GB (2116022)
When creation of New AppStack finish, we are able to see it under Volumes > AppStacks. First State of AppStack is Unprovisioned which mean that it is ready to be provision to clean machine with App Volume Agent installed. To start this process expand plus sign next to AppStack name and click Provision.
New menu with search field will show, type machine name to which we want to provision AppStack for application installation and click Search button. In list below select correct machine which Status should be available and click Provision button.
At Confirm Start Provisioning click Start Provisioning.
Opening Console to machine which was selected for provisioning, we should see window informing us that Provisioning was succesful and we can start installing Application on AppStack.
Installing new Application on machine in provisioning mode will install all files and setting in to AppStack, if Application required restart we able to do so without stopping provisioning mode. When finished the installation, click the OK button. App Volume will ask to conform that installation finish and start analyzing installed application after that will reboot the machine.
When the machine reboots and we login again we will see new window informing us that the provisioning was successful and we can assign new application to users.
In App Volume Manager under Volumes > AppStacks we can see our AppStack read to be assigned to users or groups. To do so click Assign button
In new window inside search filed type user name or AD group name to which we want to assign this AppStack, from list below check the box next to user Status and click Assign button.
Conformation window will be display with choice to Attach AppStack on next login or reboot which is a default.
Or we can choose Attach AppStacks immediately, App Volume will inform us that user has to be login to VM to attach immediately.
Depending which attach method we choose user will be able to use the application as is it installed locally on his VM.
Click here to read other entries in the series VCAP6 -DTM