| VMware App Volumes 2212.2 | 11 APR 2023 | Build 4.9.2.18 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 2212.2 includes bug fixes.
In this release, we have made a few updates containing general quality and performance improvements with no new features.
The number included after each resolved 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]
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. [3154675]
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. [3150711]
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 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.
The number included after each known issue refers to the issue logged in the VMware internal issue tracking system.
MSIX application packages fail to attach to a different OS even when the Allow package delivery to any operating system, an advanced setting, is enabled and the following error can be seen in System Messages in the App Volumes Manager admin UI: MSIX Package <Package Name> locked to <Package OS> was not attached to <Computer Name> because it is not allowed on <User’s Machine’s OS> [AVM-33322]
When SSL verification for an App Volumes target instance happens through a cacert.pem file present in the config directory where App Volumes Manager is installed, the following error is displayed: Error while retrieving the certificate. Unable to find the certificate for the target manager instance. After a while, the error is not visible. [AVM-31353]
NOTE: This is a UI display issue and causes no functional impact.
If it is not possible to determine the Active Directory site from an IP address or subnet, a default Active Directory site is not set. This might result in App Volumes Manager contacting Domain Controllers out of its (App Volumes Manager's) Active Directory site. [AVM-28680]
Application packages and Writable Volumes cannot be attached to instant-clone desktop pools which have the Add vTPM Device to VMs option selected in the Horizon console. [AVM-31057]
For more information about the Add vTPM Device to VMs option, see the Windows Desktops and Applications in Horizon 8 documentation.
For more information about the Virtual Trusted Platform Module (vTPM), see the vSphere Virtual Machine Administration documentation.
Workaround: Follow the instructions as mentioned in this knowledge base article.
After enabling the Mount ESXi option in the Machine Managers page and when saving this setting, the following error is visible in the App Volumes Manager admin UI: Failed to connect <n> of <n> hosts <host1.com> <host2.com> <hostn.com> [AVM-31066]
When accessing DocuSignPrintDriver, delivered as an application package, the printer becomes unavailable due to issues in registry virtualization. If trying to view the printer properties then the following DocuSignPrintDriver Printer Properties error message is displayed: The 'DocuSignPrintDriver' printer driver is not installed on this computer. Some printer properties... [AVA-23718]
"new Microsoft Teams" application fails to launch when Profile-only or UIA+profile Writable Volume is attached to the agent computer.
NOTE: When this issue occurs, no error message is displayed by the application. [AVA-23756]
Applications packaged on Windows 11 are shown as packaged with Windows 10 and applications packaged on Windows server 2019 and Windows server 2022 are shown as packaged with Windows server 2016 in App Volumes Manager admin UI. [AVM-29123]
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.
End users with a Writable Volume experience an increase in the login time if there is a difference in the registered MOF (Managed Object Format) entries between the base virtual machine and the Writable Volume. [AVA-23247]
When an App Volumes application package or Writable Volume includes a printer specification and the memory integrity feature is enabled, Windows crashes at startup. [AVA-23138]
Memory integrity is a virtualization-based security (VBS) feature. This feature is sometimes referred to as hypervisor-protected code integrity (HVCI). For more information about this feature, see the relevant Microsoft documentation.
After the Windows update of "September 12, 2023—KB5030219 (OS Build 22621.2283)" on a VM with either an application package or Writable Volume attached, Windows start menu and search do not respond. [AVA-23022]
Workaround: Create the file "%SVAgent%\Config\Custom\Snapvol.cfg" on the base image with the following content: exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\PolicyManager\default
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.
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 .
