Omnissa App Volumes Release Notes

Omnissa App Volumes 2412 | December 19 2024 | Build 4.16.0.66

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

What's New

Omnissa App Volumes

As part of our transition to Omnissa, App Volumes has been refreshed. This update introduces new visual elements and icons, along with significant improvements designed to enhance data visibility and streamline workflows. Additionally, the App Volumes installer has transitioned from 32-bit to 64-bit, aligning with modern system requirements.

MSI for Windows Endpoints

App Volumes now supports MSI-wrapped VHD packages, alongside traditional VHD and VMDK formats. This allows the App Volumes agent to operate independently within existing delivery infrastructures such as Workspace ONE UEM, Microsoft Intune, and Microsoft Configuration Manager. These MSIs streamline both the capture and uninstallation processes, reducing complexity and administrative effort. Additionally, leveraging Apps on Demand with MSIs enhances security by activating applications only upon launch, significantly reducing the attack surface.

App GUID Parameter for Application Capture and Application Import

Automated workflows can now specify an application unique identifier to associate packages by application. Administrators can import these packages into App Volumes Manager, where they will be automatically grouped by application, facilitating more organized and efficient application management.

Tagging for Azure Virtual Desktop Integration

Enhancements have been made to the Azure Virtual Desktop integration, allowing administrators to specify key-value pair tags that are utilized when creating or modifying app attach package resources.

Support for Microsoft Office 2024

Resolved Issues

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

System resources are exhausted due to a memory leak resulting in a black screen and Horizon Client gets disconnected from Horizon Agent. This issue is seen when both Microsoft Office 365 and Microsoft OneDrive applications are used together in the App Volumes agent machine. [AVA-24188]
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]

Known Issues

The number included after each known issue is used by 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.

Workaround: In the App Volumes Manager admin UI, navigate to Activity → Pending Actions. Identify whether any SyncIntegrationsJob job is in the Failed state. Before proceeding with further validation, configuration, or testing activities, delete all failed jobs.
[AVM-43565] The following error is displayed in the System Messages tab and logs for a few application packages Error while refreshing Applications: Primordial OS is immutable and cannot be changed. when Rescan Applications action is performed. This issue occurs due to a mismatch in some package properties in the files associated with the package.
[AVM-38022] SQL Server 2022 installation might fail intermittently when installing App Volumes Manager on Windows Server 2016

Workaround: Before installing App Volumes Manager, manually install SQL Server 2022.
[AVM-36787] 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.

Note: This error does not affect the end user.
[AVA-28403] Published applications on demand fail to launch when App Volumes 2603.1 or earlier versions are used with Horizon 2606.

Workaround: Upgrade to App Volumes 2603.2 and later.

Resolved: This issue is now resolved in App Volumes 2603.2 and later.
[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-27166] When icon index is more than the number of RT_GROUP_ICON resources, App Volumes agent fails to extract the application shortcut icon. As a result, the application when delivered on demand has blank shortcuts.

Note: When the application is launched for the first time, the application shortcut icon is correctly displayed.

Resolved: This issue is now fixed in App Volumes 2512.
[AVA-27205] Multiple shortcuts of an application having the same name are not displayed in the Start menu when the application is delivered as on-demand.

Resolved: This issue is now fixed in App Volumes 2512.
[AVA-26750] The following error You cannot call a method on a null-valued expression is observed multiple times in the command prompt when the support.bat loglevels command is used. This issue occurs when only the App Volumes agent is installed in a virtual machine and not the Horizon agent.

Resolved: This issue is now fixed in App Volumes 2512.
[AVA-26684] Writable Volumes fail to attach for some users, and the following message is displayed: Volumes were not mounted due to an issue with your Writable Volume. Please try logging in again, or contact your administrator.
This issue causes user login failures.
[AVA-26575] An unwanted message for deleting user created virtual disks is displayed when upgrading the App Volumes Application Capture Command-Line Program. This message prompts the administrator to select Yes or No. Either action can be selected as the upgrade is not affected.

The message reads as follows: The current installation of App Volumes Tools has – user -created vhd virtual-disk files in C:\ProgramData\Omnissa\AppVolumes\Packages. Click Yes to delete these files. Click No to retain them.
[AVA-26485] Application icon is not captured for an application when using the App Volumes Application Capture Command-Line Program. As a result, the icon for the application is not displayed when this package is imported to App Volumes Manager.
[AVA-26484] An MSI application package update might fail, or the application package might be handled incorrectly if more than one MSI package has the same version number.
This issue occurs when a product version is not specified during an application capture using the App Volumes Application Capture Command-Line Program. As a result, a default version of 1.0.0.0 is assigned to the captured package. If multiple versions of the same application are captured without the product version, then the resulting packages have the same default version. To resolve this issue, the /productversion parameter can be used.

For more information about this parameter, see the Windows Command-Line Arguments for the App Volumes Application Capture Command-Line Program section in the App Volumes Administration Guide.
[AVA-26477] svservice stops running for some applications when the delivered package is on-demand. As a result, the user is unable to either see the application shortcut or the user does not receive the delivered application after launching the shortcut.

Workaround: Set the package delivery mode to classic.
[AVA-26399] The WSearch service is deactivated when a user logs in to the agent computer with a Writable Volume created using a version of App Volumes Manager earlier than App Volumes agent. This issue is seen in App Volumes agent 2412.
[AVA-25639] A file access or access denied error occurs when running a database-related application.

Resolved: This issue is now fixed in App Volumes 2512.
[AVA-25969] 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-25823] Issues related to FSLogix are as follows:
- Logoff hangs when the FSLogix Cloud Cache feature is enabled.
- FSlogix app rules do not work for files and registry keys on system volumes.
Workaround:
Create a file %SVAgent%\Config\Custom\Snapvol.cfg and add the following:
```
#FSLogix exclusions
exclude_process_path=\Program Files\FSLogix
exclude_path=\Program Files\FSLogix
```
[AVA-25369] Application packages fail to attach to the Windows endpoint when the application is installed either from the file share or locally (Windows endpoint). This failure occurs because during App Volumes agent installation (directly on Windows endpoint), the install path is not set in the PATH environment variable.

Workaround: Manually add the App Volumes agent install path C:\Program Files\Omnissa\AppVolumes\Agent to the PATH environment variable.
[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 in back again.
[AVA-23264] 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.

Workaround: Add the following in the custom snapvol.cfg file: exclude_registry_value_path=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\WinStationsDisabled.
[AVA-20343] 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-20264] 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.

Was this page helpful?