VMware App Volumes 2203.2 | 01 SEP 2022 | Build 4.6.2.32

Check for additions and updates to these release notes.

What's in the Release Notes

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

Internationalization

App Volumes content is available only in English.

Resolved Issues

  • Troubleshooting issues is difficult when App Volumes Manager server processes occasionally stop logging messages for each web request that typically beings with Started GET|POST /url?query and ends with Completed 200 OK in XXXms. [3017121]

  • The default size of the connection cache was not optimal when more than 15 vCenter Servers were registered, more connections than necessary might have been established. This issue is now resolved. [3017450]

  • App Volumes Manager must contact all registered VMware vCenter Servers to discover a virtual machine and link it to the Windows guest session. When there are many vCenter Servers, this results in a lot of traffic and boot storms might take longer time to end. This issue is now resolved. [3019132]

    NOTE: As an administrator, ensure unique data center names are used in each vCenter Server.

Known Issues

  • 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.

  • In the Synchronization View, applying any filter does not display the Disabled assignments and filtering with the Status field does not return any results (Enabled or Disabled assignments). Hence, assignments in the Disabled status are not displayed in the Synchronization view. As a result, managing the synchronization progress of the assignments is difficult when there are a large number of Disabled assignments. [2946144]

    Workaround: To view or manage the Disabled assignments, sort by Status in the descending order.

  • On the Entity (Users/Computers/Groups/OrgUnit) details pages, assignments that are synchronized from a source instance can be unassigned from the target instance. However, removing these assignments results in a difference in the assignments between the source and target instances. Assignment resolution on the target instance can result in an unexpected set of attached applications or packages. [2945877]

    Workaround: To restore the assignments on the target instance, use Synchronize button for that specific target instance. To synchronize all the targets registered for a source instance, you can use Synchronize Targets button. For more information about the Synchronize and Synchronize Targets functionalities in the App Volumes Manager admin UI, see VMware App Volumes Administration Guide at VMware Docs.

  • Even after unassigning an application that is synchronized, deleted assignments might remain in the Synchronization View (Assignments table) on the Application details page and the Assignments page in the App Volumes Admin UI. However, these assignments which are in the "Disabled" status do not accurately display the state of assignments on the target instance. This issue occurs only if application synchronization fails while synchronizing the assignments of the application. For more information about the Synchronization view, see VMware App Volumes Administration Guide on VMware Docs. [2942256]

    Workaround: Navigate to the Application details page in the App Volumes Admin UI, display the Synchronization view, and click Unassign. This operation deletes the assignments again.

  • When a database failover occurs, App Volumes Manager displays a maintenance page with the appropriate database error message. The App Volumes service fails to recover and continues displaying the maintenance page even after the database is back online from the failover. [2691524]

    Workaround: When the database is back online after the failover, restart the App Volumes Manager service. Restarting the service removes the maintenance page.

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

  • App Volumes is unable to capture the GroupWise Messenger application. The capture fails due to an internal error in App Volumes. This failure is presented as a message displayed immediately by the GroupWise installer: "Class not registered". [2924188]

  • An MSIX application delivered as an on-demand package to an end user fails to launch in the first attempt. [2947214]

    Workaround: For the application to launch successfully, user must click open the shortcut again.

  • Explorer.exe opens instead of the actual MSIX application for an MSIX package when the app run command is used in the target path of the application’s simulated shortcut. [2947387]

    Workaround: For the application to launch successfully, the end user must click open the simulated shortcut again.

  • On Windows 10 1607 and Windows Server 2016, folders on App Volumes are occasionally changed to zero-length files.  Sometimes this makes the applications in these folders unavailable.  Other times, the applications in these folders are still accessible. [2937254]

  • 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.

  • 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.

  • 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.

  • 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.

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