Release Notes for VMware App Volumes 4, Version 2206 (2023)

what's new

• On-Demand Applications: File Type Associations

  Apps can now be deployed on-demand by clicking on a document, using a context menu, or launching from registered app paths. Users can even change their default memberships. This is because packages updated or created on App Volumes 4, version 2206 contain additional metadata, including icons and registration information, designed to provide a faithful experience to your end users even before the apps are deployed.

  For more information on file type associations, seeUnderstand package deployment modes on application volumesin the VMware App Volumes 4 Version 2206 Administrator's Guide atDocuments from VMware.

• Added support for vSAN Stretch Cluster

• Added support for Microsoft Azure SQL Database (PaaS).

• Packaging symmetry guarantee

  This new option in the instance relationship settings allows you to enable or disable them based on your overall deployment needs. Your source instance verifies that your packages are actually available to target instances with the option enabled.

• The App Volumes Manager API includes a new onerequested_mbValue for developers who need to automate extending writable volumes and see if the volume is pending user login to extend the partition on the guest.

  For more information about this update, seeUsing VMware App Volumes API version 2206NOVMware {Code}.

• Added support for migrating writable volumes to App Volumes 4 version 2206 using the App Volumes Migration Utility Fling 2.0.

  To download Fling, go toApplication volume migration utilitybook page.

• VMware Cloud - The vCenter option in VMware Cloud on AWS has been removed from the App Volumes Manager vCenter settings. The option included legacy compatibility checks not required for current versions of VMware Cloud on AWS.

  (Video) VMware Dynamic Environment Manager 9.3: MS Outlook OST on VMware App Volumes - Feature Walk-through

internationalization

App Volumes content is available in English only.

problem solved

• Even after you unassign a synced app, the removed assignments may remain in the sync view (assignment table) on theApplication detailsside and theassignmentsin the App Volumes admin UI. However, these tasks are in theDisabled personstatus does not accurately reflect the status of allocations on the target instance. This issue only occurs when app sync fails to sync app assignments. For more information on the synchronization view, seeVMware App Volumes Administrator's GuideoneDocuments from VMware. [2942256]

• Package name displayed inactivity logThe App Volumes Manager admin UI tab changes to the package GUID after removing the package. It is difficult to identify which package was excluded by the GUID. [2938008]

• NOlegal entity(Users/Teams/Groups/OU) synced assignments from a source instance can be unassigned from the target instance. However, removing these mappings results in a difference in the mappings between the source and target instances. Map resolution on the target instance may result in an unexpected set of attached applications or packages. [2945877]

• NOsynchronization view, applying a filter does not show thisDisabled personAssignments and filtering with theConditionfield returns no results (CapableÖDisabled personassignments). So, the tasks inDisabled personthe states are not displayed in the synchronization view. Therefore, it is difficult to manage the task sync progress when there are a large numberDisabled personTasks [2946144]

• Application installers that create data in a secondary path fromHKLM\Sistema\CurrentControlSet\Control\NetworkProviderThe registry key may affect the behavior of the application and the application may not work as expected. Symptoms vary and depend on the application. A common symptom is that when the application is captured, the registry data in the subpath is modifiedHKLM\Sistema\CurrentControlSet\Control\NetworkProviderit is created on the base volume instead of the application package. As a result, the application does not behave as expected. Example: In one of the scenarios, the single sign-on feature for an application was not working. [2871141]

• App Volumes cannot track the GroupWise Messenger application. The ingestion fails due to an internal error in App Volumes. This error is presented as a message that is immediately displayed by the GroupWise installer:unregistered class. [2924188]

• An MSIX application that is delivered to an end user as an on-demand package does not start on the first try.[2947214]

• Explorer.exe is opened for an MSIX package instead of the actual MSIX application if theapplication executionThe command is used in the target path of the application's simulated shortcut. [2947387]

• After upgrading to VMware App Volumes 4 version 2203 or VMware App Volumes 4 version 2111, SVservice fails to run scripts placed in%SVAgent%\Config\Default\Systemmi%SVAgent%\Config\Custom\System. [2969412]

known problems

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

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

• Apps packaged with Windows 11 show up as packaged with Windows 10 in the App Volumes Manager. [2841689]

• App Volumes Manager installation fails with the following error:App Volumes Manager cannot be installed in local language (Control Panel setting) other than Englishif the language setting on the virtual machine is Arabic. [2884143]

  Workaround:Change the language to English and install App Volumes Manager.

  (Video) Learning VMware App Volumes : Creating an AppStack for Notepad++ | packtpub.com

• Certain applications with a large number of icons related to file type associations can increase login time due to the time required to transfer the icon content to the virtual machine. [2989141]

  Workaround:Disable the File Type Associations (CaptureFTA) feature on the computer used to package these applications. For more information on the CaptureFTA parameter, see theParameters to configure svservicesection oneAdministration Guide for VMware App Volumes 4, Version 2206.

• Packaging AutoCAD Electrical 2022 application leads toCancelledStatus in App Volumes Manager. You can also see the same status in the App Volumes AgentSuccessful packaging!News. The svcapture logs show the following error:ERROR: Error allocating module to symbol retrieval: <file path> Error: 0xc1. [2985555]

  Workaround:Contact VMware Global Support for more information.

• For users with writable volumes, the Seadrive desktop client cannot open files on Seadrive online storage with the following error:An unexpected error prevented the file from being copied. If you keep getting this error, you can use the error code to find help with this issue. Error 0x80070185: Cloud operation was unsuccessful. [3001176]

• In addition to the Chrome icon working correctly, the end user will see a blank shortcut icon when the Google Chrome app package is deployed on demand and the user gets a write volume. The shortcut icon is not working and when you click the icon, the following message is displayed:The chrome.exe item referenced by this shortcut has been modified or moved so this shortcut no longer works properly. Do you want to remove this link?However, users can still use the icon if they are working properly. [2993027]

• run as userthe utility fails withNo active user sessionError message when run from a custom script running in the system context (e.g.: OnPreDisableApp). This issue is present in App Volumes 4 system scripts version 2111 and later. [2998865]

  Workaround:backwards fromrun as useruse the appropriate "...AsUser.bat" script in the context of the user (e.g.: OnPreDisableAppAsUser.bat).

• A black screen error occurs when the Box Drive app is assigned to a computer and packaged and delivered to a user in a built-in admin role or a built-in domain admin role. If the app is deployed to a user with a different role, the app fails to launch from the shortcut and displays the following error:This action is not allowed for the Checkout application. Please contact your administrator.[2953421]

  Workaround:Map Box Drive to a user entity instead of the computer. In scenarios where an application is assigned to a computer and the black screen error does not occur, a successful application launch requires the user to navigate the first time accessing the application at each loginC:\Programme\Box\Box\Box.exeand open the app. Then the app shortcut can be used to launch the app successfully.

• An operating system connection point of a native folder that belongs to a blacklist for a non-virtualized folder (e.g%APP DATA%in configurations not using UIA+Profile Write Volume or Profile Only Write Volume) does not work properly. Files written to the merge source do not appear in the merge target. [2991078]

• When Microsoft Office applications are deployed on demand, the application icons are displayed on theneuThe Windows Explorer context menu has different versions before and after the package is delivered to the end user. However, this issue does not affect packet delivery. [2993048]

• In Windows 10 1607 and Windows Server 2016, the folders in App Volumes are occasionally changed to zero-length files. As a result, the apps in these folders are sometimes unavailable. In other cases, the apps in those folders are still accessible. [2937254]

• If a remote printer is defined on a UIA+ profile write volume and the printer is connected to your print server via a USB interface, the printer definition on the write volume can be removed at the next non-persistent login. [2845852]

  Workaround:

  (Video) VMware App Volumes 2.14: User Writable Volumes Management - Feature Walk-through

  On the system volume, add the following two scripts to the%SVAgent%\Config\Custom\uia_plus_profile:

  OnPreLoadApp.bat: sc config spooler start= desativado 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 exists on both a writable volume and the system volume%SVAgent%\Config\Custom\uia_plus_profile, the App Volumes agent runs the script on the write 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 write volume:

  se existe "%SVAgent%\Config\Custom\uia_plus_profile\%~nx0"("%SVAgent%\Config\Custom\uia_plus_profile\%~nx0")

• If many users log on to their desktops at the same time, some users might not have write volumes created and might not be able to log on to a desktop. This issue does not occur when users already have an existing writable volume [2115623]

  Workaround:Users must log in again or have an administrator create the write volume for the user in advance.

• A writable volume move or copy operation might fail when bulk operations are performed on many volumes. [2115593]

  Workaround:Repeat the move or copy operation.

• App-V packages are not loaded when using the App Volumes agent with a UIA+ profile or a profile-only writable volume. [2434176]

• Apps packaged with App Volumes versions earlier than 2.18.2 sometimes have too many redundant firewall rules. These rules can affect end user logon time on agent machines where the application package is deployed. This issue has been fixed in App Volumes 2.18.2 and later. [2624048]

  Workaround:If you are migrating an app package that was created in a version of App Volumes earlier than 2.18.2 and you are encountering this issue, repackage the app 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 only occurs when the cloud cache feature is enabled. [2791414]

  Workaround:Disable the FSLogix Office Container Cloud Cache feature.