Omnissa App Volumes Release Notes

Omnissa App Volumes 2606 | July 30 | Build 4.22.0.161 Check for additions and updates to these release notes.

Omnissa App Volumes is a real-time application delivery system that enterprises can use to dynamically deliver and manage applications.

Omnissa App Volumes Release Notes lists New Features, Resolved Issues and Known Issues for this release.

What's New - 2606

Custom Package Lifecycle Stages

Provides the ability to define, build, and reorder stages for aligning lifecycle management processes. For example, Approved could be added after Tested, and before Published.

App Volumes Agent On-Demand Download Progress for Local Copy Mode

Introduces a download progress dialog for packages delivered in local copy mode, giving end users real-time visibility into application delivery.

With prior releases, users had no visibility to download status. The new Windows-native dialog lets users pause, resume, or cancel a package download in progress, reducing confusion and help-desk tickets during app delivery.

User Sentiment for Local Copy Mode

Brings sentiment feedback to local copy mode, matching the capability already available for virtual delivery. After using an application, end users can submit a thumbs up or down along with optional comments.

Admins and application owners can then view sentiments by package and application, giving teams a direct feedback channel.

Smart Card Login for App Volumes Manager

Adds smart card authentication support for App Volumes Manager. This capability helps organizations authenticate users with physical identity assurance media.

It removes the extra step of requesting time-bound temporary passwords for administrators who authenticate without Active Directory credentials.

CVE Reporting for Applications and Packages (Technical Preview)

Maps application packages and versions to publicly known vulnerabilities, surfacing severity and CVSS scores from sources including NVD, CISA, and OSV.

App owners can view and prioritize which applications need attention first and factor vulnerability risk into staging and delivery decisions.

For more information about this feature, see Omnissa Beta Program.

App Volumes and Workspace ONE Intelligence with Experience Management (Coming Soon)

Sends App Volumes health, performance, and operational data to Workspace ONE Intelligence with Experience Management, delivering centralized visibility into application delivery and platform health.

Administrators can proactively identify issues, monitor service reliability, and accelerate troubleshooting with insights into package activity, attachment performance, failures, and overall environment health.

Support for the upcoming Experience Management dashboard will be available soon.

Resolved Issues

The number included after each resolved issue is used by the internal issue tracking system.

• [AVM-47039] A failed SyncIntegrationsJob can block subsequent synchronization requests initiated from an App Voumes integration (in the App Volumes Admin UI, Infrastructure → Integrations), thus preventing new integration synchronization jobs from getting scheduled and running successfully.

• [AVM-46951] App Volumes Manager is unavailable after a failed Rails console session when the Windows Integrated Authentication for SQL Server is the database connection method chosen during App Volumes Manager installation.

• [AVM-46820] A database migration failure might occur when upgrading to App Volumes 2512 and the following error is logged at C:\Program Files (x86)\CloudVolumes\Manager\log\svmanager_setup.log: CREATE UNIQUE INDEX terminated because a duplicate key was found.... This issue causes the upgrade to fail.

• [AVM-46677] App Volumes Manager reports the following database error Volume access mode is not included in the list, in the System Messages tab within the App Volumes Manager admin UI, when a new computer record is created during App Volumes agent startup.
  This error occurs because App Volumes Manager is unable to detect in which package access mode (shared storage or local copy) the App Volumes agent is installed on the computer. As a result, computer-based application assignments are not attached to the computer.

• [AVM-46349] Certificate validation fails after SSL certificate regeneration on the target App Volumes Manager instance. This issue occurs because the source instance retains the previously accepted certificate. This mismatch causes certificate validation to fail, resulting in communication failure between the source and target instances.

  Note: Clicking the Certificate button on the source instance does not retrieve the newly generated certificate — it continues to display the outdated certificate.

• [AVA-28474] The PowerShell Cmdlet fails to launch an App Volumes MSIX package application, when using a Launch ID with the Run-AppVolumesApp command.

• [AVA-28403] Published applications on demand fail to launch when App Volumes 2603.1 or earlier versions are used with Horizon 2606.

• [AVA-28332] App Volumes Application Capture Command-Line Program (appappcapture.exe) fails when using the appcapture.exe convert command to convert an App-V application package to an App Volumes VHD or VMDK application package.

• [AVA-28262] When capturing an application in the MSI format using the App Volumes Application Capture Command-Line Program (appcapture.exe), the MSI file does not get created whereas the VHD and JSON files are created successfully. This issue occurs because an invalid product version is generated for the application.

• [AVA-28258] An Invalid License Key warning dialog is seen, when any App Volumes agent version currently installed in Standalone mode, without an App Essentials license key, is upgraded to App Volumes agent 2603.1 using the App Essentials license key. Regardless of this warning dialog, the upgrade is successful and the App Essentials license key is also successfully updated.

• [AVA-28172] When a Windows endpoint installed with App Volumes Agent in local copy mode synchronizes with App Volumes Manager for the first time, applications get downloaded to the endpoint only after a reboot.

• [AVA-28046] App Volumes Direct installation fails when using the App Essentials license for install and the following error occurs: The License Key entered is invalid. Verify the format and ensure it matches the provided License Key. License Keys are 35 characters long and formatted as XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.

• [AVA-28036] Some issues occur when using App Volumes-packaged MSIX applications due to a race condition between App Volumes and an OS operation. The issues are as follows:

  • In a Horizon RDSH session, the MSIX applications might fail to launch with the following error: Windows cannot access the specified device, path, or file.

  • In a Dependency or Install Order Application Relationships scenario, if an MSIX application is the base or the first application, then as per the expected behavior, the MSIX application must virtualize first followed by the dependent or the second application respectively. Instead, the dependent or the second application might get virtualized even before the MSIX application. Neither relationship type is honored.

    Note: For Dependency, the expected behavior is when the base application fails to virtualize, then virtualization of the dependent application also fails.

• [AVA-27990] Unexpected folders such as Omnissa and VMware Tools might appear in the same location as the captured package.

  Note: You can ignore these folders as they do not affect the captured package.

• [AVA-27476] Applications such as Google Chrome Portable (installed per user) display a blank window or an "Aw, Snap!" error at first launch when using a UIA+profile Writable Volume.

• [AVA-21872] When a Windows endpoint installed with App Volumes Agent in local copy mode synchronizes with App Volumes Manager for the first time, applications get downloaded to the endpoint only after a reboot.

Known Issues

The number included after each known issue is used by the internal issue tracking system:

• [AVM-36787] The following error is logged in App Volumes Manager when session hosts in a host pool are shut down: Session: Request is missing session cookie. In the Azure Virtual Desktop environment, a session cookie is provided only when an end user logs into a computer. If a computer starts and shuts down without any end user logging in, then a session cookie is never set. This results in a 401 (unauthorized) error.
  This error does not affect the end user.

• [AVA-28409] An application configured for delayed download gets automatically downloaded when this application is in a Dependency or Install Order relationship with other applications, which are configured for automatic download.

  For more information about delayed download, see the Assign an App Volumes Application to an Entity section in the App Volumes Administration Guide at Omnissa Product Documentation.

• [AVA-24547] .tmp files are seen in the install directory when an upgrade rolls back in a persistent machine with active entitlements.
  These files do not affect any App Volumes operations. By default, these files are automatically deleted after the machine restarts.

  Workaround: If they are not deleted due to any issue, then you can navigate to the install directory and manually delete the files.

• [AVA-24493] If the CURRENT marker of the application is modified after the user launches the application in a session, RemoteApp launch silently fails in Azure Virtual Desktop.

  Workaround: To use the RemoteApp, the end user must log out of the Remote Desktop client app and log back in again.

• [AVA-26351] 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.

• [AVA-26353] 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.

• [2791414] 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.

  Workaround: Deactivate the Cloud Cache feature of FSLogix Office Container.

• [2624048] 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.

  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.

• [2845852] 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.

  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")
  

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

  Workaround: Retry the move or copy operation.

App Volumes Documentation

• For information about how to install, deploy, and upgrade Omnissa App Volumes see Omnissa App Volumes Installation Guide.

• For information about how to configure and use Omnissa App Volumes see Omnissa App Volumes Administration Guide.

Omnissa App Volumes documentation is available at Omnissa Product Documentation.

Internationalization

App Volumes content is available only in English.

Support Contact Information

To receive support, access Customer Connect.

To file a Support Request in Customer Connect and via Cloud Services Portal, see How to file a Support Request in Customer Connect and via Cloud Services Portal -6000005.