VMware App Volumes 4, version 2111.1

VMware App Volumes 4, version 2111.1 | February 22 2022 | 4.5.1.10

Check for additions and updates to these release notes.

What is in the Release Notes

The release notes cover the following topics:

Internationalization
Resolved Issues
Known Issues

The VMware App Volumes 4, version 2111.1 includes bug fixes.

Internationalization

App Volumes documentation is available in English.

Resolved Issues

Unable to register an additional App Volumes Manager server via HTTPS within the same App Volumes Manager instance and the following error is displayed: Failed to connect Manager Service with guid <> to "user@host:443". [2907577]

Known Issues

Desktop shortcuts for an on-demand application is not visible to an end user if desktop folder redirection is activated for the end user. [2953681]
Applications packaged on Windows 11 are shown as packaged with Windows 10 in App Volumes Manager. [2841689]
When creating Writable Volumes for a group with many users before user login (Delay check box is not selected), the Create Writable Volume page times out with a Server Timeout error. However, the background job for creating Writable Volumes continues to run and Writable Volumes are created for the group. [2722421]

Workaround: To continue performing further operations, refresh the App Volumes Manager Admin UI.
After upgrading to VMware App Volumes 4, version 2203 or VMware App Volumes 4, version 2111, SVservice fails to run scripts that are placed in %SVAgent%\Config\Default\System and %SVAgent%\Config\Custom\System. [2969412]

Workaround: None
Application installers that create data at a sub-path of HKLM\System\CurrentControlSet\Control\NetworkProvider registry key might impact application behavior and the application might not work as expected. The symptoms vary and are dependent on the application. A common symptom is that when the application is captured, the modified registry data at the sub-path of HKLM\System\CurrentControlSet\Control\NetworkProvider is created on the base volume instead of in the application package. As a result, the application does not behave as expected. For example: In one of the scenarios, the single sign on functionality did not work for an application. [2871141]

Workaround: Before deploying the application package, create the application data on the VDI image and roll out the updated image. Deploy the application package, test the application, and ensure that the application behaves as expected.
When a Writable Volume and FSLogix Office Container are deployed together in a VDI, the FSLogix Office Container VHD is not created on an SMB file share. This issue occurs only when the Cloud Cache feature is enabled. [2791414]

Workaround: Disable the Cloud Cache feature of FSLogix Office Container.
When a remote printer is defined on a UIA+Profile Writable Volume and the printer is attached to its print server through a USB interface, the printer definition on the Writable Volume might get deleted on the next non-persistent logon. [2845852]

Workaround:

On the system volume, add the following two scripts to %SVAgent%\Config\Custom\uia_plus_profile:
```
OnPreLoadApp.bat:
sc config spooler start= disabled
net stop spooler

OnPostEnableApp.bat:
 sc config spooler start= auto
 net start spooler
```
If you already have the same script names on the Writable Volume, add the spooler commands to the scripts.

When a script is present on a Writable Volume and in the system volume at %SVAgent%\Config\Custom\uia_plus_profile, App Volumes agent runs the script present on the Writable Volume and ignores the script on the system volume. To ensure that the App Volumes agent runs both scripts, you can add the following to the script on the Writable Volume:
```
if exist "%SVAgent%\Config\Custom\uia_plus_profile\%~nx0" ( "%SVAgent%\Config\Custom\uia_plus_profile\%~nx0" )
```
When many users are logging into their desktops simultaneously, Writable Volumes might not get created for a few users and they might not be able to log into a desktop. This issue does not occur if the users already have an existing Writable Volume. [2115623]

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. [2115593]

Workaround: Retry the move or copy operation.
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]

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: https://kb.vmware.com/s/article/59666.
App-V packages do not load when App Volumes agent is used either with a UIA+profile or Profile-only Writable Volume. [2434176]
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 is fixed in App Volumes 2.18.2 and later. [2624048]

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.