App Volume Error Message on client (Virtualization is disabled)

[McCliver]

Test environment includes the following:

• vCeneter server (version 5.0.0,623373
• 2 Hosts (version 5.0.0,1311175)
• Acative Directoy
• App Volumes Manager installed on server 2008R2 and configured as per documentation
• App Volunes Agent instgalled on Windows 7 and pointed to the App Manager (FQDN) as per documentation

After restarting and loging on to Windows 7 client, I receved the following message below:

[Jason_Marshall]

This is a communications error. Ensure you are able to ping the FQDN used for the AV Manager from the client, check firewall etc. You can also check in the Manager under the Computers tab to see if the agent has checked in at all.

[McCliver]

Hi Jason,

Thanks for your response and you are correct that this was a communcations error.. I think that this Error is misleading but nevertheless, VMware was able to work with me to troubleshoot the issue. My POC lab is a nested virtualization environment. Consequently, this causes some issues where the AppVolume Manger could not communicate with the nested datastore. Both client and manager must be in the same layer of the virtual environment otherwise you may run into some communication s issues. The following KB article also provides additional info on nested virtual environments.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=200991...

[GChiamopoulos]

I am also receiving this error message but what I am trying to do is push an app stack to a physical machine.  I do not know if this is even possible but wanted to give it a shot. I have installed the agent on the machine but immediately upon reboot I get the error. Is there something I can do to get this to work? Just for the record it works perfect when pushing to VM's.

[GChiamopoulos]

To add a little information, I am not able to ping the app manager from the desktop.

[Jason_Marshall]

Couple things, physical needs to have the "Hypervisor" configuration set to Native In-Guest and the storage location be a network share with domain machine full control as well as a few other settings outlined in the user guide.

Also if the desktop can not see the Manager, no worky.. Basic communications have to be in place first.

[pari2k3]

While installing AV Manager select "Allow to HTTP port" and follow the KB to update the AV Agent machine Virtualization is disabled when logging in to a virtual machine with the VMware App Volumes Agent fo... .  It will work.