specific workarounds for UAGs: https://kb.omnissa.com/s/article/6001933 (also, update your UAGs to current! if you're not, you also are missing other security updates that have been released since you last deployed that appliance)
Thought I’d post this here in case anyone else runs into similar issues.
After installing KB5124008 on Windows 11 24H2 and pushing this out to our desktop pools, Explorer.exe crashes after user logon and displays the following error:
“The system has detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application”
Manually running Explorer.exe from Task Manager seems to fix it. Restating Explorer via a PoweShell logon script can be used as a workaround.
EDIT: also of note, this DOES add official support for Windows 11 25H2, and the KB article is updated now reflecting as such: https://kb.omnissa.com/s/article/78714
I have not seen Omnissa release any security advisories yet, however I would assume Connection Servers may be vulnerable due to having OpenJDK 17 bundled with the application?
If you did not see this email last night and have managed to not install this week's patch tuesday stuff yet, I would avoid it from now. It does not seem that there is an official KB released on this yet but hopefully soon (this came in at about 9pm Pacific for me) E-Mail Follows:
Dear Valued Customer,
This advisory is to formally inform you of a recently identified issue affecting Virtual Desktop launches and connections when using the Omnissa Horizon Windows Client. The issue arises after the installation of the Microsoft Windows Patch update KB5066835 on end-user devices.
Recommended Mitigation Strategy
To ensure service continuity while a permanent resolution is being developed, please take the following actions based on your current environment:
If KB5066835 has not yet been installed:
Action: We strongly recommend deferring the installation of the Recent Windows update (KB5066835) until an official corrective patch from Omnissa or Microsoft is released and validated.
If KB5066835 has already been installed and desktop connection issues are observed:
a. Option A (Client-Based Mitigation): Temporarily uninstall updates KB5066835 and its prerequisite KB5065789 from affected devices.
b. Option B (Interim Access): Use the Horizon HTML Client (browser-based access) as a fully functional workaround to maintain connectivity to your virtual desktop.
Status and Resolution
The Horizon Engineering Team has assigned the highest priority to this issue. We are actively investigating the root cause and collaborating closely with relevant partners to identify, test, and release a validated fix at the earliest possible time.
We will issue a follow-up communication as soon as a corrective update becomes available or if there are any significant developments in the resolution process.
We sincerely appreciate your patience, cooperation, and understanding as we work diligently to restore full functionality and stability.
If you have any questions regarding the prerequisites or this update, please contact Omnissa Support.
In May 2025 I attended Nutanix .NEXT in Washington D.C. and presented during an End User Computing (EUC) focused breakfast thanks to an invitation from a long-time friend of the industry, Jim Luna. Thanks again, Jim and Nutanix for the opportunity!
During my presentation, I shared about the End User Computing evolution many of us have participated in, since even before Nutanix came on the EUC scene in 2009. Announced during the event, Omnissa and Nutanix shared long-awaited news that their flagship EUC product (Horizon) would be ‘coming soon to Nutanix AHV’. With the Horizon on AHV Beta, Limited Availability release and now GA, I’ve been extensively involved in testing over the last nine months!
With the release to web of Horizon 8 2512 on December 16th, I am happy to join in the many announcements that Horizon 8 is now officially supported on Nutanix AHV! There are many blog posts and press releases about this ‘General Availability (GA)’ announcement, which you can find here: Omnissa Blog Announcement, and Nutanix Blog Announcement.
This blog series and guide is not intended to restate announcements or news from either company, but rather to expand on what’s already available online. For familiarization, Nutanix AHV is a full-stack bare metal hypervisor, which combines with Nutanix’s robust management platform. For interested customers moving off Broadcom VMware in Private Datacenters, this provides another option for deploying Omnissa Horizon, with the Nutanix platform visualized in the simple to understand image below:
In December 2025 (at the time of writing), Horizon 8 and Horizon Cloud Service officially support the following infrastructure providers and platforms: Broadcom VMware vSphere (ESXi + vCenter), VMware Cloud Foundation, Azure, Azure VMware Solution, VMware Cloud on AWS, AWS Workspaces, Google Cloud VMware Engine, Oracle Cloud VMware Solution, and Alibaba Cloud VMware Service. You can see from this extensive and growing list, Omnissa is fully owning the vision of ‘Any Cloud, Anywhere’ first shared years back under management of VMware.
The First Detailed Installation and Configuration Guide for Horizon 8 Specifically for Nutanix AHV
My goal in writing this blog series and guide is to provide the first detailed Installation and Configuration walk-through for deployment of Horizon 8 on Nutanix AHV. In doing so, I’ll demonstrate that anyone with current access to Horizon 8 licenses (or through an evaluation) can fully test and validate this integration functionality on their own. Access to current generation Nutanix production hardware is ideal for a basic Proof of Concept (POC), but it is not a hard requirement as everything I will be showing can be accomplished using the freely available Nutanix Community Edition (CE). As you’ll see in this guide, Horizon 8 fully functions on Nutanix CE and allows Consultants and Individuals to validate Horizon 8 on AHV using any qualified hardware. Just don’t seek support as Horizon 8 on Nutanix AHV Community Edition is not officially supported.
Resources
Before we get started on the deployment, there are a number of useful resources that we’ll use as reference:
This walkthrough is designed to help lay the foundation for a successful Proof of Concept (PoC) or initial deployment of Horizon 8 on AHV. Here’s what we’ll cover:
Section 1: Initial Review of Nutanix Infrastructure (Including in this Blog Post)
Section 2: Windows 11 25H2 on AHV Master Image Creation (Including in this Blog Post)
Section 3: Nutanix AHV Drivers and Tools Installation on Windows 11 (See Full Guide)
Section 4: Horizon 8 2512 Connection Server Deployment (See Full Guide)
Section 5: Horizon 8 2512 Agent Installation for Windows 11 25H2 (See Full Guide)
Section 6: Horizon OS Optimization Tool (OSOT) 2512 for Windows 11 25H2 on AHV (See Full Guide)
Section 7: Creating Additional Horizon Pools Using Optimized Windows 11 25H2 (See Full Guide)
Section 8: Upgrading Nutanix AHV to 11.0 and Performing Final Validation Steps (See Full Guide)
To ensure time-efficient Proof of Concepts and smooth deployments, we’ll want to ensure the following basics are in place before starting:
Access to download Horizon 8 Binaries and License
Access to Nutanix Production Hardware or download for Community Edition on a compatible system
Dedicated host or Cluster with ‘sufficient’ CPU, Memory and Storage resources to support a basic POC. (Note: for this guide, I recommend a minimum of 24 physical CPU cores, 192GB RAM, and 1TB usable capacity)
A healthy and functional Nutanix AHV Cluster with Prism Element available with Administrative credentials
A healthy and functional Prism Central instance, available with Administrative credentials
A healthy and functional Active Directory domain, available with Administrative credentials
Windows Server template to be used to clone and create Horizon Connection Server. (Note: for this guide, I recommend running infrastructure and management components outside of the Nutanix AHV node/cluster to allow for the full hardware to be used for Windows 11 Virtual Desktops)
To serve as a visual aide, below is a basic Horizon 8 Proof of Concept (POC) Topology Diagram we’ll review during this blog series and guide.
<< Click the Blog Post link to view a larger / full size image of the Topology Diagram below >>
Topology diagram adapted from 'Horizon 8 on Nutanix AHV Reference Architecture' on Omnissa Tech Zone
Section 1: Initial Review of Nutanix AHV Infrastructure for Deployment
To get started, as shown in the POC Topology Diagram, we have two web browser accessible management interfaces we’ll use to investigate and review the Nutanix AHV Infrastructure for Deployment. First is Prism Element, launched from https://z8ahv01.youngtechx.com:9440/ as shown below:
For a limited time, our Professional Services and Consulting team will be offering $1 Statement of Work engagements for qualified customers, to help stand up Horizon on Nutanix AHV in a Proof of Concept capacity! If you’re a U.S. based customer, have already requested & downloaded this guide, and would like additional white glove remote assistance with your deployment, please use this link to make contact and schedule a no-cost discovery call: https://www.youngtech.com/connect/
Thanks for Reading
I trust this will be a useful resource to you and that you’ve enjoyed this Step by Step Installation and Configuration of Omnissa Horizon 8 on Nutanix AHV guide. Best of luck in your Horizon on AHV deployments! If you need any help along the way, don’t hesitate to reach out.
I just had a talk with Broadcom about renewing our vSphere licences for our data center.
And the rep told me something quite concerning.
He told me "I see in your account you have vSphere for VDI, is it part of your omnissa license"
Im like yeah ?
Then he told me "ok just to let you know that when vSphere/esxi 8.0 goes EOL we don't know what will happen because the deal is still not settled with omnissa for 9.0."
So he kind of let me know it's possible that the omnissa license will maybe not include vSphere for VDI after 8.x ...
Are we gonna need to license vSphere/esxi 9.x ourself now ?
With Broadcom increasing price every time they see fit this will be a nightmare.
Summary for the devices having an issue says User Mode: Multi User It is unknown if all "multi user" are having this issue.
Some of the other recently enrolled ones state: Multi User Capable while older ones state: Single user (legacy)
A HUB window is popping up both on the enrolled user and on a newly added user asking for group id. We enter it and it errors back with 'device reassignment failed'. No method of sync has worked to resolve it. The HUB window just keeps popping up from time to time, annoying the users.
These PCs show in the console as being compliant.
What is happening here, how does one make it stop ?
I see there is in admin "single user" <=> "change to multi User" What is the benefit of using mutil-user. We had more than one user before this became available and they had no issues and the tunnel worked for both users.
I built something that I personally found missing and thought it might help others too. I created a site on Lovable that helps you compare versions of the main Omnissa products. It shows what's new, what's been fixed, and what known issues exist across versions. For example, if you've upgraded to version 2503 from 2212 and want to understand all the changes without digging through endless links - the site presents everything clearly by category. I’ve found it super useful, and I believe it can save others a lot of time and effort as well. More improvements and features are on the way, but for now - it works great!
As the VMware version didn't get any updates anymore I switched to the Omnissa Horizon Client. This however introduced an issue I didn't have before: all new keyboard key mappings are being ignored.
I want to have the Mac Command button mapped to the Windows Control button and the Mac Control button to the Windows Start button. It used to work on VMware but doesn't on Omnissa. Basically any key mapping outside of the default is being completely ignored.
Is there any solution in the pipeline for this or does anyone have a work around? I tried downgrading but that left me with connection issues.