Unified Access Gateway 2609: Why Upgrade from 2603

 

Covers UAG 2606 and 2609 · Based on official Omnissa release notes · November 6, 2026

I recommend updating due to a serious security vulnerability!

Why upgrade

If you are still running UAG 2603 (April 14, 2026), you have two releases to catch up on: 2606 (August 24, 2026) and 2609 (October 29, 2026). Jumping straight to 2609 gets you, in one step, the new AlmaLinux 9.6 operating system, TLS certificate replacement without downtime, the redesigned Admin UI and fixes for two CVEs.

This guide lays out what changes, which bugs are fixed and, most importantly, which behaviours change and must be checked before you upgrade. All information comes from the official Omnissa release notes; the screenshots come from my lab.

At a glance: 2603 → 2606 → 2609

Area

2603 (current)

2606

2609

Release date

Apr 14, 2026

Aug 24, 2026

Oct 29, 2026

Operating system

AlmaLinux 9.2

AlmaLinux 9.6

AlmaLinux 9.6 + OS and Java updates

Admin UI

Classic

Classic

Redesigned (dashboard, search, guided JSON import)

TLS certificates

RSA only, service restart on change

ECC/ECDSA, replacement without dropping sessions

Same as 2606

Authentication

SAML Artifact Binding, OIDC JWKS refresh

Multiple signing certs in IdP metadata, dedicated SAML signing cert

Strict X.509 client certificate validation

KVM / Nutanix AHV

OVA

Native QCOW2 image

Same as 2606, plus OpenShift (LA)

Declared CVEs

–

–

CVE-2026-91403, CVE-2026-114406, CVE-????

Open known issues

4

1

None

.

What’s new on 2606 (August 2026)

2606 is the platform release: it changes the operating system and makes certificate management far less disruptive.

General

•AlmaLinux 9.6: the OS moves from AlmaLinux 9.2 to 9.6. Omnissa states that hypervisor compatibility, hardening, password management, FIPS mode and STIG compliance are unchanged.
•Smarter log rotation: UAG monitors disk usage and triggers early log rotation, preventing storage from filling up environments with many devices.
•Logging and troubleshooting improvements; updated OS packages and Java components.

Horizon and certificates

•TLS certificate replacement without restart: existing sessions stay connected while new sessions use the updated certificate. Caveat: if a network interruption occurs after renewal, automatic reconnect can fail because Horizon Client still expects the old certificate; the user reconnects by selecting the desktop or app again.
•ECC certificates and ECDSA cypher suites, in addition to RSA certificates.
•Multiple signing certificates in IdP metadata: all of them are considered for SAML authentication at Admin UI login (useful during IdP certificate rollover).
•Dedicated SAML signing certificate: the SAML signing certificate can be separated from the TLS one; the previous behaviour remains supported.

TLS Server Certificate Settings: uploading a new certificate while a Horizon session stays connected. This is a video where I try it 

 

.

Deployment on KVM and Nutanix AHV

•Native QCOW2 image: no more manual image conversion for KVM-based hypervisors. Nutanix AHV is qualified on this image.
•Starting with 2606, Nutanix is no longer listed on the vSphere/AWS/Google Cloud OVA: AHV customers must switch to the QCOW2 artefact at their next deployment or upgrade.

Content Gateway

No new features: security and stability updates only.

What’s new in 2609 (October 2026)

2609 is the most visible release for administrators: a new console, stricter client certificate checks and two CVEs closed.

Redesigned Admin UI

•Navigation and search: a new layout with cross-category search to find any setting quickly.
•Refreshed dashboard: edge service health and appliance resource usage at a glance, with shortcuts to common tasks.
•Guided JSON import: validation and preview of the configuration before it is applied, reducing configuration errors.

[Screenshot 3] New UAG 2609 dashboard (edge service health and resources).

[Screenshot 4] Search bar in the new Admin UI while looking up a setting (e.g. “syslog” or “certificate”).

[Screenshot 5] Importing a JSON file, showing the preview/validation screen.

Authentication

•Enable Strict Certificate Validation: a new flag for X.509 authentication that adds checks on Extended Key Usage, Critical extensions and a stricter validity check during CRL/OCSP validation. Useful in smart card / PIV environments.

Horizon

•UAG on Red Hat OpenShift (Limited Availability): as part of Horizon 8 support for OpenShift, UAG can be deployed on OpenShift via PowerShell.
•Custom executables up to 500 MB (previously 200 MB): larger packages, such as clients or compliance agents, can now be distributed.

Other

•Logging and troubleshooting improvements.
•OS and Java security updates (details in the next section).

Security: what moving to 2609 fixes

UAG sits in the DMZ and is exposed to the Internet; that is the main reason not to fall behind. Since 2412, automatic OS patch updates are not available, so the only way to receive OS and Java fixes is to install the new release.

Version

Security change

2609

Addressed the eMudhra (CA) key compromise issue

2609

Resolved CVE-2026-91403 and CVE-2026-114406 through OS and Java updates

2606

Fixed UAG-13396: stack trace disclosure from an API under certain conditions (a known issue in 2603)

2606

OS upgraded from AlmaLinux 9.2 to 9.6 with its packages

2606 and 2609

Updated OS packages and Java components

Bugs fixed between 2603 and 2609

Moving to 2609 resolves 10 documented issues, including all four known issues of 2603. 2609 has no declared known issues.

ID

Fixed in

Issue

Known issue in 2603

UAG-13728

2609

rootSessionIdleTimeoutSeconds did not extend the Idle Shell Timeout

No

PPAT-21429

2609

Syslog over TCP failed when sent directly from the Tunnel service

Yes

PPAT-22611

2609

Syslog access logs had corrupted remote_host_ip / remote_host_port values for TCP tunnel flows (logging only, traffic not affected)

No

PPAT-22748

2609

Tunnel Server deadlock, with possible service disruption, when a DTR policy refresh coincided with active sessions

No

PPAT-22168

2606

Tunnel logs are no longer sent to stdout and stderr

No

PPAT-21439

2606

A DTR rule with a non-matching protocol (e.g. UDP:*) stopped evaluation of the other domains in the same rank

No

AST-25524

2606

“Settings imported partially” error when re-importing a just-exported JSON

Yes

UAG-13396

2606

Stack trace disclosure from an API

Yes

UAG-13133

2606

Incorrect health status after rapid configuration changes

No

UAG-13953

2606

False-positive CONFIG_CHANGE audit log entries when reading the SAML configuration via API

Yes

.

Before upgrading: 2609 behavior changes

2609 introduces stricter checks that, depending on your configuration, can block connections that worked on 2603. Omnissa provides a pre-upgrade checklist in KB 6001863: read it before you proceed.

Change

What to check

Risk if ignored

Host header allow list

The Host header of every request must match the configured allow list

Requests rejected with HTTP 400

CA thumbprint for outbound connections

Backend servers (Connection Server, etc.) must present a complete chain ending at the configured CA

Failed connections to backends

IdP SAML metadata

Metadata must include the leaf certificate the IdP uses to sign assertions

Failed SAML logins

Extended Server Certificate Validation

Better RFC conformance; applies only if enabled (disabled by default)

Certificate validation errors

SNMP v1/v2c

JSON import and PowerShell deployment prompt for the community name; if blank, “public” is used

Unintended community name

.

Minimum checklist:

☐Export the 2603 JSON configuration and keep a copy
☐Read KB 6001863 and mark which items apply to your environment
☐Check the Host header allow list and backend certificate chains
☐Verify the IdP metadata includes the leaf signing certificate
☐If you use SNMP v1/v2c, set the community’s name
☐If you run Nutanix AHV, download the QCOW2 image instead of the OVA

Recommended upgrade procedure

UAG is not upgraded in place: you deploy a new 2609 appliance and apply the old configuration to it. With two or more UAGs behind a load balancer, work one node at a time with no downtime.

1.Check compatibility with your Horizon / Workspace ONE version on the Omnissa Interoperability Matrix.
2.Download the 2609 files from Customer Connect: OVA for vSphere, QCOW2 for KVM/Nutanix AHV, VHDX for Hyper-V, plus the PowerShell scripts if you use them.
3.Export the configuration of 2603 as JSON (and save certificates and keys if they are not already in the JSON).
4.Remove the node from the load balancer (or quiesce it) and wait for sessions to drain.
5.Deploy the new appliance with the same IP/hostname, via the OVF wizard or PowerShell (uagdeploy.ps1 with the updated .ini file).
6.Import the JSON from the new Admin UI, using preview and validation to check what will be applied.
7.Verify the dashboard, edge service status, test logins (Horizon, SAML/RADIUS/certificate) and syslog.
8.Put the node back in the load balancer and repeat on the other nodes.

Summary

Going from 2603 to 2609 brings a newer operating system, two CVEs closed, ten bugs fixed (including every 2603 known issue), certificate replacement without downtime and a much better console. The only real preparation concerns the new checks on Host header, certificate chains and SAML metadata: once those are verified, the upgrade is a routine appliance swap.

Unified Access Gateway 2609: Why Upgrade from 2603

PCoIP Is Gone from Horizon Client 2606/2609: What Really Happens When Your Pool Still Says “PCoIP”

A hands-on look at Omnissa KB 6000812 (PCoIP End of Support Status), with a before/after test on Horizon Connection Server 2603.

Starting with the 2606 client release train, Horizon Client no longer offers PCoIP as a selectable protocol. I tested Horizon Client 2609 against a Connection Server 2603 desktop pool configured with PCoIP as the default protocol: the session silently connected using Blast. If your environment still depends on PCoIP, do not roll out the new client until you have validated Blast or ask to your team to verify

.

Background: the long goodbye to PCoIP

PCoIP has been part of Horizon (and View before it) for more than a decade, and many environments still run on it, often because of zero clients, legacy GPO tuning, or simply because “it has always worked”. The end has been announced for a while:

•2023: VMware EUC (now Omnissa) announced the end of PCoIP support in Horizon.
•End of 2025: the PCoIP code was kept until after the Horizon 8 Extended Service Branch (ESB) release, which continues to receive security and bug fixes for three years.
•Horizon 8 / Client 2606: PCoIP is removed as a selectable display protocol in Horizon Client (desktop and mobile). Blast is now the only supported protocol for client connections.
•Agent side: PCoIP remains available as an option in the Horizon Agent installer, but it is not installed by default, and it remains supported on the agent for zero client connections at this time.

Omnissa tracks the current status in KB 6000812 – PCoIP End of Support Status. I recommend bookmarking it, because it is the reference point for what is still supported and where.

Before the upgrade: PCoIP is still there

With the previous Horizon Client, right-clicking a desktop entitlement (or opening its settings) shows the familiar protocol choice: users can pick either Blast or PCoIP, as long as the pool allows it.

Figure 1 – Horizon Client before the upgrade: PCoIP is still selectable.

After the upgrade to Horizon Client 2609: Blast only

After upgrading the client to 2609, the same menu shows only Blast. The PCoIP option has simply disappeared from the user interface. There is no warning to the user at upgrade time and nothing to configure: the choice is just not there anymore.

Figure 2 – Horizon Client 2609: PCoIP is no longer available.

The test: pool set to PCoIP on Connection Server 2603

The more interesting question is what happens on the server side. Many administrators will assume that if the desktop pool is configured with PCoIP as the default protocol, the connection will either use PCoIP or fail. So I tested it.

Lab setup

•Horizon Connection Server: 2603
•Desktop pool: default display protocol set to PCoIP
•Endpoint: Horizon Client 2609

Figure 3 – Desktop pool configured with PCoIP as the default display protocol.

Result

The connection succeeds, but the session does not use PCoIP. Checking the active session (in the client and in the Horizon Console sessions view), the protocol in use is Blast.

Figure 4 – Despite the pool default, the session from Horizon Client 2609 runs on Blast.

Key takeaway: the pool configuration does not protect you. With Horizon Client 2609, the protocol is decided by the client: your “PCoIP” pool will serve Blast sessions.

.

.

Horizon Client 2603 (before)

Horizon Client 2609 (after)

Protocols in the client menu

Blast and PCoIP

Blast only

Pool default = PCoIP

Session runs on PCoIP

Session runs on Blast

PCoIP GPOs / tuning

Applied

Not relevant: Blast policies apply

Network path used

PCoIP (TCP/UDP 4172)

Blast (TCP/UDP 22443 direct, 8443 via gateway)

Table 1 – Summary of the before/after behavior observed in the lab.

Why this matters

A protocol switch that “just works” sounds harmless, but in production it can catch you off guard:

•Network and firewall rules. If only PCoIP ports (4172 TCP/UDP) are open between clients, Unified Access Gateway and agents, Blast traffic (TCP/UDP 22443, or 8443 through the Blast Secure Gateway/UAG) may be blocked or forced onto TCP-only, with poor performance.
•GPO tuning. Years of PCoIP policy tuning (bandwidth caps, image quality, build-to-lossless, session variables) no longer apply. Blast has its own set of policies that need to be reviewed.
•User experience. Blast is generally a strong protocol, but codec choice (H.264/HEVC/Blast Codec), multi-monitor setups, GPU workloads and peripherals should be validated before users notice the difference for you.
•Zero clients. PCoIP zero clients are not affected by the Horizon Client change, as they do not use Horizon Client. But they are tied to the agent-side support status described in the KB, so plan their replacement as well.

Recommendations

1.Inventory your clients. Find out which Horizon Client versions are in use and which users actually connect over PCoIP today (the Horizon Console sessions view shows the protocol per session).
2.Control client updates. If you still rely on PCoIP, hold the client on a version earlier than 2606 on managed devices and review any auto-update settings until the migration is validated.
3.Open the Blast ports. Verify firewall rules end-to-end: client → UAG/Connection Server → agent.
4.Translate your PCoIP GPOs to Blast. Review Blast policies for bandwidth, frame rate, codecs and quality, and test with real users and workloads.
5.Pilot, then roll out. Upgrade a pilot group to the latest client, compare the experience, then move the rest of the users.
6.Update pool defaults. Once everything is validated, set Blast as the default protocol on your pools, so configuration matches reality.
7.Keep an eye on KB 6000812. It is the official source for the PCoIP support status across client, agent and zero clients.

Conclusion

PCoIP’s end of support is no longer a future roadmap item: with Horizon Client 2609, users simply cannot choose it anymore, and a pool set to PCoIP will quietly serve Blast sessions. The switch itself is not the problem; doing it without preparation is. Treat the client upgrade as a protocol migration, plan it, test it, and you will avoid unpleasant surprises on Monday morning.

References

PCoIP Is Gone from Horizon Client 2606/2609: What Really Happens When Your Pool Still Says “PCoIP”

SaaS License Activation for Omnissa Horizon without EDGE Gateway

In the latest versions of Horizon, it is recommended to use the SaaS subscription, which requires the installation of an EDGE Gateway component generated by the Omnissa Connect portal under Horizon in the customer section.

This involves the need to install a Linux VM on our vSphere environment; not for everyone is this feasible:

–Need not have connections with Cloud services
–Resource savings (CPU, RAM and disk space)
–Test environments and any POCs
–Or, as in my case, I must test the new versions of Horizon

For this last point and since I need to install version 2606 as a test, I decided to explain how to do it… step by step.

Installed my connection server on a Windows Server 2025. The first thing to do is access the administration console and activate the license:

.

.

.

Verify that you have received the activation email or that you have a Horizon SaaS subscription and that you have access to the Connect Omnissa portal

So you must log in to the Omnissa Connect portal (by opening a TAB from the Browser you are using to access the Horizon console) and authenticate on connect.omnissa.com and keep the tab open.

.

.

Enter accounts, passwords and if necessary, do MFA

.

.

A new tab will automatically open with the login already made

.

Now run

The following message will appear

.

.

And on the Horizon console, the license status will be as follows

.

.

Two important points

–Mark your calendar to reactivate your license (in the same way) before 90 days have passed
–You can switch to a license via the EDGE Gateway by simply installing the EDGE Gateway (Follow the specific procedure)

.

.

.

.

SaaS License Activation for Omnissa Horizon without EDGE Gateway

App Volumes: VHD in-Guest vs Standard Mode

Technical comparison and recommended use cases

.

.

INTRODUCTION

Omnissa App Volumes provides two distinct modes for delivering applications to Horizon users: the standard mode (VMDK/VMFS-based) and VHD in-guest mode, introduced to support non-persistent OS scenarios and advanced Instant Clone environments.

The choice between the two modes directly affects performance, scalability, and infrastructure requirements.

MODE COMPARISON

Standard Mode (VMDK)

• VMDK disk attach via vCenter API

• Mandatory needs a vSphere infrastructure as a prerequisite

• Limited support for multi-hypervisor environments

• Dependency on shared vSphere datastores

• Compatible with all Horizon desktop types

VHD in-Guest

• VHD mounted directly inside the guest OS

• Hypervisor-independent

• Compatible with Azure, AVD and physical environments

• VHD exposed via SMB share or UNC path

• Application packages and writable volumes are stored in a high-performance file share

• Compatible with all Horizon desktop types

TAKE NOTE! We can select the mode (VMDK or VHD) when installing the first App Volumes Manager. We can’t switch from VMDK to VHD mode, or from VHD to VMDK mode, after the first configuration.

VHD IN GUEST ARCHITECTURE

In this mode, the App Volumes Agent inside the guest mounts the VHD file from the configured UNC path using native Windows APIs. The AppStack content is then layered onto the filesystem via the App Volumes kernel filter driver, making applications available without extraction.

.

.

Note: In VHD in guest mode, the AppStack .vhd file must be reachable via UNC path from the guest. Network latency to the share directly affects mount times.

WHEN TO CHOOSE VHD IN-GUEST

1

Reducing vCenter dependency

Environments with restrictive policies on vCenter API access or multi-cloud architectures.

.

2

Physical desktops or RDSH

Scenarios where the workload runs on bare metal or RDS servers without vSphere hypervisor.

.

3

Azure Virtual Desktop (AVD) environments

Non-vSphere infrastructure; inability to attach VMDK via vCenter.

.

.

App Volumes: VHD in-Guest vs Standard Mode

Microsoft Azure Edge and Omnissa-Managed Enterprise App Registration

My Initial Experience

During the preparation activities for deploying a new Horizon Cloud on Azure environment, I was reading the official documentation at

https://docs.omnissa.com/bundle/UsingManagingHorizonCloud/page/DeployingaMicrosoftAzureEdge.html

and discovered the presence of a new and recommended deployment method: the “Omnissa-managed” mode.

I immediately wanted to test it, but in my Omnissa Connect console, this option wasn’t yet available.

.

I contacted support and they informed me that the feature would be released soon, but if I wanted to use it immediately, they could enable it through a Feature Flag. Obviously, I couldn’t say no to that opportunity! Once they provided my ORG ID and enabled the flag, the new option appeared while I was creating the EDGE in the Primary Provider section.

This is my journey with the Omnissa-managed method, and I’d like to share what I learned about this game-changing approach.

.

.

Introduction

Horizon Cloud on Microsoft Azure is evolving, and Omnissa has introduced a significant security enhancement that every administrator should know about. The new Omnissa-managed Enterprise App registration method represents a paradigm shift in how organizations handle service principal credentials. If you’re planning a Horizon Cloud deployment on Azure, understanding the difference between this new approach and the traditional manual method could be crucial for your security posture.

The Security Challenge

Historically, deploying Horizon Edge in Horizon Cloud on Azure required organizations to create and manage their own Azure Enterprise Applications. This approach meant handling sensitive service principal secrets—credentials that need to be carefully managed, rotated, and protected. The more systems that have access to these secrets, the higher the security risk.

The traditional single-tenant deployment method (Manual Enterprise App registration) placed the responsibility of secret management squarely on the customer organization. While this approach continues to be supported, it introduces additional operational overhead and potential security vulnerabilities.

Enter Omnissa-Managed

Omnissa has introduced a new Enterprise App registration method that fundamentally changes who manages the service principal secrets.

Key Benefits

1. Enhanced Security

Organizations no longer need to provide their sensitive secrets key information to Omnissa or manage it themselves in the context of Horizon Cloud deployment. The credentials remain under Omnissa’s direct management, reducing the attack surface and potential points of compromise.

2. Simplified Administration

Say goodbye to manual Enterprise Application creation and complex permission configurations. With Omnissa-managed registration, the setup process is streamlined. Omnissa handles the heavy lifting—you focus on deployment.

3. Reduced Operational Overhead

No more worrying about secret rotation schedules, credential lifecycle management, or complex authentication flows. Omnissa manages these operational concerns, freeing your team for other critical tasks.

4. Enterprise-Grade Security

By centralizing secret management with Omnissa, organizations benefit from enterprise-grade security practices, regular audits, and dedicated security expertise that Omnissa brings to the table.

Manual Registration: Still Available

For organizations with specific requirements or legacy configurations, the traditional single-tenancy method remains available. This manual Enterprise App registration approach allows organizations to maintain full control over their authentication setup if needed. However, unless you have specific compliance or architectural reasons, the manual approach introduces unnecessary complexity.

The Recommendation

Omnissa-managed is the recommended method for all new Horizon Cloud deployments on Azure. Omnissa has taken the guesswork out of enterprise app management and elevated the security baseline for everyone using Horizon Cloud.

If you’re currently on the manual registration path, consider planning a migration to the Omnissa-managed approach. The transition offers immediate security benefits with reduced administrative overhead.

Getting Started

Ready to leverage Omnissa-managed registration for your deployment? The process is straightforward:

1.Initiate your Horizon Edge deployment in Omnissa Connect
2.Select the Omnissa-managed option during the Primary Provider setup

3.Link your Azure subscription using the consent flow (click Consent Link)

4.Authorize Omnissa to create the Enterprise Application

Insert Azure Subscription credentials (in my case Global Admin User)

Now we can see the new enterprise application with Omnissa Logo.

.

.

.

5.Assign necessary roles (Contributor or appropriate custom roles) to the subscription

First, verify the role assignment status in Omnissa Connect:

.

.

Get the Object ID from the Omnissa Enterprise App:

.

.

Go to your subscription and select IAM (Identity & Access Management):

.

Select add role assignment

Search Contributor in Previleged admnistrator Role

Select Member and ad the Enterprise Application Object ID or name

6.Refresh and verify the role assignment in Omnissa Connect

Return to the Omnissa Connect wizard. If the role is still showing as “Role not Assigned”

.

Go back to the previous step and return to refresh (Omnissa Engineer should add a refresh button)

.

.

.

At this point, you’re ready to choose whether your EDGE will be an AKS (Azure Kubernetes Service) or a Virtual Machine.

The Omnissa-managed Enterprise Application has been successfully created and configured with the naming convention omnissa-horizoncloud-app-1, marked with Omnissa’s branding for easy identification.

.

.

Conclusion

The shift to Omnissa-managed Enterprise App registration represents a meaningful step forward in cloud security practices. By removing the burden of service principal secret management from customer organizations, Omnissa enables secure, simplified, and scalable Horizon Cloud deployments on Microsoft Azure.

Whether you’re planning a new deployment or evaluating your current infrastructure, the Omnissa-managed method deserves your attention. It’s security and simplicity working in harmony—exactly what modern cloud deployments should be.

Microsoft Azure Edge and Omnissa-Managed Enterprise App Registration

Streamline Your Enterprise with Omnissa Connect and Microsoft Entra ID

A guide to enterprise federation, single sign-on, and modern identity management

What is Omnissa Connect?

Omnissa Connect is a centralized platform service that provides IT administrators and users with a single sign-on (SSO) gateway to access and manage all Omnissa services, such as Workspace ONE and Horizon. It streamlines workflows by unifying access, identity management, and service onboarding into one intuitive interface.

Key features of Omnissa Connect include:

•Unified Identity: Single sign-on capabilities and seamless integration with third-party identity providers like Microsoft Entra ID and Okta through the Omnissa Identity Service
•Centralized Administration: IT owners can securely assign roles, set multi-factor authentication (MFA) policies, and manage OAuth applications or API tokens across the entire Omnissa ecosystem
•Subscription Management: Visibility into all Omnissa service subscriptions from a single location

What is Microsoft Entra ID?

Microsoft Entra ID (formerly Azure Active Directory) is Microsoft’s cloud-based identity and access management service. It’s the foundation that millions of organizations use to manage employee identities, secure access to applications, and protect their digital assets.

Entra ID is likely already at the heart of your organization if you use:

•Microsoft 365 (Office 365, Teams, SharePoint)
•Azure cloud services
•Dynamics 365 or other enterprise applications
•Single sign-on (SSO) solutions for SaaS applications

Why Integrate Omnissa Connect with Microsoft Entra ID?

Connecting Omnissa Connect with Microsoft Entra ID through enterprise federation creates a powerful identity ecosystem. Here’s what you gain:

Single Sign-On (SSO)

Your users log in once with their corporate credentials and automatically gain access to Omnissa Connect—no separate usernames or passwords to remember.

Automatic User Provisioning

When you add or remove users in Entra ID, they’re automatically synced to Omnissa Connect. No manual account creation, no forgotten deprovisioning, no stale user accounts cluttering your systems.

Centralized Security

Manage all user access, permissions, and security policies from one central location. Apply multi-factor authentication (MFA), enforce password policies, and monitor access across your entire organization from Entra ID.

Reduced IT Overhead

Your IT team spends less time managing separate identity systems, resetting passwords, and troubleshooting access issues. Everything is automated and synchronized.

Improved Compliance

Maintain detailed audit logs of who accessed what and when. Meet regulatory requirements for access control and identity management with confidence.

A Real-World Example

Before Federation:

Sarah joins your company. The IT team manually creates accounts in Omnissa Connect, Microsoft 365, and four other systems. Sarah has to memorize 5 different passwords. When Sarah leaves three years later, the team forgets to deactivate her Omnissa Connect account, leaving a security gap.

After Federation:

Sarah’s first day: HR adds her to Entra ID. Omnissa Connect automatically creates her account and grants the right permissions. She logs in with her corporate email and password—the same one she uses for everything else. On her last day: HR removes her from Entra ID. Within seconds, Omnissa Connect and all other connected systems automatically deactivate her access. No manual steps. No forgotten accounts. No security gaps.

Is This Right for Your Organization?

Enterprise federation between Omnissa Connect and Entra ID is ideal if your organization:

•Already uses Microsoft Entra ID or Azure Active Directory
•Wants to simplify identity management and reduce IT burden
•Has multiple employees and wants to automate user provisioning
•Needs strong security controls and audit capabilities
•Is undergoing digital transformation and standardizing on cloud-based identity solutions

What’s Involved?

Configuring enterprise federation requires several steps—from verifying your domain to setting up the connection between systems to testing everything works smoothly. The process typically involves:

•Domain verification to prove your organization owns the domain
•Creating and configuring an Enterprise Application in Microsoft Entra ID
•Setting up authentication protocols and user attribute mapping
•Testing the setup before activating federation for all users
•Notifying users and helping them transition to the new authentication method

The Complete Step-by-Step Guide

While this overview covers the benefits and concepts, implementing enterprise federation involves detailed technical configuration. The complete guide is a comprehensive document with in-depth instructions, detailed screenshots, and step-by-step walkthroughs for both Omnissa Connect and Microsoft Entra ID configuration. Due to its length and technical depth, I share it directly with clients and organizations ready to implement the solution.

The complete guide includes:

•Detailed screenshots and instructions for each configuration step
•Exact fields to fill in on both Omnissa Connect and Entra ID

.

Ready to streamline your organization’s identity management?

If your organization is ready to implement enterprise federation between Omnissa Connect and Microsoft Entra ID, I’m here to help. Whether you need guidance on setup, troubleshooting during configuration, or best practices for managing the transition, I can provide a complete, step-by-step implementation guide tailored to your needs.

Get in touch to request the full technical guide and start your journey toward simplified, centralized identity management.

.

📧 Contact me for the complete implementation guide

Let’s simplify your organization’s identity and access management together.

Streamline Your Enterprise with Omnissa Connect and Microsoft Entra ID

Horizon 2603 is here!

A new version of Omnissa Horizon has just been released, and 2603 is not just another update — it’s an ESB (Extended Service Branch) release and marks an important transition point for many environments.

🔗 Release Notes:
https://docs.omnissa.com/bundle/horizon8-rnV2603/page/Horizon8-ReleaseNotes.html


First things first: end of support for vSphere 7 BY BROADCOM

Let’s start with something critical:

Horizon 2603 ESB  supports vSphere 7.x but is not the recommended version 

  • Horizon 2512 was the last release supporting vSphere 7 (Because vSphere 7 is end of life… Omnissa supports vSphere 7, but not Broadcom)
  • Starting from 2603, vSphere 8 is the recommended platform

This means one thing:
If you’re planning to move to this ESB, your vSphere upgrade is no longer optional — it’s very important 

This is a key architectural checkpoint, especially for environments that have been delaying the jump to vSphere 8. (vSphere 7 is end of support)


Event Database + Integrated Authentication (finally!)

Now, let’s talk about one of my favorite new features.

Horizon 2603 introduces the ability to configure the Event Database on Microsoft SQL Server using Active Directory identities (Domain User with Integrated Authentication).

No more SQL authentication.

Why this matters:

  • Eliminates stored SQL credentials
  • Aligns with enterprise security best practices
  • Simplifies credential lifecycle management
  • Improves compliance and auditability

From a design perspective, this is a very welcome step toward a more secure-by-default architecture.

 Final thoughts

This release is not just about new features — it’s about setting a new baseline:

  • ✔️ ESB = long-term stability
  • ✔️ vSphere 8 as the standard
  • ✔️ Stronger security integration

If you were waiting for the “right moment” to modernize your Horizon platform… this is probably it.


 In the next posts, I’ll dive deeper into the other new features and changes introduced in Horizon 2603 — stay tuned 👀


Need help testing or upgrading?

If you’re planning to:

  • Test Horizon 2603
  • Upgrade your existing environment
  • Move from vSphere 7 to vSphere 8 or 9

Feel free to reach out — happy to help with assessments, design, and upgrade strategies.


Have you already started testing Horizon 2603?
Or are you still planning your vSphere 8 migration?

Let’s discuss 

Horizon 2603 is here!

UPDATE – Remote Assistance Issue After January 2026 Windows Updates

Following up on the issue “Remote Assistance can’t make the connection”, as already mentioned in last week’s KB, the root cause has now been clearly identified.

The problem is related to recent Microsoft updates released for Windows 11, which address the security vulnerability CVE-2026-20824.

More specifically, the issue is documented in the following KB:

Remote Assistance feature of Omnissa Horizon View Administrator console, not working after January 2026 Windows security update (KB5074109) (6001252)

Note: The solution to this issue is described at the end of this post.

When Does the Issue Occur?

A key point to understand is that the issue is triggered if the updates are installed on either side of the Remote Assistance session:

  • The target machine (the device receiving assistance)
  • The operator machine (the device providing assistance)

 This means that even if your VDI environment is not patched, the error will still occur if the support operator is using a Windows 11 machine updated after January 2026.

The result is the well-known error:

Expected Fix

A permanent fix is expected to be released soon with Omnissa Horizon version 2603 (I hope cool)


Current Workaround

At the moment, if you want to provide Remote Assistance without removing Windows updates, you must follow a manual (and somewhat cumbersome) process.

Steps for the End User (Receiving Assistance)

  1. Click on the Start (Windows) button
  2. Search for and open Remote Assistance
  3. Select “Invite someone you trust to help you”
  4. Click “Save this invitation as a file”
  5. Save the file and share it with the support operator
  6. A security code will be displayed — share this code as well

Steps for the Support Operator

  1. Open the received invitation file
  2. Enter the provided security code
  3. Click OK

Final Step

  • The end user will receive a prompt to approve the connection
  • Once approved, the Remote Assistance session will start

Final Considerations

This workaround allows you to continue providing support without uninstalling security updates, but it is clearly less efficient compared to the standard workflow within the Horizon console.

Until the official fix is released, it is important to:

  • Inform support teams about the behaviour
  • Adjust troubleshooting procedures accordingly
  • Plan for the upcoming Horizon upgrade

Update (April 2026)
The issue described in this article regarding Remote Assistance after the January 2026 Windows updates has been resolved starting from Horizon Agent 2603, with the introduction of a specific registry key.

✅ Solution for Horizon Agent 2603 and later

With Horizon Agent 2603, the issue can be resolved by configuring the following registry key:

HKLM\SOFTWARE\Omnissa\Horizon\RemoteAssistance\fEnableLHTicket

STRING with value set to 1

This key enables a new Remote Assistance user experience, changing the behaviour compared to previous versions.

🧑‍💻 New user experience

When this setting is enabled:

  • The Remote Assistance session follows a more modern workflow aligned with recent Microsoft security changes
  • End users receive clearer and more contextual notifications
  • Compatibility with the latest Windows security updates is ensured

With the key modified, when a Remote Assistance session is initiated, the VDI user will see a code displayed on their screen (similar to the image below) that they must communicate to the operator to allow the operator to connect.

Versions before 2603

For Horizon Agent versions earlier than 2603, the registry key is not available by default.

In this case:

  • You must open a support request with Omnissa
  • Support can provide a specific/custom Agent build
  • Only with that version will it be possible to enable the registry key

Recommendations

    • Plan to upgrade to Horizon Agent 2603 or later whenever possible
    • Validate the registry configuration within your environment before production rollout
    • Test the new user experience to understand the behavioral changes
UPDATE – Remote Assistance Issue After January 2026 Windows Updates

Migrating Horizon from VMware to Omnissa: Why a Parallel Connection Server Deployment Is Often the Safest Approach

The transition from VMware Horizon to Omnissa Horizon introduced more than just a branding change. Starting with Horizon 2412 and continuing with later releases such as 2503 and 2506, several architectural and configuration elements have been modified.

These changes include licensing format updates, ADAM/AD LDS database modifications, registry key renaming, folder restructuring, and updated group policy templates.

While the official upgrade path works, in many environments a parallel deployment strategy can significantly reduce risk and allow end users to validate the new platform before switching production workloads.

This article outlines the key changes introduced by Omnissa and explains why building a new Horizon pod alongside the existing one can be a practical migration strategy.

.

Key Changes Introduced with Omnissa Horizon

1. New Licensing Model

Beginning with Horizon 2412, Omnissa introduced a new licensing mechanism and licensing portal.

During the transition phase, both VMware and Omnissa license keys are temporarily accepted, but this compatibility window is limited. Later releases, such as 2503.1 ESB and 250,6 rely entirely on the Omnissa License Module (OLM).

If a valid Omnissa license key is not installed after upgrading, the Horizon Console may enter a restricted or degraded mode.

Relevant KB and documentation references include:

• KB 6000212 – Horizon licensing transition guidance
• KB 6000745 – Omnissa rebranding changes and affected components

.

2. ADAM / AD LDS Database Changes

One of the most important backend changes affects the Horizon LDAP (ADAM/AD LDS) database.

Historically, Horizon used application partitions referencing the VMware namespace.
With the Omnissa rebranding, new environments now use the
horizon namespace.

Example:

Old partition naming:

dc=vdi,dc=vmware,dc=int

dc=vdiglobal,dc=vmware,dc=int

New partition naming:

dc=vdi,dc=horizon,dc=internal

dc=vdiglobal,dc=horizon,dc=internal

Omnissa provides a migration script to update the partition names after upgrading all pods to newer versions, such as 2503.

Relevant documentation:

• KB 6000797 – ADLDS partition migration for Horizon

.

3. Registry Key and File System Changes

The rebranding also impacted multiple components of the Horizon installation:

Component

Previous Location

New Location

Installation folder

C:\Program Files\VMware\VMware View

C:\Program Files\Omnissa\Horizon

Logs

C:\ProgramData\VMware\VDM\logs

C:\ProgramData\Omnissa\Horizon\logs

Registry keys

HKLM\Software\VMware, Inc.\VMware VDM

HKLM\Software\Omnissa\Horizon

ADAM DB instance

VMwareVDMDS

OmnissaHzeDS

Because registry paths changed, Group Policy templates (ADMX) were also updated and must be replaced during upgrades.

Failure to update the ADMX files can lead to policies silently no longer applying.

.

Why a Parallel Horizon Deployment Can Be a Better Migration Strategy

Although a direct upgrade of the Connection Servers is supported, the number of changes introduced with the Omnissa transition makes a greenfield-style deployment attractive.

Instead of upgrading the existing servers, consider deploying new Connection Servers alongside the current environment.

Advantages include:

1. Opportunity to Upgrade Windows Server

New Connection Servers allow administrators to deploy a modern operating system, such as:

• Windows Server 2022 or later (Windows 2025 is a like option)

This avoids performing multiple upgrades on the same system.

.

2. User Acceptance Testing

With a parallel deployment, you can:

• publish test desktop pools
• provide pilot users access
• validate authentication flows
• verify DEM and App Volumes integration

Users can test the environment before the production switch.

.

3. Reduced Upgrade Risk

Upgrading in place modifies:

• ADAM database
• registry keys
• services
• folder paths

A clean installation avoids potential issues caused by legacy configurations.

.

Example Parallel Migration Architecture

A typical migration architecture might look like this:

Existing Environment

• Horizon Connection Servers
• Unified Access Gateways
• Instant Clone pools
• DEM and App Volumes

New Environment

• New Omnissa Connection Servers
• New Omnissa Unified Access Gateways
• Same vCenter Server
• Same Active Directory
• Same desktop images
• Same DEM*
• Same App Volumes*

*After migration, it will be upgraded.

This allows a staged migration.

Key points:

• vCenter Server can remain unchanged
• Desktop pools can be recreated or migrated
• User profiles continue to work through DEM

.

Migrating Instant Clone Desktop Pools

In environments heavily using Instant Clones, rebuilding pools manually can be time-consuming.

Automation scripts can accelerate the process by exporting and recreating pools through the Horizon APIs.

In my environment, I use a PowerShell-based migration script that reads the configuration of Instant Clone pools and recreates them on the new pod.

This allows administrators to migrate:

• pool configuration
• entitlements
• naming patterns
• provisioning settings

with minimal manual effort.

This is the link to the script

OMNISSA/OMNISSA – Export and Import Desktop and Entitlements v7.ps1 at main · fabio1975/OMNISSA

.

Reusing DEM and App Volumes

Existing deployments of

• Omnissa Dynamic Environment Manager
• Omnissa App Volumes

can usually remain unchanged during migration.

However, compatibility must always be validated using the official interoperability matrix.

Relevant documentation:

• Horizon interoperability matrix
• App Volumes compatibility with Horizon
• DEM compatibility with Horizon

Official documentation:

These matrices confirm supported combinations between:

• Horizon versions
• App Volumes
• Dynamic Environment Manager
• vCenter Server
• ESXi

.

Suggested Migration Workflow

A practical migration process could look like this:

    1. Deploy new Connection Servers with Omnissa Horizon
    2. Deploy new Unified Access Gateways
    3. Connect the new pod to the existing vCenter
    4. Validate App Volumes and DEM compatibility
    5. Recreate or migrate Instant Clone pools
    6. Perform pilot user testing
    7. Switch production access
    8. Decommission legacy Connection Servers
    9. Create the news GPO for Horizon (we need use the new GPO Templates)
    10. Upgrade the Horizon Agent, DEM and App Volumes

    .

    Final Thoughts

    The transition from VMware Horizon to Omnissa Horizon introduces several structural changes that go beyond simple branding.

    Changes in licensing, LDAP partitions, registry paths, and policy templates can complicate traditional upgrade workflows.

    For many environments, especially large VDI deployments, deploying new Connection Servers in parallel offers a safer and more flexible migration strategy.

    It provides an opportunity to modernize the infrastructure, validate compatibility with components such as App Volumes and DEM, and allow users to test the platform before the final cutover.

    .

    .

    Migrating Horizon from VMware to Omnissa: Why a Parallel Connection Server Deployment Is Often the Safest Approach

    Horizon Cloud Service Next Gen Apis – Chapter 2

    Immagine che contiene testo, Neon, Segnali luminosi, Insegna al neon Il contenuto generato dall'IA potrebbe non essere corretto.

    Set Syslog settings across UAG deployments

    In this second article on working with APIs in Horizon Cloud Services, we will focus on a practical, security-relevant use case: configuring Syslog on Unified Access Gateways (UAGs) deployed through Horizon Cloud.

    Whether you are running Horizon Cloud Service on Microsoft Azure or Horizon Cloud Service on vSphere, centralized logging is a fundamental component of any secure and well-governed environment. Proper Syslog configuration ensures that security events, authentication logs, and operational data generated by UAG appliances are forwarded to your SIEM or log management platform for monitoring, auditing, and incident response.

    Instead of performing manual configuration tasks, we will explore how to leverage Horizon Cloud APIs to automate and standardise Syslog settings across UAG deployments, improving consistency, scalability, and operational efficiency.

    Now when can explain the API we need to use and how to apply the syslog configuration on UAG (In this case, I used an HCS on vSphere, the new solution where we don’t deploy the Connection Server, but we use the HCS control panel to configure Pools, Entitlements and other…)

    The first step is always the authentication process; I explained how to create the API token in my previous post (Horizon Cloud Service Next Gen Apis – Chapter 1), and now I won’t explain it again.

    Let’s go…..

    How to show UAG information

    This command displays the UAG’s information

    Invoke-RestMethod -Uri https://cloud-sg.horizon.omnissa.com/admin/v2/uag-deployments Method Get -Headers $Header

     We have two UAG deployments connected to HCS, and the output displays two deployment ids:

    Immagine che contiene testo, schermata, Carattere Il contenuto generato dall'IA potrebbe non essere corretto.

    The UAG id for HCS on vSphere is the second id.

    Immagine che contiene testo, schermata, Carattere Il contenuto generato dall'IA potrebbe non essere corretto.

    Now I need to recover only the UAG IDs and OrgIDs

    Invoke-RestMethod -Uri https://cloud-sg.horizon.omnissa.com/admin/v2/uag-deployments -Method Get -Headers $Header | Select-Object -ExpandProperty content | Select-Object id,OrgId

    Immagine che contiene testo, schermata, Carattere Il contenuto generato dall'IA potrebbe non essere corretto.

    The UAG id that I need to use for identifying the deployment for HCS on vSphere is:

    6994998bcb2a7086afaddf1c 

    I will use this ID to associate the syslog configuration with the UAG server.

     

    How to set the correct parameters for Syslog configuration

    We need to create a Body value like this:

    $Body = @{
      orgId  = "8a4931b3-e6ac-44bf-9d25-723f4119e46f"
      projectId = "Pollaio-Project"
      name = "Pollaio-Configuration2"
      syslogEventCategory = "ALL_EVENTS"
      syslogServerProtocolSettingsCreateTO = @{
        sourceToSyslogServerProtocol = "TCP"
      }
      syslogFormat = "TEXT"
      syslogURI = "192.168.111.223:514"
      includeSystemMessages = $true
      sources = @(
        @{
          type = "UAG"
          id   = "6994998bcb2a7086afaddf1c"
        }
      )
    }

    .

    Where:

    Value Description Accept value
    OrgID It is the OrgId that we recovered with the previous command String
    ProjectId ID of theCSP project that owns this data String
    Name User defined name of the syslog server configuration String
    SyslogEventCategory Events sent from the UAG appliance to the syslog server [ ALL_EVENTS, AUDIT_EVENTS ]
    sourceToSyslogServerProtocol The protocol used to send data from the UAG appliance to the syslog server [ UDP, TCP, TLS, MQTT ]
    syslogFormat [ JSON_TITAN, TEXT ]
    syslogURI Syslog server URI String
    includeSystemMessages If true, system messages are sent to the syslog server [ $True]
    sources

    List of sources associated with the syslog server:

    Type = Source for the syslog server. For es: UAG

    Id = Id of the source associated with the syslog server (The Id value that we recovered with the previous command

     

    .

    .

    How to set the configuration for UAG
    $Body = @{
      orgId  = "8a4931b3-e6ac-44bf-9d25-723f4119e46f"
      projectId = "Pollaio-Project"
      name = "Pollaio-Configuration2"
      syslogEventCategory = "ALL_EVENTS"
      syslogServerProtocolSettingsCreateTO = @{
        sourceToSyslogServerProtocol = "TCP"
      }
      syslogFormat = "TEXT"
      syslogURI = "192.168.111.223:514"
      includeSystemMessages = $true
      sources = @(
        @{
          type = "UAG"
          id   = "6994998bcb2a7086afaddf1c"
        }
      )
    }
    
    #Convert Body to JSON
    $JsonBody = $Body | ConvertTo-Json -Depth 5
    #Send POST request to create Syslog Server UAG configuration
    Invoke-RestMethod -Uri https://cloud-sg.horizon.omnissa.com/admin/v1/syslog-server -Method Post -Headers $Header -Body $JsonBody
    HOW to check SYSLOG Configuration on UAG deployment

     

    Invoke-RestMethod -Uri https://cloud-sg.horizon.omnissa.com/admin/v1/syslog-server -Method Get -Headers $Header
    

    The command output is like this:

    .

     Now I can see in my SYSLOG server the UAG Log

    Immagine che contiene testo, schermata, Carattere Il contenuto generato dall'IA potrebbe non essere corretto.

    .

    .

    .

    Horizon Cloud Service Next Gen Apis – Chapter 2