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

What's New

• Persistent Desktop Support

  • Expanded Use Cases: New support for classic Windows desktop environments, a significant enhancement to our Apps Everywhere strategy. This new feature extends our efficient one-to-many provisioning model, previously available only for non-persistent desktops, to persistent virtual desktop environments.

  • User-Installed Applications: Users can now install their own applications alongside those delivered by App Volumes.

  • Enhanced Management: This feature supports desktops managed with tools like Omnissa Workspace ONE UEM and Microsoft Intune and Configuration Manager, enabling traditional system updates instead of relying solely on image updates in non-persistent environments.

  • Installer Update: Administrators installing App Volumes agent will now see an option in the installer for selecting the Machine Type, making the setup process more tailored and efficient.

• Windows 365 and Amazon Workspaces Compatibility

  This release includes compatibility with Windows 365 and Amazon Workspaces Core.
  It also aligns with the Horizon 2406 release, ensuring seamless management for Horizon and Workspaces Core environments.

• Replicate Application Packages in Specific Stages

  We are excited to introduce the Replicate Application Packages in Specific Stages feature, designed to enhance the life cycle management of applications across multiple instances of App Volumes Manager. The main benefits are as follows:

  • Stage-Specific Replication: Administrators can now configure replication to occur based on the stage of the application package. This allows for precise control over which packages are replicated and when, ensuring that only necessary packages are distributed across environments.

  • Improved Environment Segmentation: Packages that are in the New and Tested stages can be confined to the packaging environment. Only when packages reach the Published stage, the packages will be replicated to the production environment, maintaining a clean and efficient workflow.

  • Optimized Storage Group Management: This feature leverages storage groups to streamline the management of application life cycles, reducing the overhead and complexity of handling application packages in different stages across multiple instances of App Volumes Manager.

  These enhancements aim to provide better control, efficiency, and reliability in managing application packages, ensuring that your production environment remains stable and up-to-date with tested and approved applications.

• Select a specific Package Version when Launching an App (Technology Preview)

  Leveraging Apps on Demand, end users can now select from multiple packages of an application at launch, giving them the ability to try out a new version or launch something specific. Administrators can now assign multiple packages for an application, offering three options for assignment: "Marker," "Package," and "Multiple."

• Writable Volumes Performance Improvements

  Optimized disk I/O, enhancing overall performance and reliability of Writable Volumes.

Resolved Issues

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

• Application packages fail to attach to the agent computer when the Fast Attach option is enabled in App Volumes Manager and the hardware version of the agent computer (VM version) is earlier than 21.
  
  For information about the Fast Attach option, see the Configure and Register the Machine Manager section in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation. [AVM-34933]

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

• Whenever an App Volumes classic application package is delivered, 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 might run again causing unexpected results. [AVA-23248]

• When an App Volumes application is uninstalled during delivery, the application icon continues to be visible in the start menu until a system reboot or any change in the start menu directory location. [AVA-23474]

• When Adobe Acrobat XI is launched for the first time, the application goes into configuration mode and the following message is displayed: Please wait while Windows configures Adobe Reader XI. This issue might occur when the application is either captured using an App Volumes agent version earlier than 2406 or delivered to an agent computer which has an App Volumes agent version earlier than 2406. [AVA-23752]

• End users with a Writable Volume, experience an increase in the login time or black screen for a few seconds after login if there is a difference in the registered MOF (Managed Object Format) entries between the base virtual machine and the Writable Volume. [AVA-23809]

• In an RDSH machine, when the same user logs in multiple sessions and launches on-demand published applications through Horizon Client and Workspace ONE, svservice might crash and the following error gets displayed: The application could not be launched, possible because it is missing for misconfigured. Contact your administrator for more information. [AVA-23935]

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

• If some hardlinks are generated during package creation and the source file is opened with the FILE_FLAG_DELETE_ON_CLOSE flag, then closing one of the source or target files might result in some missing files and the application might not work correctly when the package is assigned to an entity.
  NOTE: Currently, this issues is observed only in the Anaconda application. [AVA-24031]

• new Microsoft Teams, which is installed in the base with the Auto-start Teams option enabled and successfully launched by a user having a UIA+Profile or Profile-only Writable Volume in the first login, sometimes fails to automatically start from the second login onwards for that user with the same Writable Volumes.
  
  This failure occurs when a significant number of UWP apps (Universal Windows Platform apps) are present on the machine and the trigger for Windows Explorer’s startup tasks elapses by the time the new Microsoft Teams application is registered for that user. [AVA-24055]

• When assigning an application, sometimes locating a specific Active Directory search entry of the entity might get affected. This issue occurs due to the limitation in the maximum number of search entries that can be displayed for an entity. If the number of entries matching the search criteria is more than the maximum number, then the rest of the entries remain hidden and unavailable for selection in the admin UI thus affecting application assignment.
  
  For example: If there are 1400 entries matching the search criteria for a user entity, then only 1000 entries are displayed whereas the remaining 400 are hidden and unavailable for selection in the UI. [AVM-33410]

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

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

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

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