The App Volumes operation mode is determined by configuring the Machine Manager. The Machine Manager determines the type of hypervisor connection.

Three types of hypervisor connections are available. You can configure the hypervisor to connect to one of the following hosts using the App Volumes Manager console. See Establish a Secure vCenter Server Connection to learn how to set up a secure connection to vCenter Server.
Note: If you are configuring App Volumes Manager on VMware Cloud on AWS, and you select vCenter Server as the hypervisor, you must check the vCenter on VMware Cloud on AWS option. See Configuring App Volumes Manager for VMware Cloud on AWS for more information.
Table 1. Hypervisor Connection Types
Hypervisor Connection Type Description
VMware vCenter Server Preferred connection type for mid-to-large environments. Enables the use of VMDK Direct Attached operation mode. When using this connection type, you can assign Applications, Packages, AppStacks, and Writable Volumes to the virtual machines running on multiple hypervisor hosts.
Single ESXi Host Enables the use of VMDK Direct Attached Operation Mode, but only for a single ESXi host. Use this connection type for small deployments and proofs of concepts. You can assign Applications, Packages, AppStacks, and Writable Volumes to the virtual machines running on a single hypervisor host.
VHD In-Guest Services Disables other hypervisor connections and enables the use of VHD In-Guest operation mode. Use this connection type to assign Applications, Packages, AppStacks, and Writable Volumes either to virtual machines running on an unsupported third-party hypervisor or to the physical computers. See Configure VHD In-Guest Storage.
Note: You cannot change the operation mode after you configure the Machine Manager. However, if you have configured vCenter Server as the first Machine Manager, additional vCenter Server instances can be added and configured.

Reconfigure vCenter Server

If you regenerate new certificates for ESXi hosts and you have selected vCenter Server as your machine manager, with the Mount ESXi option, you must reconfigure your vCenter Server.

See Regenerate Certificates for an ESXi Host section in the VMware vSphere ESXi and vCenter Server 5 Documentation.

vCenter Server Permissions

The following permissions are required if you are configuring a vCenter Server as the machine manager.

You also require these permissions if you choose the Mount ESXi option when you are configuring the machine manager.

Note: Datastore browsing must be enabled for the App Volumes Manager to enumerate volumes on the datastore. Check the enableHttpDatastoreAccess parameter under C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg in the vCenter Server. If it is set to false, change this to true and restart the vCenter Server service.
Permissions
Datastore
  • Allocate space
  • Browse datastore
  • Low level file operations
  • Remove file
  • Update virtual machine files
Global Cancel task
Host Local Operations -> Reconfigure virtual machine
Note:
  • Host permission is required when using the Mount ESXi option.
  • Mount ESXi option is not available for the VMware Cloud on AWS environment.
Sessions View and stop sessions
Note: This permission is not required for the VMware Cloud on AWS environment.
Tasks Create task
Virtual machine
  • Configuration
    • Add existing disk
    • Add new disk
    • Add or remove device
    • Query unowned files
    • Change resource
    • Remove disk
    • Settings
    • Advanced
  • Inventory
    • Create new
    • Move
    • Register
    • Remove
    • Unregister
  • Provisioning
    • Promote disks