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 2312.2 Release Notes lists Resolved Issues and Known Issues for this release.

Resolved Issues

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

• MSIX application packages fail to attach to a different OS even when the Allow package delivery to any operating system , an advanced setting, is enabled and the following error can be seen in System Messages in the App Volumes Manager admin UI:
  MSIX Package name_of_the_package locked to name_of_package_OS was not attached to name_of_the_computer because it is not allowed on User’s Machine’s OS
  [AVM-33322]

• Administrator (Read Only) account can neither expand the + button of each application and package on their respective summary pages nor able to view their respective details in the App Volumes Manager admin UI though they are able to view the list of applications and packages on the summary pages. [AVM-33408]

• When replicating packages or AppStacks from a vSAN datastore, the replication fails to copy these files to the destination storage. In the App Volumes Manager log file, the packages and AppStacks meant for replication are skipped. [AVM-33446]

• App Volumes Manager FQDN is shown as Unknown in the CONFIGURATION > Managers > App Volumes Manager Servers page in the App Volumes Manager admin UI. [AVM-33399]

• Due to an internal issue in the LDAP Base field, accessing the AppStacks > Volumes (2.x) tab displays the App Volumes server error, and the tab is not accessible. This issue occurs when the LDAP Base field contains a value. [AVM-33108]

  In the App Volumes Manager logs, the following error can be observed:

  [2024-02-02 19:50:43 UTC] P4672R1802 ERROR Manager: Inspecting Array (195620) (from log block)
  [ 0] "D:/CloudVolumes/Manager/vendor/bundle/ruby/3.2.0/gems/actionview-6.0.6.1/lib/action_view/helpers/translation_helper.rb:60:in `translate'",
  [ 1] "D:/CloudVolumes/Manager/app/views/appstacks/index.html.erb:217:in
  

  The LDAP Base field is present in the Register Active Directory Domain page in the App Volumes Manager admin UI.

  For a description about the LDAP Base field, see Register an Active Directory Domain topic in the Omnissa App Volumes Administration Guide.

• Unable to replicate packages if the folder structure provided in the Default Storage Path field in the CONFIGURATION > Storage tab of the App Volumes Admin UI (for example: /appvolumes/packages) is not present on the datastore during the replication of packages. [AVM-33431]

  The following error is reported in the log:
  ERROR RvSphere: Fault in folder_exists? #<Thread:0x000000010559b130 run> (exception NoMethodError): undefined method `include?' for nil:NilClass

• When accessing DocuSignPrintDriver, delivered as an application package, the printer becomes unavailable due to issues in registry virtualization. If trying to view the printer properties then the following DocuSignPrintDriver Printer Properties error message is displayed: The DocuSignPrintDriver printer driver is not installed on this computer. Some printer properties.... [AVA-23718]

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

• Microsoft Teams icon is not visible in the Start menu when delivered as an on-demand MSIX application package. [AVA-23761]

Known Issues

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

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

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

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

• 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 advertised shortcut launches the MSI installer when the shortcut is clicked. App Volumes agent does not allow the MSI installer to run when a corresponding application package having such an advertised shortcut is virtualized.
  The following error message is displayed: This action is not allowed for application <application_name>. [AVA-21004]

  Workaround: When packaging the application, delete the advertised shortcut from the Start menu, and recreate another shortcut for the application's executable.

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

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

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.