VMware App Volumes 2.17 | 2 July 2019 | Build 2.17.0.49 Check for additions and updates to these release notes.

What's in the Release Notes

• What's New
• Resolved Issues
• Known Issues
• Internationalization

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

What's New

• Support for Windows 10 1903
• App Volumes Manager can now communicate to SQL Server using TLS 1.2 protocol.
• App Volumes API reference documentation is available on VMWare {code}.
• Support for SQL server 2014 Enterprise SP3 64-bit

Resolved Issues

• System files that were unnecessarily stored in a user’s Writable Volume caused the volume to increase in size and in some cases led to issues after updating Windows.[2000289]
• If you upgrade from App Volumes 2.15 to 2.16 and have imported AppStacks from 2.15, these AppStacks are not seen in the App Volumes manager UI. [2313602]
• Desktop connection gets interrupted during login when an AppStack is attached immediately or if you log out and log in when a Writable is attached. [2325202]
• Configuration settings are not displayed sometimes when user clicks on the CONFIGURATION tab in App Volumes Manager. [2304233]
• High RAM utilization on a vCenter Server which has Horizon associated with it. [2208690]

Known Issues

• Writable Volumes created with profile-based templates on Windows 10 versions prior to 1803 may exhibit Start Menu or search related issues after using the same volume on Windows 10 versions 1803 or later.
• 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.
• 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.
• Multiple duplicate Writables are seen after upgrading from App Volumes 2.13.2 to App Volumes 2.17.
  Workaround: See the Knowledge Base article 67482.

Internationalization

App Volumes documentation is available in English.