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

What's New

• App Links for Apps on Demand

  Send an App Link in an email, post on a webpage, or add to your app portal. These application URIs can now be used to deliver and launch applications wherever App Volumes agent is installed. Administrators can collect these links from the App Volumes Manager admin UI and distribute them as needed.

• VMDK Package Attachment Resiliency

  In combination with vSphere 8.0 Update 1, App Volumes has added a feature to allow partial disk attachment in the vCenter. If a particular VMDK application package is unable to be attached, any application package disks that are able to be added will still be added. The default behavior in vSphere is to cancel the VM reconfigure which typically results in none of the applications being delivered to end users. This new vSphere feature is particularly important for classic application delivery when multiple disks are added to the machine during startup or login.

  To activate this new feature on upgraded App Volumes Manager instances, the feature toggle must be turned on. For more information, see the VMDK Package Attachment Resiliency advanced setting in the App Volumes Manager Configuration Settings Page section in the Omnissa App Volumes Administration Guide.

• Omnissa App Volumes Deployment Guide for Azure Virtual Desktop Remote Apps

  Remote app streaming for Azure Virtual Desktop enables users to access applications on an as-needed basis, without requiring the applications to be installed locally on their devices or on the image of a multi-session server.

  With Apps on Demand, the applications are delivered to the server for the user when launching the application in real time. The user gets an application when they need the application without the app rationalization and pre-planning required of admins for typical host pools. Remote applications coupled with App Volumes and its Apps on Demand feature also simplifies application management of app updates. Rolling out a new version of an application to thousands of users is as simple as installing once and moving a marker to indicate the current version.

• Technical Preview of App Volumes Deployment Guide for Amazon AppStream 2.0

  We are excited to announce the Technical Preview for the integration of Omnissa App Volumes with Amazon AppStream 2.0, enabling the delivery of App Volumes applications to AppStream users. This integration empowers App Volumes administrators to package and manage applications independently from the underlying operating system, resulting in more efficient management of virtualized applications. These packaged applications can be seamlessly streamed to AppStream Windows desktop fleets, allowing end users to quickly access the applications they need without the delay of installation processes or fleet reprovisioning.

  With this release of App Volumes, which is now generally available, you have the opportunity to explore a technical preview of App Volumes with Amazon AppStream 2.0 applications.

  For more information, see the Omnissa App Volumes Deployment Guide for Amazon AppStream 2.0 guide at Omnissa Product Documentation.

Resolved Issues

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

• With two Active Directory domains in a parent-child relationship where users from both parent and child domains are members of a group of the parent AD domain, if an application is assigned to such a group, then the application is delivered only to the group members of the parent domain but not to the group members of the child domain. [AVM-28519]

• Application driver when installed in a Writable Volume does is not invoked when an end user logs into the agent computer. As as result, the installed application in the Writable Volume might not run properly. [3160286]

• Application managed by an App Volumes source instance is incorrectly shown in the drop-down box when selecting a destination application during a package Move operation in an App Volumes target instance. As a result, synchronization and other operations such as delete, assign, or unassign fails for the moved package. [3119867]

  For more information about App Volumes Instances for application synchronization, see Configure Multiple App Volumes Instances for Application Synchronization section in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation.

• During application delivery, timeout occurs due to the processing of a huge number of services and firewall rules. The timeout happens when the SVAgent environment variable (which points to the folder where App Volumes agent binaries are located) has the drive letter in lowercase. This issue occurs due to an insufficient check for the SVAgent environment variable path. [AVA-20314]

  Important: To resolve this issue, in addition to upgrading to this version of App Volumes, recreate the Writable Volumes for the affected users.

• Input/Output performance in the datastore might get affected when unnecessary user data is recorded in a database in the Writable Volume. [AVA-18833]

• App Volumes applications are missing for end users after they log in to their machines. [AVA-21213]

  The following log message is recorded in svservice.log :

  [svservice:<process_id>:<thread_id>] HttpSendRequest: Session([<session_id>][<domain_name>\<user_name>]) Manager status 200
  

  instead of

  [svservice:<process_id>:<thread_id>] LogManagerResponse: Manager status 200 response (<byte count> bytes): *<volume count>*#<package count>#LOGIN <domain_name>\<user_name>
  

• User-installed software fails on an agent computer which has SentinelOne Antivirus installed. [AVA-20850]

• When a handle is created/opened before virualization started in an agent computer which has a Profile-only Writable Volume and application packages as attachments, memory leak and increased handle count is observed. This can impact the performance of the Profile-only Writable Volume. [AVA-20550]

• App Volumes agent is unable to connect to App Volumes Manager when an update to the App Volumes Manager IP address is not successful during an App Volumes agent upgrade. As a result, application packages are not delivered to the agent computer. [AVA-20102]

  Note: App Volumes agent upgrade is successful.

• During application delivery, timeout occurs due to the processing of huge number of services and firewall rules when there is an insufficient check for the SVAgent environment variable path. [AVA-20314]

  All the services and firewall rules are recorded in the Writable Volume. As a result, ensure that the Writable Volume is recreated.

• An on-demand MSIX application fails to open when using the application shortcut for the first time, though the package is delivered to the end user. The application opens when the shortcut is used again in the same session. [AVA-20098]

• The cobra ADRESS PLUS 2022 application fails to launch with an MSI error after application capture and installation. This issue is seen only in packaging machines running Windows 11 or Windows Server 2022. This issue is not observed in Windows 10. [AVA-20870]

• Software Protection service fails to work when FSLogix 2.9.8440.42104 is installed on an agent computer running App Volumes 2212 and later and affects some of the attached application packages. As a result, these applications do not work correctly. [AVA-20595]

• With Profile-only Writable Volume and an application package attached, search does not get redirected to the Writable Volume and the WSearch redirection service fails to start with the following error: The device is not ready. This issue occurs in App Volumes 2203 and later. [AVA-20711]

• Published applications on demand are not delivered at application launch when a user is assigned both on demand and classic delivery mode applications when logged into an RDSH server. [AVA-20356]

Known Issues

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

• When SSL verification for an App Volumes target instance happens through a cacert.pem file present in the config directory where App Volumes Manager is installed, the following error is displayed: Error while retrieving the certificate. Unable to find the certificate for the target manager instance. After a while, the error is not visible. [AVM-31353]

  NOTE: This is a UI display issue and causes no functional impact.

• If it is not possible to determine the Active Directory site from an IP address or subnet, a default Active Directory site is not set. This might result in App Volumes Manager contacting Domain Controllers out of its (App Volumes Manager's) Active Directory site. [AVM-28680]

• After upgrading from App Volumes 2203.2, cached static files prevent the loading of UI elements within App Volumes Manager admin UI. [AVM-30954]

  Workaround: Clear the cache of your browser and load balancer.

• Application packages and Writable Volumes cannot be attached to instant-clone desktop pools which have the Add vTPM Device to VMs option selected in the Horizon console. [AVM-31057]

  For more information about the Add vTPM Device to VMs option, see the Windows Desktops and Applications in Horizon 8 documentation.

  For more information about the Virtual Trusted Platform Module (vTPM), see the vSphere Virtual Machine Administration documentation.

  Workaround: Follow the instructions as mentioned in this knowledge base article.

• After enabling the Mount ESXi option in the Machine Managers page and when saving this setting, the following error is visible in the App Volumes Manager admin UI: Failed to connect n of n hosts host1.com host2.com hostn.com [AVM-31066]

• Applications packaged on Windows 11 are shown as packaged with Windows 10 and applications packaged on Windows server 2019 and Windows server 2022 are shown as packaged with Windows server 2016 in App Volumes Manager admin UI. [AVM-29123]

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

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

• "new Microsoft Teams" which is installed in the base image, launched, and updated successfully by the user with a UIA+profile Writable Volume at the first login fails to launch at the second login onwards with the same UIA + Profile writable. This failure occurs because unexpected registry entries are captured in the Writable Volume. [AVA-24024]

  Workaround: Customize the base image by adding the following exclusions in custom\snapvol.cfg:

  exclude_registry=\REGISTRY\MACHINE\Software\Classes\PackagedCom
  exclude_registry=\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\ms-teams.exe
  exclude_registry=\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\ms-teamsupdate.exe
  

  When the user having the same Writable Volume logs into the agent computer which has the updated based image, new MS Teams launches successfully.

• "new Microsoft Teams" application fails to launch when Profile-only or UIA+profile Writable Volume is attached to the agent computer.

  Note: When this issue occurs, no error message is displayed by the application. [AVA-23756]

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

• End users with a Writable Volume experience an increase in the login time if there is a difference in the registered MOF (Managed Object Format) entries between the base virtual machine and the Writable Volume. [AVA-23247]

• When an App Volumes application package or Writable Volume includes a printer specification and the memory integrity feature is enabled, Windows crashes at startup. [AVA-23138]

  Memory integrity is a virtualization-based security (VBS) feature. This feature is sometimes referred to as hypervisor-protected code integrity (HVCI). For more information about this feature, see the relevant Microsoft documentation.

• After the Windows update of "September 12, 2023—KB5030219 (OS Build 22621.2283)" on a VM with either an application package or Writable Volume attached, Windows start menu and search do not respond. [AVA-23022]

  Workaround: Create the file "%SVAgent%\Config\Custom\Snapvol.cfg" on the base image with the following content: exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\PolicyManager\default

• Google Chrome icon is not visible until after the application is virtualized when the application package is delivered as on-demand. [AVA-21423]

• An application which does not have an icon and shortcut after capture cannot be delivered as an on-demand application. Additionally, for such applications, App Links are not available. [AVA-21355]

• If the SFN (Short File Name) of a folder is changed during capture and after assignment the folder is searched using the updated SFN, then the following error is displayed " System cannot find the the file specified ". When the folder is searched using the original folder name, search results display the folder with the updated SFN. [AVA-19401]

• When an EXE is present in both C:\Windows\System32\ and C:\Windows\SysWOW64, and the EXE is referenced in an HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run key, App Volumes must use the SysWOW64 version. Instead, App Volumes currently uses the System32 version, which might behave incorrectly. [AVA-20073]

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

• An App Volumes application assigned to an RDS server is not listed in the Horizon Console. As a result, a Horizon administrator is unable to create an application pool with the application assigned to the RDS server. [AVA-20887]

  Workaround:

  1. On the RDS server where agent is installed, create a registry key OverrideSkipHzWsnmAppScanCalls of type REG_DWORD at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svdriver\Parameters and set the value to 1.

  2. Restart the RDS server.

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

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

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

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