VirtualSpence's Accepted Solutions

I was able to reproduce the error and log entry "Manager status 500 response (50 bytes): Failed to mount volumes, no mount results returned". by connecting to a VM running on an EXSi host that didn't have access to the datastore where the package (VMDK) resides. Can you verify that the host where the desktop resides has access to that datastore?

As suggested in the thread above, AVM can manage only VMDK or VHD, not both, at this time. If you explore the VHD option, you might be interested in the App Volumes migration fling, which allows you to use VMDKs as input, and has the option to output VHDs: App Volumes Migration Utility | VMware Flings Keep in mind App Volumes requires non-persistent desktops for support. That is, the Windows OS should be reverted to a clean state between user sessions as described in this KB: VMware Knowledge Base If you're planning to use physical machines, and AppStacks/Packages are routinely being attached/detached/reattached, you will likely run into anomalies.

Which version of App Volumes are you running? The KB you're referencing states: Note: This solution can be used with App Volumes 2.12.x and 2.13.x. For AppVolumes 2.14 a solution to manage the OST file and the Search index is build-in, so that version does not require this KB anymore.

There are actually a few features applicable to 2.x AppStacks which are not yet available with v4 Packages. See Considerations before migrating from AppStacks to Packages​ for more information. The ability to select different operating systems for the Package is on the list: Option to edit the type of Operating System to which an AppStack is attached.