VMware App Volumes 2.15 Release Notes

VMware App Volumes 2.15 | 13 DEC 2018

Check for additions and updates to these release notes.

What's in the Release Notes

The VMware App Volumes 2.15 release includes the following new features, updates, and bug fixes.

Profile-only Template for Writable Volumes - The App Volumes agent now leverages a new dual-write capability to ensure support of AppStacks while retaining only the files related to the user’s profile. Also new with this feature is an ability to specify folders within the profile to be excluded, giving administrators additional controls to reduce files persisted to a user’s Writable Volume.
App Volumes on VMware Cloud on AWS - Using App Volumes 2.15 or later you can configure vSphere to work with VMware Cloud servers.
Microsoft OneDrive For Business Support - Improved support for Office 365 on non-persistent desktops using Writable Volumes to persist OneDrive’s local files across login sessions.
Box Drive Integration - Box Drive version 2.1.105 or later is now supported on App Volumes 2.15 using Writable Volumes to persist credentials and file cache.
Support for Microsoft Windows 10, version 1809 SAC and LTSC

If App Volumes Manager is configured to use smart domain controller discovery and a domain controller is not available, Agent NTLM authentication may fail even if other domain controllers are available.
If a new ESX host is added with Mount on Host selected, AppStacks do not get attached to agent VMs on the new ESX host.
Volumes are not attached to an instant clone VMs when the VM folder location contains both non-ASCII and high-ASCII characters.
Palo Alto Networks Traps exploit protection modules do not function without specifying exclusions.
If you upgraded to 2.14, App Volumes Manager does not show the shared datastores locations for volumes.
In some cases when installing App Volumes Manager, "Error installing SQL Server Express" message is displayed requiring users to complete installation on their own.
In rare cases, “Exception: Circular dependency detected while autoloading constant” error message is displayed when App Volumes Manager is configured with multiple domains.

Users who have Writable Volumes created with the UIA+Profile template on Windows 10 1703 will encounter Start Menu issues after using the same volume on later versions of Windows.
When using Microsoft Outlook Cached Exchange Mode with a UIA-only type Writable Volume and no profile persistence solution such as UEM or roaming profiles, a new .ost cache file will be created in the user’s volume upon each login.
OST and search index redirection is not enabled in the profile-only template for Writable Volumes.
When creating custom administrator roles, granting view privilege to either AppStacks or applications will effectively grant view privileges to both functions.
During a login storm, when a large number of users are logging into their desktops simultaneously, Writable Volumes may not get created for a few users and they may not be able to log in to a desktop.
Note: This issue does not occur if the users already have an existing Writable Volume.
Workaround: The users must must log in again or have an administrator pre-create the Writable Volume for the user.
A Writable Volume move or copy operation may fail when bulk operations are performed on a large number of volumes.
Workaround: Retry the move or copy operation.

App Volumes documentation is available in English.