VMware App Volumes 4 | 14 January 2020
App Volumes Manager Build 18.104.22.168 | App Volumes Agent Build 22.214.171.124
Check for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
The VMware App Volumes 4 release includes new features, updates, and bug fixes.
- Applications – Records that represent an application irrespective of its versions. You can create application records to manage a collection of related packages. Users, groups, computers, or organizational units can be entitled to receive one of the packaged versions.
- Packages – Virtual disks that store one or more programs required for an application to run. A single package can be delivered to multiple computers, and one or many users.
- Programs – Installed during the packaging process. When an application is assigned and a package is delivered to a desktop, these programs are then visible inside Windows under Programs and Features and often available from the Start Menu.
- Intent-based Assignments – Mark one of an Application’s packages as current to indicate the intended version for delivery.
- Lifecycle Stages – Designate the maturity of a package by setting it from New toTested, Published or Retired.
- Application Owners – Assign active directory entities to indicate ownership to each Application.
- Application History – View a list of administrative actions that have been performed on an application and who performed them.
New Agent and Package Format
- Improved Performance – App Volumes Agent now handles more package disks per user session.
- Package Notes – Keep track of a package details by noting any specifics steps or configurations after packaging an application.
- Improved Template Management – Template policy files (snapvol.cfg) have moved out of the template disk to the base image so that it may be updated easily when updating the Agent. Manager also provides an improved management interface for uploading and maintaining templates.
- Support for Windows 10, version 1909
Upgrade from App Volumes 2.x – Manage App Volumes 4 and 2.x agent versions in the App Volumes 4 Manager. Deployments upgraded from App Volumes Manager 2.18 or later can view Volumes (2.X) in the navigation to access all the 2.x AppStacks and Writable Volumes. If necessary, new installations can enable this functionality under Advanced Settings. For more information about upgrading to App Volumes 4, see the VMware App Volumes 4 Installation Guide. You can access this documentation at VMware Docs.
App Volumes documentation is available in English.
When many 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. 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 a large number of volumes. 
Workaround: Retry the move or copy operation.
If you are in a Windows administrator role, having a rule that contains the %USERPROFILE% environment variable in snapvol.cfg is not supported. 
When a Firewall rule is present in the AppStack or Writable Volume, the Firewall Console might display the same rule twice. This is redundant and does not have any impact on the functionality and performance. 
SSH Tectia Client intermittently shows a "Failed to initialize..." error when launched. This issue depends on the operating system environment and system performance. 
Workaround: Relaunch SSH Tectia Client. If you have multiple applications, avoid launching SSH Tectia Client as the first application.
If you belong to one of the App Volumes Manager roles and delete the role assigned to the group to which you belong, you will not be able to log into App Volumes Manager again. 
Chrome fails with the "Aw,Snap!" error occurs due to compatibility issues with Chrome version or 78 and later. 
Workaround: Disable a recently activated Renderer Code Integrity security feature in Chrome. For more information about this feature, see https://cloud.google.com/docs/chrome-enterprise/policies/?policy=RendererCodeIntegrityEnabled.
Silent installation or upgrade of App Volumes Agent requires the EnforceSSLCertificateValidation parameter be set to 0 or 1. 
Use the following command to install or upgrade the agent:
msiexec.exe /i "App Volumes Agent.msi" /qn MANAGER_ADDR=<Manager_FQDN/IP> MANAGER_PORT=<port> EnforceSSLCertificateValidation = 1
For the entire install and upgrade procedures, see the relevant sections in the VMware App Volumes 4 Installation Guide at VMware Docs.