VMware App Volumes 2.13 Release Notes

|

VMware App Volumes 2.13 | 19 OCT 2017 

Check for additions and updates to these release notes.

What's in the Release Notes

This release notes for App Volumes 2.13 covers the following topics:

Check for additions and updates to these release notes.

About VMware App Volumes

VMware App Volumes provides a system to deliver applications to desktops through virtual disks. Applications are bundled in AppStacks and delivered by attaching a standard VMDK file to a virtual machine. You can centrally manage the applications with the App Volumes Manager and there is no need to modify the desktops or individual applications. Applications that are delivered by using App Volumes look and feel natively installed and you can update or replace the applications in real time.
All applications are provisioned during login time and App Volumes enables users to have a persistent user experience wherein users can install their own applications and have them persist across sessions.

App Volumes is intended for use on non-persistent desktops.

For more information, see the VMware App Volumes documentation.

What's New in This Release

The 2.13 release of VMware App Volumes includes the following new features and enhancements:

  • Support for concurrent AppStack assignment
    You can assign AppStacks to computers and users concurrently which results in improved login times. The AppStack is attached to the user when the user logs in and the computer-based AppStack is attached when the computer starts up.
  • Limiting AppStack attachments
    You can limit the number of active attachments of an AppStack and configure each AppStack with the maximum number of concurrent assignments that you want to allow.
  • Troubleshooting archives
    You can use App Volumes Manager to create archives of server logs and configuration files and download these files for troubleshooting App Volumes.
  • Important enhancements to secure connection to Active Directory
    You can choose to connect securely from App Volumes Manager to an Active Directory using a CA root certificate, using either LDAPs (default) or LDAP over TLS.
  • App Volumes Manager is supported on SQL Server 2016 and Microsoft Windows Server 2016. App Volumes agent supports Microsoft Windows Server 2016 and Windows 10 1703.

Miscellaneous Updates

  • Support for TLS v1.0 protocol
    By default, communication over TLS v1.0 protocol from App Volumes agent is disabled. However, you can enable the communication using TLS v1.0 while installing the App Volumes agent, or by modifying the Nginx configuration file after installing the agent.
  • Improved Reverse Replication
    Reverse replication option now runs in parallel with log in and can be delayed to allow the OS to complete resource intensive login activities.

Security Updates

App Volumes 2.13 release includes updates to many open source libraries. The updates resolve a variety of issues ranging from functional issues to security vulnerabilities. The copyright statements and licenses applicable to the open source software components distributed in VMware App Volumes 2.13 are available on the Open Source tab of the product download page. You can also download the source files for any GPL, LGPL, or other similar licenses that require the source code or modifications to source code to be made available for the most recent available release of App Volumes.

Resolved Issues

The following issues have been resolved in this release:

  • Issue with Smart Domain Controller when a private class IP address in not used.
  • Application issues with Internet Explorer.
  • UI issue with duplicate application icons.
  • Visio/Project reconfiguration issue seen when deployed with same native Office image used for provisioning.
  • Broken icons and search issues occurring during subsequent logins with Windows 10 1607 and Writable Volumes.
  • Start menu will not launch on Windows 10 1607 with Writable Volumes after March cumulative update.
  • Cases with 100% CPU consumption after deployment of Office in an AppStack.
  • Files that are flagged as downloaded from internet or untrusted fail to open with Office applications when a Writable Volume is attached.
  • Cannot insert duplicate key row in object dbo.users with unique index 'index_users_on_upn'.
  • Writable Volume was not attached as 1000 error was returned from App Volumes Manager
  • Trust between vCenter Server and App Volumes is lost when a SQL failover situation occurs.
  • Log noise containing the following text: Unable to find known VM with Instance UUID is fixed.
  • Performance challenges with Office under certain conditions.
  • Virtual machine attached with an AppStack or Writable Volume freezes when searching for files and docs under C drive.
  • Some machines offline after provisioning 2K instant clone pool.
  • Error getting naming_contexts: An existing connection was forcibly closed by the remote host.
  • MS Short File names: GetFinalPathNameByHandle/FILE_NAME_OPENED normalizes the path.
  • Recycle bin does not show multiple files upon deletion of files and folder.

Known Issues

  • In some instances, desktops are unresponsive when there are a large number (more than 2K) logons and the message Unable to secure your writable volume error is displayed.
    Workaround: Log out and log in to the desktop again.
  • All Writable Volumes are shown as duplicated in the App Volumes Manager when an existing vSAN datastore is deleted and a new vSAN datastore is created.
  • If vCenter fails to return VM information, App Volumes Manager may mark some VMs as missing and offline even though the VMs are alive and responsive. During a cleanup later, App Volumes Manager may mark these VMs as deleted.
    Workaround: Reboot the VMs to recover the "missing" VMs.
  • A Writable Volume may sometimes fail to get created due to an error from vCenter. The volume is unavailable to the user and the error InvalidArgument: A specified parameter was not correct:fileType is displayed.
    Workaround: Log out and log in to the desktop again.
  • You cannot upgrade App Volumes Manager if you have installed VMware vRealize Log Insight Agent on the same VM where App Volumes Manager is also installed.
    Workaround: Open services.msc from the desktop and stop the VMware vRealize Log Insight Agent service and retry the operation. You can restart the VMware vRealize Log Insight Agent service after the upgrade is completed.
  • In a large-scale deployment of App Volumes, a few users may sometimes get disconnected within minutes of logging in, and in a View deployment, View firewall policies are seen to be deleted. The user may also see one of the following error messages on every connection attempt:
    The display protocol for desktop is currently blocked by firewall. Please contact administrator or
    The connection to the remote computer ended.
    Workaround: Run a cleanup script and log in to the desktop again. See KB 2151948 for detailed instructions.
  • AppStacks do not get attached if ESX certificates are regenerated for ESX host when Mount on host option is enabled.
    Workaround:Configure vCenter machine manager again from App Volumes Manager.

Internationalization

VMware App Volumes 2.13 product documentation is available in English.