VMware App Volumes 2212 | 12 JAN 2023 | Build 4.9.0.41

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, Release Notes lists New Features, Resolved Issues, and Known Issues for this release.

What's New

  • Horizon 8 version 2212 in conjunction with App Volumes 4, version 2212 introduces Horizon Published Apps on Demand.

    With this new feature, administrators can use App Volumes applications directly in their instant-clone RDS farms. Now applications can be delivered dynamically to a generic Windows OS as users launch them. This dynamic application delivery greatly simplifies static image management and gives administrators the ability to reduce their application specific farms. This feature also brings the Horizon and App Volumes administration consoles closer together, allowing Horizon administrators to add App Volumes Manager servers and entitle applications to users without the need for duplicate entitlements in App Volumes.

    This feature creates an opportunity to reduce the time-consuming management of application installations on RDS farms, and enables scenarios such as multiple users being able to use different versions of the same application whilst logged in to the same RDS server.

  • When multiple users are logged in and using application packages, disks remain attached until the last user using the package logs out.

  • With multi-session operating systems, more than one package for an application can be delivered to a single Windows machine.

    Compatibility to deliver more than one package to a single Windows machine depends on the application. The RDS package attachment option allows administrators to specify which applications should and should not have multiple packages from the same application delivered.

  • On the Edit Package window, in the App Volumes Manager admin UI, the Notes field can now be updated.

  • Login performance improvements using on-demand delivery with many applications.

Resolved Issues

The number included after each resolved issue refers to the issue logged in the VMware internal issue tracking system.

  • Shortcut data does not get captured in the metadata.json file for shortcuts with path length more than 260 characters. As a result, application shortcut does not appear when the application is delivered on-demand. [3038371]

  • Certain applications with many icons related to file type associations might increase the login duration due to the time taken to transfer the icon content to the virtual machine. [2989141]

    Workaround: Turn off the file type associations feature (CaptureFTA) on the machine that is used to package these applications. For more information about the CaptureFTA parameter, see the Parameters for Configuring svservice section in the VMware App Volumes 4, version 2206 Administration Guide.

  • When the Box Drive application is assigned to a computer and any user logs into that computer, application launch fails when using the shortcut and the following error is seen: This action is not allowed for application ‘Box’. Please contact your administrator. [3002403]

  • File Explorer is slow when processing files in folders that contain large numbers of files. [3029679]

  • Towards the end of an in-app Chrome update, the user is prompted to relaunch Chrome to complete the update process. When natively installed, the current version of Chrome exits and the newer version opens immediately. With App Volumes, though, after the current version of Chrome exits, the newer version of Chrome opens after a delay of several minutes and there is no visible activity on the user computer until then. [3038483]

  • In Windows 11 configurations that include a UIA+profile Writable Volume, printers deleted by means of the Windows GUI might reappear in subsequent sessions. [3029793]

  • ArcGIS and related applications, such as ArcMap, are slow in the presence of App Volumes, even when ArcGIS is natively installed. [3036343]

  • Some 32-bit registry operations fail during App Volumes packaging. As a result, when the following custom PowerShell script is run on a 64-bit virtual machine which has 32-bit Office 365 natively installed, the second command does not display the expected operating system information. [3050432]

    $msoExcel = New-Object -ComObject Excel.Application 
    $msoExcel | Select-Object -Property OperatingSystem

    In versions earlier than App Volumes 4, version 2212, to achieve the correct output, an App Volumes packaging optimization registry key, OptimizationLevel must be turned off by setting the registry value to 0 (reg add HKLM\SYSTEM\CurrentControlSet\Services\svdriver\Parameters /v OptimizationLevel /t REG_DWORD /d) and prior to packaging, the operating system must be restarted. Note that optimization is turned on (registry value is 1) by default.

Known Issues

The number included after each known issue refers to the issue logged in the VMware internal issue tracking system.

  • Applications packaged on Windows 11 are shown as packaged with Windows 10 in App Volumes Manager. [2841689]

  • 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 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 no 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 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")
  • 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.

Documentation

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.

Internationalization

App Volumes content is available only in English.

Support Contact Information

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 .

check-circle-line exclamation-circle-line close-line
Scroll to top icon