Configure App Volumes Manager

In my previous post we installed the App Volumes Manager. Now it is time for it’s configuration. In this post I will show you the basic configuration to start of with App Volumes.

Before we start make sure you have a Service Account ready for App Volumes. During the configuration, you will need this account to read objects in Active Directory..

Also create a App Volumes Administrators group.

First, open the App Volumes Manager webinterface via the shortcut on the Desktop.

Click Get Started.

On the page you are able to activatie your license. Because this is a simple lab envoirement will stick with the evaluation license for now.

Click Next.

Fill in your Active Directory information. A mentioned at the top of this page you need a service account with read permission on your Active Directory.

In this lab environment I will use LDAP for communication with Active Directory. On a highly secured production environment you may choose LDAPS, if available on your Domain Controllers.

If all the information is correct you will see the Active Directory Domain registered. It is possible to register multiple Active Directories. In some use cases you want to provision App Stacks to multiple domains. For now we just leave it by one.

Now it is time to choose your Administrators group. Users of this group are allow to login to this webinterface and have Administrator rights in App Volumes.

I usually create a Horizon Admins group which are Administrator in the Horizon Administrator and App Volumes.

When the group is selected I will show up in the Administrator Roles overview. You may also add additional groups and roles.

Enter your vCenter hostname and credentials. Read the other options carefully. In this lab I use a single ESXi host with local storage so this settings will be sufficient.

If all information is correct your vCenter will be shown in the list. If needed you may add more vCenter servers.

Choose your datastores and click Next.

Leave the settings default and click Upload.

Change the settings if needed. Otherwise leave it to default and click Finish.

You are all set. You have a basic App Volumes Manager running and you are now ready to start creating App Stacks 🙂


You might be interested in …

How to check the compliance of VMware new Licensing for an enterprise


  As you might already know VMware announced a change to its per-CPU licensing model,effective April 2, 2020.   Do you want to check if you are compliant or need more licenses? Just see below VMwareKB which contains a PowerCLI script for checking this. VMware KB

Read More

VMware PowerCLI Connect-VIServer Error: Invalid server certificate. Use Set-PowerCLIConfiguration


    Problem:   Unable to connect vCenter with  “Connect-VIServer” command. It gives error “VMware PowerCLI Connect-VIServer Error: Invalid server certificate. Use Set-PowerCLIConfiguration“       Reason:   The issue usually happen whenever Self Signed Certificate is used in Vcenter server.     Solution:   Execute below command to ignore Certificate check during vCenter Connection. […]

Read More

How to Change Workspace ONE Access SAML Signing Certificate

VMware, Workspace ONE Access

In my previous engagement, a customer asked to change the Workspace ONE Access SAML signing cert after a year and a half in production.  WS1 Access was fully deployed along with DR sites and configured as 3rd party IDP with ADFS for O365 use cases. Background: SAML signing certificates ensure that messages are coming from […]

Read More

Leave a Reply

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