| VMware App Volumes 2303 | 30 MAR 2023 | Build 4.10.0.27 Check for additions and updates to these release notes. |
VMware App Volumes is a real-time application delivery system that enterprises can use to dynamically deliver and manage applications.
VMware App Volumes 4, version 2303, Release Notes lists New Features, Resolved Issues, and Known Issues for this release.
Admins can specify credentials for the App Volumes agent to use to access the file shares when using VHD In-Guest operation mode.
This feature allows users also to explore the solution preview for deploying App Volumes Manager to Azure. For information about how to deploy App Volumes Manager to Azure, see the VMware App Volumes Manager Deployment Guide for Azure at VMware Docs.
The number included after each resolved issue refers to the issue logged in the VMware internal issue tracking system.
Users might not receive assigned applications when logged into an agent computer running Microsoft Windows Server 2016 and later due to a mismatch in the OS type. In the App Volumes Manager admin UI, the OS column in the COMPUTERS tab incorrectly displays DESKTOP instead of SERVER. [3116072]
App Volumes applications are attached at login (classic delivery mode) to host machines which are configured to receive an on demand VMware Horizon published application. These applications are unnecessarily attached at login when a published application is launched. As a result, both the published application and any classic assignments are delivered. However, there is no impact to end user. [3116474]
The DeliverAppsAtLogin parameter can be used to resolve this issue.
For more information about package delivery modes, see the Understanding Package Delivery Modes in App Volumes section in the VMware App Volumes 4 Administration Guide at VMware Docs. For more information about the DeliverAppsAtLogin parameter, see the Parameters for Configuring svservice section in the VMware App Volumes 4 Administration Guide at VMware Docs. For more information about a VMware published application on demand, see the Configure Horizon 8 for Published Applications on Demand Delivery in the Windows Desktops and Applications in Horizon 8 guide at VMware Docs.
After the App Volumes agent installer rolls back during an upgrade, the App Volumes agent installation fails the subsequent time due to the presence of tmf files. [3109366]
Simulated shortcuts of on-demand packages cannot be stored and reused. These shortcuts are deleted after package attachment and before virtualization. As a result, when end users launch the stored, simulated shortcut after a package is attached to the agent computer, the following message is displayed App delivery failed. Unable to deliver the application at this time. Please try again later. [3091113]
The number included after each known issue refers to the issue logged in the VMware internal issue tracking system.
With two Active Directory domains in a parent-child relationship where users from both parent and child domains are members of a group of the parent AD domain, if an application is assigned to such a group, then the application is delivered only to the group members of the parent domain but not to the group members of the child domain. [AVM-28519]
Application managed by an App Volumes source instance is incorrectly shown in the drop-down box when selecting a destination application during a package Move operation in an App Volumes target instance. As a result, synchronization and other operations such as delete, assign, or unassign fails for the moved package.For more information about App Volumes Instances for application synchronization, see Configure Multiple App Volumes Instances for Application Synchronization section in the VMware App Volumes 4 Administration Guide at VMware Docs. [3119867]
Workaround:
Move the package back to the source application. To move the package, perform the following steps:
Navigate to the Packages tab.
Select the package that you want to move back to the source application.
Click Move.
On the Move package page, select the source application in the Application drop-down box.
Click Move.
For more information, see Move a Package section in the VMware App Volumes 4 Administration Guide at VMware Docs.
NOTE:
If you have deleted the source application, then you must create another application with the same source application name. When creating the application, ensure that you do not select the Create a package checkbox. For the package move, follow the instructions as mentioned earlier.
Applications packaged on Windows 11 are shown as packaged with Windows 10 in App Volumes Manager. [2841689]
An application assigned to an RDS server using App Volumes Manager is not listed in the Horizon Console. As a result, a Horizon administrator is unable to create an application pool with the application assigned to the RDS server. [AVA-20887]
Workaround:
On the RDS server where agent is installed, locate the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svdriver\Parameters, create a REG_DWORD value OverrideSkipHzWsnmAppScanCalls, and set the value to 1.
Restart the RDS server.
If a VMDK of an application package contains a square bracket, '[', the package does not get imported to App Volumes. As a result, the package is not listed in the Inventory tab of the App Volumes Manager admin UI. [3034059]
Workaround: Rename the VMDK and import the package again.
App Volumes Manager installation fails with the following error: Unable to install App Volumes Manager with region language (Control Panel setting) except English when the language setting on the virtual machine is Arabic. [2884143]
Workaround:Change the language to English and then install App Volumes Manager.
If the SFN (Short File Name) of a folder is changed during capture and after assignment the folder is searched using the updated SFN, then the following error is displayed "System cannot find the the file specified". When the folder is searched using the original folder name, search results display the folder with the updated SFN. [3116360]
When an EXE is present in both C:\Windows\System32\ and C:\Windows\SysWOW64\, and the EXE is referenced in an HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run key, App Volumes must use the SysWOW64 version. Instead, App Volumes currently uses the System32 version, which might behave incorrectly. [3153660]
An OS junction point from a native folder that belongs to a banned list to a non-virtualized folder (such as %APPDATA% in configurations that do not use UIA+Profile Writable Volume or a Profile-only Writable Volume) does not work properly. Files written to the junction source do not appear in the junction target. [3006443]
In a multi-session environment, the error associated with the Microsoft Office application is also visible to users who are not assigned this application package. While the application does not behave as expected for the users assigned to this package, the error has no effect on users who are not assigned to the package. [3072078]
Applications cannot write large string values (several hundred thousand characters) to the registry. [3034063]
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: Deactivate the Cloud Cache feature of FSLogix Office Container.
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.
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 spoolerIf 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")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.
VMware App Volumes Documentation
For information about how to install, deploy, and upgrade VMware App Volumes, see VMware App Volumes 4 Installation Guide.
For information about how to configure and use VMware App Volumes, see VMware App Volumes 4 Administration Guide.
VMware App Volumes documentation is available at VMware Docs.
App Volumes content is available only in English.
To receive support, access VMware Customer Connect.
Alternately, to file a Support Request in Customer Connect and via Cloud Services Portal, you can use the information presented in this KB article .
