bjosoren's IT-Tech blog

IT-Tech blog about different tried and tested solutions based on vmware, microsoft, linux and more tips and tricks

App Volumes – Upgrade to v. 2412

Release date: January 30th 2025

Welcome to my Omnissa App Volumes series. The new version of App Volumes, 2412, was GA on December 19th 2024, with the build being 4.16.0.66. The Release Notes contains the following info about what is new, and can be reviewed here: App Volumes 4 Release Notes These are some of the New features etc:

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.

In this section I will describe how I upgraded my App Volumes infrastructure to v. 2412, but first, at what point in an upgrade procedure should we upgrade the Omnissa App Volumes Components? According to Omnissa’s official documentation, this should be done as shown below.

Horizon 8 Upgrade Overview

Before beginning the upgrade, I also verify that the upgrade path is supported in the Product Interoperability Matrix

The procedure used for upgrading is as follows:

Omnissa Documentation:

App Volumes – Upgrades

App Volumes planning, deployment etc.

Disclaimer: Every tips/tricks/posting I have published here, is tried and tested in different it-solutions. It is not guaranteed to work everywhere, but is meant as a tip for other users out there. Remember, Google is your friend and don’t be afraid to steal with pride! Feel free to comment below as needed.