Tuesday, November 10, 2015

Installing and performing initial configuration of VMware App Volumes Manager

I’ve been fortunate enough to have a few clients interested in adopting VMware’s new App Volumes earlier this year and while I’ve had numerous issues with Microsoft Office or related applications, I’ve found it extremely for most other applications that have no dependency on Microsoft Office.  I know I’m a bit late in writing this post as the screenshots have been sitting in my Outlook for almost a year but better late than never, right?


  1. Begin by allocating a server to deploy VMware App Volumes Manager on.  The server I’ll be using in this example will be Windows Server 2012 R2.
  2. Launch Server Manager and install .NET Framework 3.5 Features:image
  3. If a remote SQL database server is going to be used, create an empty database named svmanager_production (or a different name if desired) and a SQL authentication account granting it dbcreator and db_owner rights to the svmanager_production database.
  4. Create a service account in Active Directory with read-only access (regular domain user is fine).
  5. Assign the service account created in step #4 to vCenter and assign the following permissions:
  • Datastore
    • Allocate space
    • Browse datastore
    • Low level file operations
    • Remove file
    • Update virtual machine files
  • Folder
    • Create folder
    • Delete folder
  • Global
    • Cancel task
  • Host
    • Local operations
      • Create virtual machine
      • Delete virtual machine
      • Reconfigure virtual machine
  • Resource
    • Assign virtual machine to resource pool
  • Sessions
    • View and stop sessions
  • Tasks
    • Create task
  • Virtual machine
    • Configuration
      • Add existing disk
      • Add new disk
      • Add or remove device
      • Change resource
      • Remove disk
      • Settings
    • Interaction
      • Power Off
      • Power On
      • Suspend
    • Inventory
      • Create from exising
      • Create new
      • Move
      • Register
      • Remove
      • Unregister
    • Provisioning
      • Clone template
      • Clone virtual machine
      • Create template from virtual machine
      • Customize
      • Deploy template
      • Mark as template
      • Mark as virtual machine
      • Modify customization specification
      • Promote disks
      • Read customization specifications

App Volumes Manager Installation

Download the VMware App Volume ISO, extract it to a directory then run setup.exe:


Proceed through the installation wizard:



Select Install App Volume Manager:




Select either Install local SQL Server Express Database or Connect to an existing SQL Server Database:


For the purpose of this example, I will be using a remote database server:


Type in the remote SQL server’s name and database instance, the account that was created and svmanager_production as the Name of database catalog to use or create then check the option to Overwrite existing database (if any) checkbox:








Once the installation has completed, proceed and launch the App Volumes Manager portal to begin the initial configuration:



In the Active Directory window fill in the following:

Active Directory Domain Name: Enter the FQDN of your AD domain
Domain Controller Host Name: <leave blank>
LDAP Base: <leave blank if you would like the whole domain to be used or fill in the DN of a specific OU>
Username: Enter the service account created
Password: Enter the password for the service account
Use LDAPS: <enable if LDAPS is enabled on the DCs>
Allow non-domain entities: <enable if non-domain users and computers are going to be used>


Select a group that you would like to assign administrative privileges to the App Volumes Manager:


Fill in the required details for the vCenter in your environment:


Select a storage location to store the App Volumes:


Confirm the Storage Settings:


Select a host in your cluster and enter root credentials to upload prepackaged volumes:


Confirm the upload:


Confirm the summary settings:


The initial configuration is now setup and you can proceed installing the App Volumes agent onto a desktop or server to provision new AppStacks:


1 comment:

Unknown said...

Thanks for sharing this post. I just get done mine.
Work perfectly, appreciate the granular security you apply, instead of using "administrator" group.