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

What's New

• Azure Virtual Desktop Integration and Entra ID

  App Volumes now integrates seamlessly with Azure Virtual Desktop, allowing customers to manage application lifecycle and virtualization within Azure Virtual Desktop environments. Additionally, Entra ID (former Azure Active Directory) is added as an alternative authentication method for deployments.

  Azure Virtual Desktop Integration can be enabled in the Azure Marketplace. For information about this feature, see Deploy App Volumes Manager through Azure Marketplace.

• App-V Conversion

  The App Volumes Application Capture Command-Line Program is now enhanced for seamless conversion of App-V packages to App Volumes packages, providing a lifeline for enterprises facing the end of life for App-V. This feature ensures a smooth transition to modern application delivery, preserving existing investments and offering continuity with a trusted, scalable solution.

• Implement Uniqueness Check for the Delayed Jobs Queue

  To enhance system efficiency, a job uniqueness check is implemented, preventing duplicate tasks from being queued. This ensures only one job per handler is processed, reducing the queue size and improving performance, especially in multi-manager environments.

• Support for Microsoft Windows Server 2025 and Microsoft Windows 11 24H2

Resolved Issues

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

• Microsoft Office 365, 2019, and 2021 App Volumes packages sometimes report an svoffice logon error in a popup window during volume attachment. The issue can occur with App Volumes agent versions 2406 and earlier. The issue first appeared after Microsoft released its March 2024 OS maintenance. [AVA-24476]

  In the %SVAgent%\Logs\cv_startup_postsvc.log file, the error is logged as follows:

  svoffice Cannot find HKLM\SOFTWARE\Microsoft\AppVISV
  System.SystemException: Application aborting
  

• App Volumes redirection of the search index from a folder on the system volume (C:\ProgramData\Microsoft\Search\Data) to a folder on the Writable Volume (C:\SnapVolumesTemp\writable\persistent\Search\Data) does not occur on Windows 10 with App Volumes 2312 and later and Windows 11 with any version of App Volumes. [AVA-24417]

  Typically in App Volumes configurations with a Writable Volume, if redirection is not already configured by DEM (Dynamic Environment Manager) or GPO (Group Policy Objects), App Volumes automatically redirects the OS search index from a folder on the system volume (C:\ProgramData\Microsoft\Search\Data) to a folder on the Writable Volume (C:\SnapVolumesTemp\writable\persistent\Search\Data).

• An application package created in the year 2022 and earlier using any version of Windows 10 or Windows 11 might fail on recent versions of Windows 10 and 11 if the package includes WebView2. Affected applications are Citrix Workspace and Microsoft Teams. Due to this issue, the application shows an error that WebView2 is not present even though WebView2 is installed on the base OS. [AVA-24251]

• Whenever multiple on-demand App Volumes applications are launched or an on-demand application is launched with a classic application package attached to the agent computer, Dynamic Environment Manager triggered tasks using the App Volumes logon-time apps delivered trigger can be triggered multiple times. As a result, the selected actions run again causing unexpected results. [AVA-23846]

• Application icons located in the Start menu folder, C:\ProgramData\Microsoft\Windows\Start Menu, are not visible if the application is delivered as on-demand. [AVA-23383]

• Applications cannot write large string values (several hundred thousand characters) to the registry. [ESC-33581]

Known Issues

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

• The following error is logged in App Volumes Manager when session hosts in a host pool are shutdown: 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. [AVM-36787]

  Note: This error does not affect the end user.

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

  Workaround: Upgrade to App Volumes 2603.2 and later.

  Resolved: This issue is now resolved in App Volumes 2603.2 and later.

• 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-27476]

• Horizon Agent 8.14 (2412) and 8.15 (2503) processes crash during a Horizon Client reconnect if the Horizon configuration includes an App Volumes package which contains Visual C++ x64 runtime version 14.36.32532.0 or earlier. [AVA-25969]

• With App Volumes deployed on Azure Virtual Desktop and the current logged-in user has no entitlements, the login takes 30 seconds and a message pops up which states the following: Unable to contact App Volumes Manager. Virtualization is disabled.

  When App Volumes is used with Azure Virtual Desktop, App Volumes agent expects a signed payload from Azure Virtual Desktop. When there are no entitlements, the Azure Virtual Desktop agent does not send the signed payload to App Volumes agent and hence the agent is unable to contact App Volumes Manager. [AVA-24862]

  Workaround: Entitle at least one application to the user or group.

• On-demand applications are not delivered to the end user and application launch fails when app links are used after App Volumes agent is upgraded in a persistent virtual desktop which has active assignments. [AVA-24500]

  Workaround: Restart the desktop where App Volumes agent is upgraded. After the restart, on-demand applications are delivered, and an application launches successfully when app links are used.

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

  Workaround: To use the RemoteApp, the end user must be logged out of the session and must log in back again.

• Running the change logon command on an RDS host does not work when application packages or Writable Volumes are attached to the RDS host. Status of the RDS host machine is not updated in the Omnissa Horizon console. [AVA-23264]

  Workaround: Add the following in the custom snapvol.cfg file: exclude_registry_value_path=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\WinStationsDisabled.

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

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

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

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.