VMware App Volumes 2012.3 | 07 JUL 2022 | Build 22.214.171.124
Check for additions and updates to these release notes.
The VMware App Volumes 4, version 2012.3 includes security updates, bug fixes, and known issues.
App Volumes content is available only in English.
Due to the issue related to the high number of snapvol_operating_systems records for the AppStacks and Application Packages, the volume imports and replications are slow and the App Volumes Manager admin UI is slow to load the Volume (2.x) page. 
Writable Volumes (2.x) are not automatically created for newly added members of an Active Directory group. 
Workaround: Create the Writable Volume manually for the user.
When automatic application import is enabled for a storage group, multiple Import Applications jobs can be scheduled for different storage locations. The jobs might run at the same time which results in the applications taking a longer time to import. This results in errors which can be viewed in the ACTIVITY -> System Messages tab of the App Volumes Manager UI. The applications eventually get imported. 
Workaround: In the App Volumes Manager Admin UI, navigate to the ACTIVITY -> Jobs tab and increase the Import Storage Groups job interval.
Package replication fails if the metadata of a package is updated and the package is replicated from a read-only storage. App Volumes Manager skips writing the updates to the read-only storage and the package does not get replicated. 
Workaround: Configure the storage to have a read/write permission. Alternately, upgrade to App Volumes 4, version 2103.
When certain App Volumes background jobs such as Import Applications take a long time to complete, volume replication does not occur across multiple manager instances and end users are unable to receive the application packages. 
Workaround: From the manager on which replication fails, update the package properties (for example: modify the package description) and perform the replication again.
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. 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 might fail when bulk operations are performed on many volumes. 
Workaround: Retry the move or copy operation.
App-V packages do not load when App Volumes agent is used either with a UIA+profile or Profile-only Writable Volume. 
Sometimes, the applications that are packaged using App Volumes versions older than 2.18.2 have many redundant firewall rules. These rules can impact the end-user login time on agent computers where the application package is deployed.This issue has been fixed in App Volumes 2.18.2 and later. 
Workaround: If you are migrating an application package created in an App Volumes version earlier than 2.18.2 with such an issue, repackage the application after migrating to the target version.
Invalid session cookie issue occurs intermittently at end user login or logoff and can be seen in the ACTIVITY -> System Messages tab of the App Volumes Manager UI. When the issue occurs during login, volume attachments might fail and the following error message is displayed on the agent computer: Volumes were not mounted due to an error on the server. [2646276, 2675527, 2689736]
Workaround: When the error occurs and login fails, the end user can log into the agent computer again. To disable the "Agent Session Cookie" settings, you can toggle the advanced setting in the App Volumes Manager UI. For more information about this issue, see the knowledge base article.