clush
Contributor
Contributor

App Volumes Assignments

Hello,

I am new to the community and fairly new to vmware.

I have recently created a app stack through a provisioning machine.

As a test i assigned my domain account permissions to the app volume.   We currently have two domains in our organization one said that there was no licence for it but the other domain had a licence which I gave myself permissions.  It shows that I have successfully added myself and at next logon the applications will be attached

However when i log into a pool those apps are not attached.

My question is do you need the app volumes agent installed on the systems that you are trying to attach the apps to?   The agent was installed on the provisioning machine.

Also can you attached apps to a system that is connected to the domain but not a virtual machine.  And if so do you need to have the agent installed.

Any help would be greatly appreciated.

Thank you,

Craig

Reply
0 Kudos
Lakshman
Champion
Champion

Welcome Craig.

App Volumes agent must be installed on all the deployment VMs where you want to use AppStack or Writable volumes. If you are using VMware Horizon you can install the agent on the master image before creating pools.

When it comes to AppStack assignment, it can be assigned to users, groups, computers (domain) and OUs. By default, non domain entities are not allowed but it is possible to allow if required. Hope this helps.

Reply
0 Kudos
clush
Contributor
Contributor

Hi,

Thanks for the info.  I did install the agent on a local machine within our domain however the agent will not connect I get an error unable to connect to App Volumes Manager.  Virtualization is disabled.

I tired both the FQDN as well as the IP of the App Volume server.  

I do have it setup the same way as the provisioning computer which it works on. 

I wonder if it is a VLAN issue?

Thanks,

Craig

Reply
0 Kudos
Ray_handels
Virtuoso
Virtuoso

For the record. For testing purposes I would use a Virtual machine (creating a pool would be nice with VMView but not necessary).

That being said, you should always be able to connect to the Appvolumes manager server. Do you have a valid certificate for the Appvolumes Manager? If not, try to create one or make sure that your agent has the following registry key

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svservice\Parameters\EnforceSSLCertificateValidation=0 (DWORD)

Also, if you go to the FQDN of your Appvolumes manager, are you able to logon from the virtual machine you are starting up??

I would also suggest starting with the admin guide before you begin. It is quite well written if you start with Appvolumes and it gives you an idea of what it is capable off.

Reply
0 Kudos