| VMware App Volumes 2.16 | 14 Mar 2019 | Build 2.16.0.62 Check for additions and updates to these release notes. |
What's in the Release Notes
The VMware App Volumes 2.16 release includes the following new features, updates, and bug fixes.
What's New
- SQL Server 2008 is no longer supported. Customers must upgrade to a supported version of SQL Server prior to upgrading.
- Administrators can now see a list of all the App Volumes Managers of their instance from with-in the App Volumes Manager console.
- App Volumes Manager secure registration is automatically activated for new installations of 2.16 and later. Customers upgrading to the latest version of App Volumes are encouraged to activate the new registration feature.
Note:Secure registration is automatically activated on environments with only one manager. - Support for App Volumes Manager on Windows Server 2019.
- General security updates.
Resolved Issues
- 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 1709.
- OST and search index redirection is not enabled in the profile-only template for Writable Volumes.
- When you log in to a VDI session with a Writable Volume attached and change Firefox settings, the changes are not saved when you close and restart Firefox.
- vCenter may exhibit high memory usage when Horizon is cloning VMs.
- When certificates are misconfigured, the message The system needs to be rebooted. Please reboot or contact your system administrator. is displayed.
- VM takes a long time to boot or log in when the App Volumes agent is installed on a non-domain joined VM.
- When moving from Storage tab from Machine Manager tab, App Volumes Manager throws Unable to save certificate of EndPoint ODBC error.
- Unable to launch BAT file from Windows explorer and instead presented with a security dialog.
- Cannot enable or disable McAfee anti-virus software when an AppStack is attached.
- Undefined method 'upn' exception when record of a user who is online is deleted.
- On App Volumes Manager, 2 to 5 wrong password attempts results in lockout even if the account lockout policy is configured for 10 attempts.
- When groups are added under Administrator Role links do not work as expected in App Volumes Manager.
- App Volumes Manager (Directory -> Users) user page resolves user assignment information if the assignment has been made through a group.
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.16.
Workaround: See the Knowledge Base article 67482.
Internationalization
App Volumes documentation is available in English.
