| VMware App Volumes 2.18.6 | August 20 2020 | 2.18.6.24 Check for additions and updates to these release notes. |
What is in the Release Notes
The VMware App Volumes 2.18.6 release includes critical fixes.
What's New
- LDAP support for channel binding
In response to the March 2020 ADV190023 | Microsoft Guidance for Enabling LDAP Channel Binding and LDAP Signing, App Volumes Manager and agent have been upgraded to use channel binding. Configure App Volumes Manager to use LDAPS or LDAP over TLS to support the new Active Directory security modes. For more information, see KB article 77093.
- Security Updates
This App Volumes release includes an update to jQuery.
Administrators may need to clear their browser cache before accessing the App Volumes Manager to ensure the new jQuery version takes effect.
Internationalization
App Volumes documentation is available in English.
Resolved Issues
During a volume (.vmdk) replication, if the volume’s metadata does not get replicated then the volume’s status is displayed as "Legacy" in the App Volumes Manager UI at the replication site. The volume’s attributes and corresponding Program icons and data might be missing from the UI. [2573570]
A Javascript error occurs and Microsoft Teams fails to start when this application is installed in the base image of a Windows Server 2019 machine and an AppStack is assigned to the machine. [2571462]
In App Volumes agent 2.18.2 to 2.18.4, when Outlook is present in AppStacks, the Preview feature in Outlook fails for Office attachments such as Word and Excel. Instead of seeing the preview of the attached document, the end user receives an error message that begins with: This file cannot be previewed because of an error with the following previewed:. [2573397]
Environment variables in the system volume are overwritten by the environment variables of the AppStack or Writable Volume. As a result, applications that depend on the system volume’s environment variables might not function properly. [2572397]
Applications can stop working due to memory leaks in svdriver. [2575927]
When Autodesk Desktop Connector application is installed on the base image and an end-user with a Writable Volume starts the application, the application is expected to respond immediately. Instead, the application's menu takes a long time to pop up on right clicking the system tray notification icon. [2558093]
When directly upgrading to App Volumes Manager 2.18.x from versions earlier than App Volumes Manager 2.15, the upgrade finishes but the App Volumes Manager server fails to start. [2537337]
After recomposing VDIs, some of the VDIs with computer-assigned AppStacks fail to power on with the following error message Failed to lock file. This occurs due to some internal failure when the computer shuts down which results in AppStacks not getting detached from the computer. [2602102]
Guest Introspection provides a library called EPSeclib which allows the consumers to capture and query in-guest context or events such as file, network, process, and registry. One of the APIs in the library EPSecQueryRegistry failed in the presence of App Volumes with the following error in Guest Introspection (vsep) debug logs: QueryRegistryData failed for path \Registry\Machine\SOFTWARE\Microsoft\Windows NT\CurrentVersion, ns = 0xc0000001. [2557540]
When using volumes on shared storage, an undefined method 'path' error might occur when one of the storage devices is removed or becomes temporarily inaccessible. [2527405]
Known Issues
Writable Volumes created with profile-based templates on Windows 10 versions before 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 VMware Dynamic Environment Manager or roaming profiles, a new .ost cache file is created in the user’s volume upon each login.
When many users are logging into their desktops simultaneously, Writable Volumes may not get created for a few users and they might 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 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 many 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.18.
Workaround: See the Knowledge Base article 67482.
