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 2303.1 includes internal bug fixes.

What's New

In this release, we have made a few updates containing general quality and performance improvements with no new features.

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]

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

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

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

  Workaround: Move the package back to the source application. To move the package, perform the following steps:

  1. Navigate to the Packages tab.

  2. Select the package that you want to move back to the source application.

  3. Click Move.

  4. On the Move package page, select the source application in the Application drop-down box.

  5. Click Move.

  For more information, see Move a Package section in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation.

  NOTE :

  If you have deleted the source application, then you must create another application with the same source application name. When creating the application, ensure that you do not select the Create a package checkbox. For the package move, follow the instructions as mentioned earlier.

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

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

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

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

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

• 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

• An application assigned to an RDS server using App Volumes Manager 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, locate the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svdriver\Parameters, create a REG_DWORD value OverrideSkipHzWsnmAppScanCalls, and set the value to 1.

  2. Restart the RDS server.

• If a VMDK of an application package contains a square bracket, '[', the package does not get imported to App Volumes. As a result, the package is not listed in the Inventory tab of the App Volumes Manager admin UI. [3034059]

  Workaround : Rename the VMDK and import the package again.

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

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

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

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

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

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