If you've built your virtual desktop infrastructure on VMware Horizon over the last decade, you've been watching a slow-motion corporate earthquake with a mixture of anxiety and cautious optimism. First came Broadcom's $69 billion acquisition of VMware in 2023. Then, almost immediately, Broadcom's CEO labelled End User Computing a "non-core asset" and put it up for sale. Private equity firm KKR stepped in with a $4 billion cheque, and on July 1, 2024, the newly independent company announced its name to the world: Omnissa.

The name might be unfamiliar, but the technology underneath it is not. Horizon, Workspace ONE, App Volumes — all of it survives and, according to the company's 2025 roadmap, is being accelerated in ways that simply weren't possible when EUC was a line item inside a larger enterprise software giant. But surviving a rebrand and thriving because of one are very different outcomes. As an IT leader, the question isn't whether Omnissa is real. It demonstrably is. The question is: what does this mean for the EUC strategy you're executing right now?

From VMware EUC to Omnissa: The Story So Far

To understand where Omnissa is going, it helps to understand exactly how it got here. When Broadcom finalised its VMware acquisition in late 2023, the writing was on the wall for EUC almost immediately. Broadcom had a clear playbook: focus on the highest-margin enterprise infrastructure products and divest anything that didn't fit the core thesis. Virtual desktops and endpoint management, while genuinely valuable, didn't make that cut.

KKR's acquisition was financed and structured to give the EUC division something it arguably never had as a VMware business unit — undivided executive attention, dedicated R&D investment, and the freedom to build its own partner ecosystem from scratch. Shankar Iyer, who had led VMware EUC since 2018, stepped in as CEO and has been remarkably candid about the opportunity: this is a business that serves tens of thousands of enterprises globally, and it now has the independence to innovate specifically for those customers rather than fitting into a broader corporate roadmap.

Key Milestones

What Actually Changed (And What Didn't)

Let's be direct: if you are a Horizon administrator who woke up the morning after the rebrand expecting everything to look different, you were in for a quiet surprise. The core technology — the Connection Server, the virtual desktop infrastructure, the Workspace ONE UEM console — didn't fundamentally change overnight. What changed was ownership, direction, and licensing.

The licensing piece is worth dwelling on because it has generated real administrative work. Horizon 8 releases from version 2503 onward have transitioned away from VMware/Broadcom license modules to a new Omnissa License Module (OLM). If you upgrade without valid Omnissa keys, your deployment enters a restricted mode. That's not a disaster, but it is exactly the kind of friction that catches organisations off guard if they haven't planned their upgrade path carefully.

On the branding side, the changes run deeper than just logos. File paths, ADAM database partitions, service names, registry keys, and Group Policy templates have all been renamed to reflect the Omnissa identity. For most production environments, this surfaces during upgrades — scripts and automation tools that reference old VMware-named paths will need updating. It's worth auditing your Horizon automation before your next major version bump.

The 2025 Roadmap: Three Bets That Matter

The most telling signal of where Omnissa intends to go came out of Omnissa ONE 2025 in Las Vegas — the company's flagship annual conference. Three strategic themes dominated every session and every product announcement, and each one has direct implications for EUC strategy planning.

Bet #1: Break the VMware Infrastructure Lock

For years, running Horizon meant running vSphere. Full stop. That dependency was manageable when VMware controlled both sides of the equation, but post-Broadcom acquisition, many Horizon customers found themselves facing steep vSphere licensing increases. Omnissa heard the frustration and responded with what may be its most strategically significant 2025 move: opening Horizon to run on multiple hypervisors.

The headline announcement was Horizon on Nutanix AHV. Nutanix's modern hypervisor, purpose-built for hyper-converged infrastructure, can now host Horizon virtual desktops — giving organisations a credible on-premises VDI path that doesn't require VMware ESXi licensing. A partnership with Platform9 takes this further, enabling Horizon Cloud to run on private cloud infrastructure with enterprise features like live migration and dynamic resource rebalancing, without proprietary hardware requirements.

“Our customers are focused on outcomes, not tools. By giving IT teams an integrated, open platform to manage across any user, app, device, or cloud, we're enabling organisations to adapt to the way people work — not the other way around.”

— Bharath Rangarajan, SVP Products & Technology Alliances, Omnissa

Bet #2: AI-Powered Digital Employee Experience (DEX)

The second major strategic thrust is embedding AI directly into the day-to-day operational fabric of Horizon and Workspace ONE. This isn't marketing language for a chatbot bolted onto a dashboard. Omnissa has shipped several genuinely useful AI capabilities that change how IT teams work.

1  AI-guided root cause analysis for VDI issues Logon-time anomalies, last-mile network telemetry, and performance degradation are now surfaced with AI-recommended remediation steps — not just raw data dumps for engineers to decode manually.

2  DEX Playbooks with closed-loop feedback IT teams can define automated remediation playbooks, get AI-recommended action paths, and then feed real-world outcomes back into the model to continuously refine future recommendations.

3  Omnissa Monitor (on-premises) For organisations that are deliberately not cloud-connected, Omnissa Monitor delivers unified monitoring across on-premises Horizon pods with ITSM integration for automated ticketing and remediation — closing a gap that previously forced on-prem customers into expensive third-party DEX tools.

4  NVIDIA Blackwell GPU support Horizon now supports NVIDIA RTX PRO 6000 Blackwell Server Edition GPUs with vGPU software, enabling far greater workload density for GPU-intensive VDI use cases — from knowledge workers running creative apps to AI developers who need GPU access in a managed virtual environment.

Bet #3: Platform Consolidation Over Tool Sprawl

The third theme is perhaps the most important for EUC architects thinking about long-term strategy. Omnissa is making a deliberate argument that the future of EUC is a unified platform — not a collection of point tools for desktops, servers, mobile devices, and frontline workers that each require their own management console, their own licensing agreement, and their own support relationship.

Workspace ONE UEM now extends to Windows Server OS management — unifying server lifecycle management (patching, inventory, remote support, configuration) alongside desktop and virtual endpoint management in a single console. Same-day Apple platform support, achieved through direct integration with Apple's GitHub repository, means Omnissa can ship DDM configurations and profile payloads the moment Apple releases a new OS. For organisations managing mixed fleets of Macs, iPhones, and Windows VDI sessions, this kind of platform cohesion has real operational value.

What This Means for Your EUC Strategy Right Now

If you're in the middle of a VDI refresh cycle, a Horizon licensing renewal, or a broader digital workspace strategy review, here's the honest assessment: Omnissa's independence has been, on balance, a positive development for Horizon customers. The product is receiving more focused investment than it did inside VMware, the hypervisor lock-in is genuinely being dismantled, and the AI-driven operational capabilities are ahead of where most organisations expected them to be at this stage of the company's independence.

That said, the transition introduces real complexity that deserves proactive attention. Licensing migration, file path changes, and the shift to Omnissa-native tooling all require planning — especially if you have mature automation built on the old VMware naming conventions. Treating this like a simple vendor rebrand would be a mistake.

Your Omnissa Transition Checklist

→  Audit all Horizon automation scripts for VMware-named file paths, registry keys, and service names that need updating post-rebrand.

→  Validate your licensing position — confirm your Omnissa License Module (OLM) keys before your next major Horizon upgrade to avoid restricted-mode deployments.

→  Evaluate your vSphere dependency. If you're facing Broadcom licensing pressure, the Nutanix AHV integration and Platform9 private cloud options are now viable alternatives worth a proof-of-concept.

→  Build a DEX baseline now. Omnissa's AI capabilities work best with historical telemetry data — deploy Experience Management for Horizon early to start capturing the logon times and network data that will power future AI remediation.

→  Review your partner relationships. Broadcom dismantled VMware's traditional partner ecosystem; Omnissa has been rebuilding it. Confirm your reseller or MSP has an active Omnissa partnership before your next renewal.

→  Plan for the autonomous workspace roadmap. Omnissa's stated goal is a self-configuring, self-healing, self-securing workspace. Understand which elements (DEX Playbooks, QuickFlows, Freestyle Orchestrator) are GA today vs. still in limited preview.

The Bigger Picture: Why Omnissa's Independence Matters for EUC

There's a broader industry point worth making here. End User Computing has often been treated as a second-tier concern inside large enterprise software vendors — important enough to keep, not quite important enough to properly fund. The result, for many years, was incremental Horizon releases that kept pace with Windows updates but rarely set the pace for innovation.

Omnissa operating as an independent, KKR-backed company changes the incentive structure entirely. This is now an organisation whose entire market value rests on the quality of its EUC products. There are no cross-subsidies from hypervisor revenues, no platform-level politics about which division gets R&D budget, and no strategic ambiguity about whether Horizon is core to the company's mission. It is the mission.

The early evidence — the multi-hypervisor support, the AI-native DEX tooling, the same-day Apple platform integration, the aggressive partner ecosystem expansion — suggests Omnissa is spending that independence well. The autonomous workspace goal, which would have sounded like conference keynote aspirationalism two years ago, looks increasingly like a credible product roadmap in 2025.

For IT leaders, the most productive frame for thinking about this isn't "should I trust the new brand?" It's "does this product roadmap solve the problems I actually have?" Right now, for most organisations running Horizon in hybrid work environments, the answer appears to be yes — with a clear-eyed understanding of the migration work required to get there fully.

Omnissa isn't asking you to forget ten years of VMware investment. It's asking you to carry that investment forward into a platform that, for the first time, is singularly focused on making your workforce's digital experience better. That's an offer worth taking seriously.