Omnissa Horizon
Omnissa Horizon is a family of virtualization products that securely delivers virtual desktops and applications across on-premises, hybrid, and multi-cloud environments, supporting flexible deployment models such as virtual desktop infrastructure (VDI) and desktop-as-a-service (DaaS).[1] Developed to empower hybrid workforces, it provides consistent user experiences on any device while centralizing data management and enhancing security through features like end-to-end encryption and adaptive protocols that adjust to network conditions.[2] The platform includes core offerings like Horizon 8 for robust on-premises and cloud delivery, Horizon Cloud Service for managed infrastructure with automation, and integrated tools such as App Volumes for application layering and Dynamic Environment Manager for user personalization.[1] Originally launched as VMware Horizon in the early 2010s, the product evolved from VMware's desktop virtualization solutions to support modern architectures amid growing demands for remote work.[3] In 2024, following Broadcom's acquisition of VMware, the end-user computing division was spun off into an independent company named Omnissa, which rebranded the product line to Omnissa Horizon to reflect its new standalone identity and focus on innovation in digital workspaces.[4] This transition, completed in releases like Horizon 8 2412, updated branding across software, documentation, and endpoints while maintaining backward compatibility for existing deployments.[5] Key features of Omnissa Horizon emphasize scalability, security, and efficiency, including support for Windows and Linux operating systems, multi-session capabilities for Windows 10/11, and integration with Omnissa Workspace ONE for unified endpoint management.[2] It enables organizations to optimize resource allocation with power management, streamline IT operations through centralized patching and access controls, and ensure compliance by keeping sensitive data off end-user devices.[1] Available in subscription-based models like SaaS and term editions, the platform caters to varying needs, from single-site private clouds to global multi-cloud strategies, delivering cost savings and improved return on investment for enterprises.[2]History
Origins and Development at VMware
Omnissa Horizon originated from VMware's early efforts in virtual desktop infrastructure (VDI), beginning with the acquisition of Propero Technologies in April 2007 for approximately $25 million. Propero had developed a connection broker technology essential for managing access to centralized virtual desktops, which VMware integrated into its initial VDI offering. This acquisition laid the foundation for server-based computing solutions focused on delivering virtual desktops to end-users.[6] The product debuted as VMware Virtual Desktop Manager (VDM) version 2.0 in January 2008, providing a scalable connection broker for provisioning and managing virtual desktops on VMware Infrastructure. Later that year, in December 2008, VMware released version 3.0 and rebranded the solution as VMware View, emphasizing improved remote access capabilities through enhanced protocols like RDP. View 4.0 followed in November 2009, introducing the PCoIP display protocol developed by Teradici, which VMware had licensed to enable high-performance remote desktop delivery with features such as USB redirection and multi-monitor support.[7][8] VMware View 5.0 launched in September 2011, unifying desktop and application delivery with features like View Composer for linked-clone management and improved scalability for large deployments. The product evolved into VMware Horizon with version 6.0 in June 2014 (build 6.0.0), integrating support for Remote Desktop Services Hosted (RDSH) sessions to enable published applications and multi-session desktops alongside full virtual desktops. A key milestone came in February 2014 when VMware acquired AirWatch for $1.54 billion, bolstering endpoint management capabilities that later influenced Horizon's mobile and security integrations through the Workspace ONE platform. Horizon 7.0 arrived in March 2016 (build 7.0.0), enhancing the Blast Extreme protocol for adaptive multimedia and real-time audio-video optimization, while expanding mobile device support across iOS, Android, and other platforms.[9][10][11][12] Horizon 8.0 (build 2006) was released on August 11, 2020, introducing hybrid cloud capabilities that allowed seamless integration with public clouds like Microsoft Azure for workload bursting and unified management across on-premises and cloud environments. This version emphasized subscription-based licensing and enhanced scalability for remote work scenarios. Development continued under VMware until 2023, with incremental updates focusing on security and performance. In 2024, as part of Broadcom's spin-off of VMware's end-user computing business, the product transitioned to Omnissa, rebranded as Omnissa Horizon while maintaining its core architecture.[13]Rebranding to Omnissa
In November 2023, Broadcom completed its acquisition of VMware, integrating the company into its portfolio and prompting subsequent restructuring of VMware's divisions.[14] This led to the announcement on February 26, 2024, that global investment firm KKR would acquire VMware's End-User Computing (EUC) division, positioning it as an independent entity focused on digital workspace solutions.[15] On April 25, 2024, the EUC division was officially rebranded as Omnissa (pronounced "ahm-NISS-uh"), reflecting a vision of comprehensive empowerment in end-user computing.[16] The rebranding emphasized continuity for existing products while establishing Omnissa as a standalone software company, with the acquisition closing and operations launching independently on July 1, 2024.[17] Despite the corporate changes, Omnissa retained the Horizon branding for its core virtual desktop and application delivery product line, ensuring seamless support for integrations with vSphere and vSAN.[18] This decision preserved compatibility for on-premises deployments without requiring immediate migrations, allowing customers to maintain their existing VMware-based infrastructures.[18] Under Omnissa's ownership, Horizon's development continued with a strategic emphasis on empowering digital workspaces through enhanced multi-cloud Desktop-as-a-Service (DaaS) capabilities, aiming to unify endpoint management, application delivery, and user experiences across hybrid environments.[19] Omnissa's initial product releases under the new branding included Horizon 8 2412 on January 28, 2025, which introduced updates for greater control in virtual desktops and apps, alongside cloud-first enhancements to support flexible deployments.[20] This was followed by Horizon 8 2506 on July 31, 2025, featuring improvements in performance, security, and productivity tools to bolster multi-cloud DaaS without disrupting legacy setups.[20] These releases marked Omnissa's commitment to innovation in VDI and DaaS while honoring the product's historical roots in VMware View.[21]Technical Architecture
Core Components
The core components of Omnissa Horizon form the foundational architecture for delivering virtual desktops and applications, enabling secure and scalable access through a combination of servers, agents, and management tools.[22] These elements work together to handle user authentication, resource provisioning, session brokering, and protocol communication, supporting deployments in both on-premises and cloud environments.[3] The Horizon Connection Server serves as the central broker in the Horizon architecture, responsible for user authentication, resource allocation, and session management.[23] It authenticates incoming connections from clients, enumerates available desktops and applications, and directs users to the appropriate virtual resources while maintaining session state across the environment.[3] Multiple Connection Servers can be deployed in a pod configuration to ensure high availability and load distribution, preventing single points of failure through replication and failover mechanisms.[22] The Horizon Agent is installed on the guest operating system of virtual desktops or Remote Desktop Services (RDS) hosts, facilitating communication between the end-user device and the Connection Server.[24] It enables key protocol interactions, such as the Blast Extreme display protocol for multimedia acceleration and PCoIP for high-performance remote access, while also supporting features like USB redirection and multi-monitor handling.[3] This agent ensures that virtual resources remain manageable and responsive to user sessions initiated via the Connection Server.[22] Supporting tools enhance provisioning and application delivery within the Horizon ecosystem. Horizon Composer manages linked-clone technology, allowing efficient creation of multiple desktop instances from a single golden image by linking clones to a shared parent virtual machine, which optimizes storage and simplifies updates.[22] Instant Clone technology builds on this by enabling rapid, just-in-time provisioning of full-clone desktops through VM duplication and customization, reducing deployment times and improving scalability for large user pools.[3] Additionally, App Volumes provides application layering by delivering apps via assignable virtual disks, decoupling them from the base operating system for dynamic attachment and easier management across desktops.[25] Database integration underpins configuration and data persistence in Horizon. The embedded ADAM (Active Directory Application Mode) database handles local configuration storage for individual Connection Servers, including user entitlements and resource pools.[22] For larger-scale deployments, an external SQL database is used to store events, performance metrics, and pod federation data, enabling centralized management and scalability across multiple sites.[3] The Unified Access Gateway (UAG) acts as a secure edge service for external access to Horizon resources, functioning as a reverse proxy typically deployed in the DMZ to handle authentication and load balancing without exposing internal Connection Servers. It supports high availability through clustering and integrates with identity providers for zero-trust access, ensuring encrypted tunnels for remote users while mitigating external threats.[22]Deployment Models
Omnissa Horizon supports multiple deployment models to accommodate varying organizational needs, ranging from traditional on-premises setups to hybrid and fully cloud-based environments. The on-premises model leverages VMware vSphere infrastructure for complete control over virtual desktops and applications within enterprise data centers, enabling administrators to manage all components locally. This approach is ideal for organizations requiring strict data sovereignty and customization.[26] For scalability in on-premises deployments, Horizon uses pods—logical groupings of resources including Connection Servers, vCenter Servers, and desktop pools—that can support up to 20,000 sessions per pod. Multi-site scaling is achieved through Cloud Pod Architecture (CPA), which federates multiple pods into a global entitlement layer, allowing up to 250,000 concurrent sessions across sites while maintaining centralized user management. High availability is ensured by deploying replicated Connection Servers, with up to seven per pod for redundancy and load balancing to handle failures without service disruption.[26] Hybrid cloud options extend on-premises Horizon environments by integrating with public clouds such as AWS, Azure, or Google Cloud, facilitating workload bursting during peak demand or gradual migration of desktops. This model employs remote agents to connect cloud-hosted virtual machines to the on-premises Connection Server, supporting up to 1,000 remote desktops per agent for flexible resource allocation.[26] The full cloud deployment is provided through Horizon Cloud Service – next-gen, a Desktop-as-a-Service (DaaS) offering that utilizes a multi-cloud control plane for unified management across providers. It incorporates Thin Edge Infrastructure, consisting of lightweight Edge Gateways and Unified Access Gateways deployed at customer sites, to deliver virtual desktops and applications with minimal on-premises footprint. A single Horizon Edge can scale to 20,000 virtual machines on Azure or 5,000 on AWS, enabling efficient multi-cloud operations.[27] Migration paths from legacy VMware View to Horizon 8 support zero-downtime upgrades, allowing in-place enhancements to Connection Servers and other components without interrupting user sessions, thus facilitating a smooth transition to modern features.[26]Features
Virtualization Capabilities
Omnissa Horizon provides a virtual desktop infrastructure (VDI) that supports both persistent and non-persistent desktops to deliver flexible virtual workspaces. Persistent desktops maintain user-specific configurations and data across sessions, while non-persistent desktops reset to a baseline state after each use, enabling efficient resource sharing. For persistent desktops, Horizon utilizes full clones, which create independent copies of a golden image virtual machine, ensuring complete isolation and customization for each user.[28] Non-persistent desktops leverage instant clones, a technology that rapidly provisions VMs from a parent snapshot in seconds, replacing the legacy linked clone method for improved scalability and reduced storage needs.[29] Linked clones, originally used for non-persistent desktops in earlier versions, are supported in a salvaged mode for migration purposes but are deprecated in favor of instant clones.[30] As of Horizon 8 2506 (August 2025), virtualization capabilities include support for VMware Cloud Foundation 9.0 and vSphere 9, enabling deployments on updated infrastructure. Limited availability support for Nutanix AHV hypervisor adds power management, vGPU, App Volumes, Dynamic Environment Manager, and Cloud Pod Architecture. Improved session density is achieved with the default Indirect Display Driver (IDD), which enhances performance for hardware GPUs and software rasterizers. Earlier, Horizon 8 2503 (May 2025) introduced support for Windows Server 2025 on Connection Servers, Amazon WorkSpaces Core G4DN instances for automated pools, and screen sharing via Browser Content Redirection on Linux clients.[31][32] Application virtualization in Horizon enables the delivery of individual applications without requiring a full desktop session. This is achieved through Remote Desktop Session Host (RDSH) hosting, where multiple users share a single server to run applications, and Horizon Published Applications, which stream remote apps seamlessly to end-user devices.[33] Published applications run on RDS farms—groups of RDS hosts—and support features like on-demand delivery, allowing apps to be dynamically attached during user sessions for optimized performance.[34] This approach facilitates centralized application management and reduces endpoint resource demands by transmitting only the app interface over the network.[35] Horizon supports multiple display protocols to optimize remote access based on network conditions and use cases. The primary protocol, Blast Extreme, delivers high-quality multimedia, including 4K resolution, HDR, and adaptive audio, while adapting to varying bandwidth for smooth performance.[36] For low-latency scenarios such as CAD or financial applications, PCoIP provides pixel-level compression and efficient handling of graphics-intensive workloads; support for PCoIP ends after the extended service branch release at the end of 2025, with extended maintenance through 2028 for qualifying users.[37][38] Additionally, HTML5 access via the Horizon Web Client enables browser-based connectivity using Blast Extreme, eliminating the need for dedicated client software.[39] Provisioning in Horizon emphasizes efficiency through just-in-time desktop creation, where instant clones are generated on demand to match user sessions, minimizing idle resources.[3] Automated power management schedules VM power states based on usage patterns, powering down unused desktops to cut energy and hardware costs, while resource optimization features like storage tiering and CPU/memory balancing further reduce operational expenses.[3] These capabilities support scalable deployments across on-premises and cloud environments.[2] Horizon integrates with Dynamic Environment Manager (DEM) to handle user personalization and profile management, ensuring consistent experiences in virtual sessions. DEM captures and applies user profiles, settings, and policies dynamically at login, supporting both persistent and non-persistent desktops without relying on traditional roaming profiles.[40] This integration allows for features like application configuration and privilege elevation, enhancing usability while maintaining central control.[41]Security and Management Tools
Omnissa Horizon incorporates robust authentication mechanisms to secure user access, including multi-factor authentication (MFA) integration with providers such as RSA SecurID and RADIUS-based solutions.[42] These integrations allow administrators to enable two-factor authentication directly in the Horizon Console by configuring Connection Server instances, supporting modes like New PIN and Next Token Code for enhanced verification.[43] Additionally, Horizon provides an open standard extension interface for third-party authentication providers, enabling flexible deployment of advanced MFA options without requiring VPNs.[42] In Horizon 8 2503, adaptive authentication and network policies were added at the pool level, supporting SAML and RADIUS via API, along with native SAML support on Connection Servers for third-party identity providers. Horizon 8 2506 introduced combined x.509 and SAML authentication in the Unified Access Gateway for stronger multi-factor security.[32][31] True SSO facilitates passwordless access by allowing users to authenticate once via smart card, RSA SecurID, RADIUS, or a third-party identity provider through the Unified Access Gateway, eliminating the need to enter Active Directory credentials for virtual desktops or applications.[44] This feature, which requires integration with Workspace ONE Access, generates user-specific certificates from an enterprise certificate authority and supports both Horizon Client and HTML Access connections, though it is limited to IPv4 environments and incompatible with certain direct-connection plugins.[44] For zero-trust network access, the Unified Access Gateway serves as a hardened Linux-based virtual appliance that proxies secure remote connections to Horizon resources, enforcing TLS encryption and role-based access controls to protect against unauthorized entry.[45] Data security in Horizon emphasizes centralized storage of resources within the data center or cloud, ensuring no persistent data resides on end-user devices to minimize exposure risks.[46] Sessions are protected with end-to-end encryption using TLS 1.2 or higher (with TLS 1.3 preferred since Horizon 8 2312.1) for data in transit and AES-256 for data at rest, including customer-managed virtual desktops and stored credentials. Horizon 8 2503 added ChaCha20 cipher suites for enhanced encryption and performance. Automated TLS certificate renewal for Blast, introduced in 2506, reduces administrative overhead by auto-renewing self-signed certificates.[46][47][32][31] Compliance features support standards such as HIPAA and GDPR through per-tenant data isolation, annual third-party audits, and alignment with frameworks like ISO 27001 and NIST SP 800-53, enabling organizations to meet regulatory requirements for protected health information and personal data handling.[46] The Horizon Console provides a web-based interface for centralized management, enabling administrators to monitor system performance, generate usage reports, and enforce access policies across desktops and applications.[48] Built-in monitoring for Unified Access Gateways and Connection Servers was added in Horizon 8 2503. It integrates with Workspace ONE for unified endpoint management, allowing automated enrollment of persistent VDI desktops, software deployment, compliance profiling, and real-time support via features like Intelligent Hub and Intelligence reporting.[32][49] This integration supports OS updates, baseline enforcement, and performance analytics on platforms including vSphere and Azure, using staging accounts for pre-enrollment before user assignment.[49] Automated agent upgrades for Dynamic Environment Manager and App Volumes, introduced in 2506, ensure secure and up-to-date desktops. Horizon 8 2503 also added SMB file share support for Connection Server lifecycle management and dynamic user assignment for remote access on physical PCs.[31][32] For tunneled connections, the Blast Secure Gateway ensures that only authenticated traffic reaches internal resources, leveraging TLS certificates to validate sessions and block unauthorized access from external networks.[50] It works in conjunction with the Unified Access Gateway to support Horizon Blast Extreme protocol, allowing secure remote access without exposing the data center directly to the internet.[50] To prevent resource contention, anti-affinity rules can be configured in the Horizon Console for application pools, specifying matching patterns (e.g., executable names) and maximum instance counts per RDS host to distribute workloads and avoid overloading individual servers.[51] Auditing and logging capabilities include comprehensive event tracking via the Horizon Console's Activity Logs, which capture administrator and end-user actions for compliance and troubleshooting.[52] Events can be logged to local files (up to 300 MB), UNC shares, or syslog servers in Syslog format, with options for always-on, error-only, or disabled logging configured through the UI or command-line tools.[53] An events database stores operational data for analysis, supporting integration with analytics software while maintaining security through IPsec recommendations for syslog transmission.[53]Client and Access
Horizon Client
The Omnissa Horizon Client is a downloadable software application that enables end-users to access virtual desktops and published applications from Omnissa Horizon environments. It is available across multiple platforms, including Windows, macOS, Linux, iOS, Android, and Chrome OS, providing a consistent user experience on desktops, laptops, tablets, and mobile devices. For scenarios where a native client is not feasible, an HTML5-based fallback option allows browser access without installation. Key functionalities of the Horizon Client include support for multi-monitor configurations, enabling up to six 4K displays when using the Blast display protocol on compatible Windows agents. USB redirection allows local peripherals, such as storage devices or input hardware, to be seamlessly accessed within remote sessions, with support for multiple devices sharing the same vendor and product IDs in multi-user environments. Multimedia acceleration is provided through Multimedia Redirection (MMR), which offloads decoding of video and audio streams to the client device, reducing server load and improving playback performance for applications like streaming media. Additionally, the Blast protocol incorporates adaptive capabilities to optimize bandwidth usage across varying network conditions, such as adjusting quality based on latency and throughput to maintain session stability.[54][55][56][57] Installation of the Horizon Client typically involves downloading the platform-specific installer from the official Omnissa Customer Connect portal and running it with administrator privileges, with options for typical or custom setups that include IPv6 support and FIPS compliance. Configuration features encompass auto-update mechanisms to ensure the client remains current with security patches and enhancements, smart card authentication requiring compatible hardware and certificates for secure logins, and relative mouse support that uses coordinate-relative movements to enhance precision in CAD and graphics applications. These settings can be managed via client menus, group policy templates, or command-line options during deployment.[58][59][60][61] In version 2503 of the Horizon Client, enhancements include asynchronous bandwidth estimation now available on macOS and Linux clients, optimizing bandwidth usage and improving session stability. As of November 2025, the latest version is 2506, which includes further performance improvements; see the Versions section for details.[62][63] Common troubleshooting for the Horizon Client involves addressing protocol selection issues, where users can manually switch between Blast and PCoIP via client settings if automatic detection fails due to network constraints. Certificate handling problems, such as invalid or expired SSL certificates during connection to the Horizon Connection Server, can be resolved by adjusting the certificate checking mode in client security settings to warn or bypass for trusted environments, or by verifying and updating server-side certificates. Restarting sessions, resetting desktops, or reinstalling the client often resolves connectivity glitches, with logs accessible for deeper diagnostics.[64][65][66][67]Alternative Access Methods
Omnissa Horizon supports access through an HTML5 web client, enabling users to connect to virtual desktops and published applications directly from a compatible web browser without installing dedicated software. This browser-based method leverages the Blast display protocol for rendering sessions and is accessible via a Horizon Connection Server URL, providing a lightweight alternative for environments where client installation is restricted or impractical.[68][69] Zero clients and thin clients offer hardware-optimized endpoints for secure Horizon access, integrating Omnissa Horizon Client binaries into specialized devices from certified partners such as 10ZiG, HP, and legacy Teradici (now HP Anyware) hardware. These devices support protocols like Blast and provide managed, low-maintenance access points with enhanced security features, including restricted local processing to minimize attack surfaces. Compatibility is ensured through Omnissa's certification program, covering x86, x64, and ARM architectures for Horizon 8 and later versions.[70][71][72] For mobile scenarios, Horizon integrates with Omnissa Workspace ONE to deliver access to virtual desktops on smartphones and tablets via the Workspace ONE Intelligent Hub app, supporting bring-your-own-device (BYOD) policies with configurable security and single sign-on (SSO). This setup allows optional or required enrollment based on app sensitivity, enabling kiosk mode for restricted, single-purpose device usage in enterprise environments.[73][74] External access to Horizon resources can be achieved without traditional VPNs using the Unified Access Gateway (UAG), a virtual appliance that serves as a secure edge gateway over TCP port 443 for HTTPS traffic. UAG enforces user entitlements, optimizes performance for protocols like Blast and WebSocket, and eliminates the need for separate VPN authentication or software installation.[75][76] While these methods provide flexible, install-free or hardware-centric access, they have limitations compared to the full-featured Horizon Client, such as the absence of USB redirection in the HTML5 web client due to browser constraints. Best practices include optimizing network bandwidth and latency for web and mobile sessions to ensure smooth Blast protocol performance, as well as performing regular firmware updates on zero and thin clients to maintain compatibility and security through Omnissa's certification processes.[77][78][70]Versions
Major Releases
The Omnissa Horizon 7 series, launched in March 2016, marked a significant evolution in desktop and application virtualization, spanning versions from 7.0 to 7.13.3 through 2020.[12] This series introduced key innovations such as the Just-in-Time Management Platform (JMP) in version 7.1, which enabled automated image management and provisioning for optimized desktop delivery.[79] Subsequent updates, including 7.5 in May 2018, enhanced integrated platform capabilities like support for VMware Cloud on AWS and improved JMP workflows.[80] General support for the entire Horizon 7 series concluded on April 30, 2023.[81] The Horizon 8 series, introduced in August 2020 with version 2006 (also referred to as 8.0), shifted toward hybrid and multi-cloud architectures, supporting deployments on Azure VMware Solution for seamless on-premises to cloud transitions.[13][82] Key milestones include version 2206 in August 2022, which expanded Linux desktop support to include Ubuntu 22.04 and Red Hat Enterprise Linux 8.6.[83] The series continues with ongoing releases, such as 2506 in August 2025, featuring enhancements for security, management, and integration with VMware Cloud Foundation 9.0 and vSphere 9.[21] A maintenance update, 2506.1, was released later in 2025, providing critical bug fixes and security patches.[63] Notable updates like version 2503 (8.15) in April 2025 further broadened Linux guest OS compatibility and added efficiency improvements for virtual environments.[84] Omnissa Horizon follows a quarterly release cadence for major updates, typically aligned with a YYMM naming convention—such as 2412 (December 2024, generally available in early 2025) and 2503 (March 2025, available April 2025)—to deliver incremental features, security enhancements, and compatibility updates.[85][86] Build numbers follow a format like 8.x.x-YYYYMMDDxxxx, exemplified by releases such as 8.15.0-16904936221 for 2503.[20] Under Omnissa's support policy, Extended Service Branch (ESB) releases receive 3 years (36 months) of general support, followed by technical guidance for critical patches and migration assistance.[84] Notable patches emphasize security fixes and feature packs; for instance, version 8.15 includes expanded support for Linux distributions, while interim updates address vulnerabilities and operational stability across the series.[84] Client compatibility is maintained across major server releases, with Horizon 8 supporting clients from version 2006 onward for interoperability.[87]| Release Series | Key Versions and Dates | Notable Features/Changes | End of General Support |
|---|---|---|---|
| Horizon 7 (2016–2020) | 7.0 (Mar 2016); 7.1 (Mar 2017); 7.5 (May 2018); 7.13 (Oct 2020) | JMP introduction (7.1); AWS integration (7.5) | Apr 30, 2023[81] |
| Horizon 8 (2020–present) | 2006/8.0 (Aug 2020); 2206/8.x (Aug 2022); 2503/8.15 (Apr 2025); 2506/8.16 (Aug 2025) | Azure VMware Solution support (2006); Linux expansions (2206, 8.15); VCF 9.0 integration (2506) | Varies by release; e.g., 2006: Aug 2025[88] |