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

Release date: May 6th 2025

Welcome to my Omnissa App Volumes series. The new version of App Volumes, 2503, was GA on April 15th 2025, with the build being 4.17.0.75. 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

  • App Volumes Term Licensing
    • App Volumes now supports term-based licenses, enabling compatibility with Term SKUs. This enhancement allows the same license key to be used for both App Volumes Manager and App Volumes agent-only deployments, streamlining license management and ensuring greater flexibility in different environments.
  • Storage Group VHD Replication
    • Storage Group functionality has been extended to support SMB-based replication, providing administrators with the ability to replicate VHD storage across multiple file shares. Just like VMDK storage replication, specific VHD storage locations can now be designated not to be replicated, ensuring storage efficiency in distributed environments.
  • Recovery Administrator Account
    • A new Recovery Administrator account introduces an independent, local access method for App Volumes Manager when domain credentials are unavailable. This account is strictly limited to managing domain configuration and administrator roles, allowing administrators to restore access in situations where primary login methods are disrupted.
  • Removal of Volumes (2.x) and AppStacks
    • The ability to enable Volumes (2.x) is removed from the advanced settings to simplify the interface for customers. The support for App Volumes 2.x ended on March 9, 2023.

In this section I will describe how I upgraded my App Volumes infrastructure to v. 2503, 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.