Omnissa Horizon
The vSphere-native DaaS platform with Instant Clone technology, App Volumes and Blast Extreme — ideal for organisations with an existing VMware estate. Choose add-ons for extended enterprise scenarios.
As at September 2026
Build your Horizon configuration
Omnissa Horizon covers 10 of the 12 core modules from the service itself — App Volumes, the Dynamic Environment Manager and the Unified Access Gateway are part of Horizon Cloud. What remains open is auto scaling and policy control by device posture; for that, Workspace ONE UEM is added, licensed separately.
The feature set at a glance
Which of the twelve core capabilities of a modern workplace stack does your configuration cover natively — and where are extensions needed? Each puzzle piece shows the maturity.
The twelve modules — what is in, what is missing?
Each module describes one core capability of the workplace stack. The colour shows its current status in your configuration. Select add-ons in the configurator above and you will see here which module improves and why.
Endpoint platform (outside the puzzle)
Through its Workspace ONE heritage Omnissa brings its own endpoint stack. The Horizon Client runs on every platform, IGEL OS has deep Blast Extreme integration and UniconOS (formerly Unicon eLux) offers a native Blast client. Often the first choice for complex endpoint estates.
Horizon Client · Omnissa
The official Omnissa client — available for Windows, macOS, Linux, iOS, Android, ChromeOS and HTML5 browsers. Blast Extreme with USB redirection, smart card, multimedia redirection and session collaboration — but features differ by client: in a browser, the Horizon Web Client supports USB redirection to Windows virtual desktops but neither smart cards nor Windows Media MMR; further features come with the installed clients.
IGEL OS · IGEL Technology
A Linux-based thin client operating system with deep Blast Extreme integration. Read-only, chain-of-trust boot, preventive security model. Often the first choice for Zero Trust endpoints in Horizon deployments.
UniconOS / UniconOS Management (formerly eLux / Scout) · Citrix (Unicon GmbH)
A German thin client operating system with a native Blast client, managed centrally through UniconOS Management (formerly Scout Enterprise). Recommended by the BSI and often the standard in public bodies and the financial sector.
Workspace ONE UEM · Omnissa
Omnissa’s endpoint management platform — managing Windows, macOS, iOS, Android and virtual desktops in one console. Available as an add-on bundle for a unified experience across physical and virtual endpoints.
All sensible Horizon combinations compared
Omnissa Horizon is rarely used on its own — almost always in combination with App Volumes, DEM and/or Workspace ONE UEM. This matrix shows typical DACH configurations. Following the VMware and Omnissa spin-off, specific licence terms should be obtained directly from the vendor.
| Setup | Modules native | Target group | What changes compared with “Horizon on its own” |
|---|---|---|---|
| Horizon StandardThe simplest Horizon setup | 7 / 12 | Smaller vSphere estates, straightforward VDI deployments | The baseline with 7 of 12 modules fully native. App Volumes, DEM and UAG are missing and are added through Horizon Enterprise. |
| Horizon EnterpriseStandard enterprise bundle (App Volumes + DEM + UAG) | 10 / 12 | Mid-market to enterprise, complete VDI deployments | App Volumes, DEM, UAG in the bundle. 10 of 12 modules fully native — only autoscaling and conditional access policies remain open. |
| Horizon UniversalA subscription with full flexibility | 10 / 12 | Multi-cloud deployments, organisations without a named-user model | A subscription for either named users or concurrent connected users, with full flexibility across vSphere, Azure, AWS and GCP. The same feature set as Enterprise. |
| Horizon Enterprise + Workspace ONE UEMUnified Endpoint Management | 11 / 12 | Organisations with a mixed endpoint estate (Windows, Mac, iOS, Android plus VDI) | UEM for physical and virtual, ZTNA, compliance policies in a single console. The policy module becomes fully native. |
| Horizon + IGEL OSZero Trust endpoint setup | 7 / 12 | Regulated industries with endpoint hardening requirements | Hardened thin client endpoints with deep Blast integration. Not a direct module upgrade, but strategically important for Zero Trust compliance. |
| Horizon Enterprise + ControlUpFor DEX-critical environments | 11 / 12 | Enterprises with strict service level commitments, help desk-intensive setups | DEX-Score at user level, auto-remediation, monitoring of physical and virtual endpoints — and it closes the autoscaling gap through ControlUp’s score-based scaling. |
Horizon’s strengths
- Instant clones on vSphere capacity — new machines are created within seconds, by default directly from a replica VM without a parent VM
- The Blast Extreme protocol — optimised for WAN and low bandwidth, with adaptive TCP and UDP
- A vSphere-native architecture — full control of the hypervisor layer, ideal integration for VMware shops
- Linux desktops natively and completely — Microsoft supports Windows only in AVD and Windows 365
- App Volumes and the Dynamic Environment Manager are part of the service; Workspace ONE UEM is added separately
- Workspace ONE UEM manages physical endpoints alongside virtual ones: Windows, macOS, iOS, Android and thin clients from one console — even without a Microsoft 365 agreement
- The help desk tool has been available in almost every edition since version 2506 (previously Enterprise only)
- Instant clones solve host repair elegantly: instead of repairing an unhealthy host, it is recreated within seconds
- Nutanix AHV support has been GA since Horizon 8 2512 — an alternative to vSphere
Gaps & what to add
- Autonomous Mode was to be rolled out “through the month of March” according to release 2602; cost recommendations arrived in beta with the update of 15 April 2026, and later release notes name no newer maturity
- Horizon 8 Advanced (Term) was discontinued in August 2026 — existing customers need a migration path
- Since 2606 creating new images with Windows 10 22H2 or Windows Server 2016 is no longer supported and will be blocked; existing ones keep running but receive no further updates
- The vSphere dependency ties desktop costs to Broadcom price developments. Nutanix AHV has been generally available for Horizon 8 since 2512 and an alternative as a Horizon Cloud provider in limited availability since 2608, but moving an existing environment remains laborious — Citrix by contrast allows a free choice of hypervisor during operation
- A young independent company: since the spin-off from VMware the product portfolio has already been adjusted — with contract terms of three to five years, a point for risk assessment
- Several interfaces side by side: Horizon Universal Console, Horizon Console and the Workspace ONE consoles are separate; a unified global search in the Universal Console exists since Service Release 2511 (3 December 2025)
- High complexity in multi-pod deployments with the Cloud Pod Architecture
- Teams optimisation: Microsoft now lists its new SlimCore media engine as generally available for Omnissa Horizon too, as with AVD, Windows 365 and Citrix; it requires Horizon Client for Windows 8.17 (2512) or later
- Blast Extreme is strong on the local network but weaker than Citrix HDX on poor connections
- Windows licensing and RDS access licences come from Microsoft on top — Omnissa supplies only provisioning and management
- Horizon 9 Cloud-Native (on the roadmap) is not yet available — the legacy architecture still dominates
The assessment in one sentence
Omnissa Horizon is the natural choice for VMware shops — anyone with an existing vSphere estate gets in Horizon a technically mature DaaS platform on that foundation. For cloud-first organisations without a vSphere history, AVD plus Nerdio or Citrix DaaS is usually the more economical choice.
Technical deep dive
Instant Clones: Horizon uses instant clones early and throughout — VMs are created within seconds, by default directly from a replica VM without a parent VM, and without a reboot. For pooled desktops with high turnover (shift scenarios, educational institutions, kiosk environments) that is a real speed advantage. Combined with App Volumes for applications without an image rebuild, and DEM for the user environment, it makes a mature stack.
The Omnissa spin-off: In late 2023 and early 2024, VMware’s EUC division (Horizon, Workspace ONE, Dynamic Environment Manager) was sold to KKR and spun off as the independent company Omnissa. Since April 2024 the products have officially been called Omnissa Horizon, Omnissa Workspace ONE and so on. Technically little changes; organisationally a great deal: new licence portals, new support structures, new pricing models. Existing customers should actively renegotiate terms after the transition.
Horizon 9 Cloud-Native as the future: Omnissa has announced Horizon 9 as a cloud-native architecture — microservice-based, container-orchestrated, without the classic connection servers. That would resolve many current pain points (multi-pod complexity, update effort, legacy architecture). No release date is official yet. Until then, Horizon 8 with the Cloud Pod Architecture remains the production standard.
When Horizon is the right choice: An existing vSphere or vSAN estate (particularly vSphere Foundation or VCF). Workspace ONE already in use for UEM. Linux desktops as a hard requirement. Nutanix shops looking for a VDI option. If none of these applies and there is no VMware context, AVD plus Nerdio or Citrix DaaS is usually more economical.
Which Horizon configuration fits your organisation?
The feature set is one side of the coin — the fit with personas, compliance and the existing IT estate is the other. Compare directly in DaaS Maps, or discuss it on LinkedIn.
The terminology behind Omnissa Horizon.
VDI, PCoIP, gold image — assessing the feature set means knowing the terms behind it. Each one is explained in a few sentences in the glossary.
Trademarks: Omnissa®, Horizon®, Workspace ONE®, Blast Extreme® · VMware® (Legacy) · IGEL® · Unicon® — and all other product and company names mentioned are registered trademarks of their respective owners and are named here solely for factual comparison, as nominative use.