The Horizon 8 2512 release brings updates that elevate the end-user experience and give IT more flexibility in how they deploy and manage Horizon. You’ll see deeper Workspace ONE UEM integration, expanded hybrid cloud capabilities, stronger protocol performance, broader platform support, and improvements across management and security. No matter your priorities, this release delivers advancements that make Horizon easier to operate at scale.
Horizon 8 support on Nutanix AHV is now generally available (GA), giving organizations more flexibility in how they deploy and manage their virtual desktops and apps. This GA release brings a full set of production-ready capabilities, including automated provisioning and power management of Desktop Pools and Farms through Prism Central, AHV-native UAG appliance for secure access, and a simplified pool model using Redirect-on-Write cloning for fast, space-efficient provisioning. Horizon also adds built-in image customization via Horizon-managed ClonePrep and Sysprep, and reusable compute profiles for consistent desktop deployments. And with support for Nutanix NC2 on Azure, and Google Cloud, customers can manage on-premises and cloud environments from a single Horizon console. Learn more about this solution in the Horizon 8 on Nutanix AHV blog.
A newly redesigned Omnissa Horizon Client for Windows, Mac, and Linux delivers a consistent, modern experience across every device. The updated interface brings all desktops, apps, settings, and in-session controls into a unified layout, making it easier for users to move between platforms without retraining or relearning where things live. Features like folders, favorites, and streamlined settings help users stay organized and productive, while all the enterprise capabilities you rely on remain fully supported. You can explore the full walkthrough and migration details as well as a product demo in Omnissa Horizon client preview blog.
A unified Horizon Client interface across Windows, Linux, and Mac delivers a consistent, modern experience on every device.
Horizon 8 now integrates directly with Workspace ONE UEM, extending the same unified management approach that’s already available with Horizon Cloud. This capability allows IT admins to manage their physical devices and virtual desktops from one place. It simplifies daily operations and helps lower overall costs by centralizing policies, updates, apps, and security controls. UEM automatically enrolls Horizon 8 desktops across capacity providers, including vSphere, Amazon WorkSpaces Core, and Nutanix AHV, giving IT a consistent way to manage every system as soon as it’s provisioned. The result is a single, cohesive management experience across the entire digital workspace.
In this section, we’re highlighting the updates that focus on the day-to-day experience in Horizon. This release includes a set of enhancements across Blast, the Horizon client, and the Horizon agent, each designed to strengthen performance, responsiveness, and usability in everyday workflows.
Horizon now supports the NVIDIA Blackwell RTX Pro 6000 GPUs. That means organizations using Horizon for virtual desktops or virtual GPU (vGPU) deployments can now tap into the massive performance Blackwell offers. The RTX PRO 6000 Blackwell is built on the next-gen Blackwell architecture, with — among other specs — up to 96 GB GDDR7 memory and powerful AI/graphics engines designed for demanding AI, rendering, 3D, and scientific workloads. By combining Horizon’s management and virtualization capabilities with Blackwell’s raw GPU power, enterprises can deliver high-performance virtual desktops or virtual workstations, scale AI workloads, and support compute-heavy applications securely and efficiently.
Blast will support NVIDIA’s latest SDK 13, bringing noticeable improvements to graphics quality, efficiency, and professional media workflows. This upgrade helps teams get clearer visuals at lower bandwidth, work with richer color formats, benefit from higher-precision encoding, and support interlaced and AV1 ultra-high-quality modes. It also improves handling of 3D and stereoscopic content, making it easier to support specialized media and design use cases.
Horizon has implemented support for Virtual Channel (VVC) Raw Channels for Blast mouse, keyboard, screen data (MKS), and audio. These high-volume inputs move off the shared path and onto their own dedicated socket connection, which reduces overhead, cuts bandwidth use, and lowers latency. It also helps prevent MKS traffic from competing with other features on standard VVC channels, improving host density and reducing CPU usage. Support now extends across Windows, Linux, Mac, and mobile clients. We’ve also added Blast Secure Gateway (BSG) awareness for these channels so they flow correctly when a BSG is in the path, ensuring consistent performance across all deployment architectures.
This update adds reverse connection support for BEAT, allowing the Horizon agent to initiate a UDP-based connection back toward the client. It builds on the existing TCP reverse connection work and extends the same flexibility to BEAT, including scenarios that involve physical PCs. This helps Horizon connect reliably in environments with strict inbound firewall rules, making it easier to support a wider range of enterprise networks and deployment models.
Blast now uses truly intelligent, dynamic transport switching between TCP and BENIT, adjusting in real time as network conditions change. Instead of relying on a single transport choice, Blast continually evaluates bandwidth, latency, and overall connection quality to select the most efficient path. This gives users a smoother, more reliable experience and helps maintain the best possible performance under any network conditions.
We are improving the Teams experience when using Horizon by adding noise suppression, which filters out unwanted background sounds during video and audio calls. This makes conversations clearer and more natural, especially in busy or shared work environments, and brings a more polished calling experience to optimized Teams sessions. Additional enhancements also include being able to use the Zoom In feature with Teams optimization for a better experience.
The new Teams Slimcore aka VDI 2.0 is now available for Horizon Windows clients as part of Microsoft’s TAP program and will soon be available as part of Microsoft’s tech preview program. The new Teams optimization (VDI 2.0) brings with it an enhanced feature set, improved audio/video quality, streamlined updates and direct support from Microsoft.
Clipboard redirection is being enhanced to better support large data transfers and maintain a consistent experience when working with big files like large Excel datasets. A new GPO option raises the clipboard limit beyond the previous 16 MB cap, now supporting transfers up to 4GB. Horizon also improves how formatting is preserved with larger payloads, preventing rich data from being reduced to plain text during copy-and-paste. Along with optimizing performance during heavy transfers and better handling when large operations take time, these updates deliver faster, more reliable, and more consistent clipboard behavior.
With this release, Horizon supports multi-monitor configurations in nested mode for both Windows and Linux. This includes mixed portrait and landscape setups, giving users more flexibility to arrange their workspace the way they want. The update delivers a consistent and reliable multi-monitor experience in nested mode, even in more complex desktop layouts.
Linux distributions are steadily moving from X11 to Wayland, and we’re preparing the Horizon client for that shift. In 2512, we’re adding an XWayland compatibility layer, which allows X11-based Horizon apps to run smoothly in Wayland environments. This gives organizations a reliable bridge as the ecosystem transitions. Full native Wayland support is planned for a future release, but this update ensures Horizon continues to work well across current and emerging Linux distributions as teams adopt newer desktop environments.
WebAuthn can now be used inside UWP apps running in the virtual desktop, including apps like the new Outlook experience. This lets users authenticate with FIDO2 security keys and other modern methods directly in the app, without relying on USB device forwarding. It creates a smoother, more secure sign-in experience as more Windows apps move to the UWP model.
The Windows client now supports SPNEGO and Kerberos for proxy connections, providing a more secure alternative to deprecated NTLM. By adopting this modern authentication method, Horizon improves the security of environments that rely on proxy connectivity in Windows clients.
This release adds support for single sign-on into pre-created Azure desktops and applications that are joined to Entra ID, using Horizon 8 together with Omnissa Access. End users authenticate through Omnissa Access and can launch their Horizon desktops and applications without needing to re-enter credentials inside the session. This streamlines access for environments built on Entra ID and gives on-prem organizations a smoother path when delivering Azure-based Horizon resources.
Launch Azure-based Horizon resources joined to Entra ID without re-entering credentials.
This update removes the need to include admin usernames and passwords when installing the Horizon Agent on unmanaged or pre-provisioned desktops including Physical machines. Instead of embedding sensitive credentials in the installation package or command line, organizations can use a secure, credential-free method to pair these machines with Horizon. This makes it safer and easier to bring native cloud VMs or physical PCs under Horizon management without changing how those systems are built or provisioned.
Agent Auto-Update now supports using UNC paths on standard file shares as the source for Horizon agent packages. Admins can host the agent files on their own SMB shares, whether open or access-restricted, and point Horizon to that location for upgrades. This gives organizations more control over where agent binaries are stored and makes it easier to manage updates in environments that prefer internal file shares over URLs.
This release adds broader Windows OS coverage in the Horizon agent. We’ve updated our OS Optimization Tool (OSOT) plugin for the Microsoft Deployment Toolkit (MDT), which many customers use to build and deploy their Windows images at scale. The plugin now supports Windows 11 24H2, helping teams keep their imaging workflows consistent as they adopt newer versions. Microsoft is ending support for Windows 10 22H2 on October 14, 2025. Because of this, Horizon Agent and Client version 2603 (expected Q1 2026) will be the final release to support this OS. For more details on extending support, visit KB6001105.
Next we turn to the enhancements that strengthen how Horizon is managed, covering authentication, load balancing, routing logic, client controls, and agent updates across cloud providers.
SAML configuration can now be applied at the pod level, making it easier to manage authentication settings across all Connection Servers. Admins can define the method once and have it apply everywhere, while still enforcing re-authentication even when a SAML session is active, preventing unauthorized access and supporting compliance needs. The update also allows flexible IDP configuration per Connection Server when required. This capability reduces setup effort, strengthens security, and gives customers more control over how SAML behaves in their environment.
Horizon 8 now supports a zero-spare power-optimized hourly pool configuration on Amazon WorkSpaces Core. All desktops can be provisioned upfront and placed into a suspended state, waking only when a user requests a session. This eliminates the cost of keeping idle machines running, improves resource utilization, and gives customers on-demand scalability without maintaining an online buffer.
Horizon on Amazon WorkSpaces Core allows pools to run without idle spares, waking desktops on demand for more efficient scaling.
Agent Auto Update is now available for Horizon 8 desktops running on Amazon WorkSpaces Core, including automatic updates for persistent pools, farms and manual pools. With AAU, admins can roll out new agent versions for Horizon Agent, DEEM, DEM and App Volumes without manual touchpoints, keeping environments current with far less effort and maintaining consistent agent versions across deployments.
Horizon 8 now makes it easier to adjust load balancing settings for RDSH farms directly in the console. Admins can now enable or disable load index–based RDSH session load balancing for each farm individually, whereas previously this could only be configured at the pod level. Additionally, Horizon now more effectively adapts RDSH session load balancing within each farm, meaning more even load distribution in low usage as well as high usage scenarios. These expanded controls give IT a clearer way to shape how sessions are distributed across hosts, improving stability and delivering a more predictable user experience.
Cloud Pod Architecture (CPA) introduces a preferred site order that gives admins more control over how users are routed when their primary site reaches capacity. Rather than selecting another site at random, CPA follows the configured sequence to find the next available location. This creates more predictable routing, helps avoid unnecessary latency from misdirected sessions, and supports better load distribution across sites.
Horizon 8 adds new controls that let admins manage how users download client updates. Instead of only warning or blocking older clients, admins can now choose whether users receive the default download link, a custom URL, or no upgrade option at all. The result is a more predictable upgrade process and a smoother experience for users who need to stay on approved client versions. This capability is available for Windows and Mac clients.
Horizon 8 meets key WCAG 2.0 Level AA accessibility guidelines, helping organizations support users with a wider range of needs while meeting federal and international accessibility requirements. By strengthening our accessibility foundation, we’re making Horizon easier to adopt in regulated industries and more inclusive for all users.
Here are the features that expand Horizon’s hybrid cloud capabilities and give organizations a more unified way to run Horizon across clouds.
Universal Broker v2 brings Horizon 8 and Horizon Cloud together under a single brokering experience, giving users one URL for all their desktops and apps across Windows, Mac, Linux, and web clients. The service runs in the Horizon Control Plane and handles authentication and routing in the cloud, while the user’s session connects through the nearest Unified Access Gateway for the best possible performance. By removing the need for inter-pod networking, global load balancers, or complex site-to-site configurations, Universal Broker makes multi-site and multi-cloud deployments far easier to operate. It can route based on geography, capacity, or home-site policy and supports multi-cloud assignments that span Horizon 8 pods and Horizon Cloud capacity. The update also improves desktop launch reliability with support for multi-backend scenarios in Horizon Cloud, smarter retries when a pool has no available desktops, and consistent idle and logout timeout behavior across environments. The result is a consistent, scalable, and resilient access experience no matter where desktops or apps are hosted.
A single access point directs users to Horizon 8 or Horizon Cloud resources across sites, using the nearest gateway for optimal performance.
The Horizon Edge Gateway allows Horizon 8 environments running on vSphere, Nutanix, or native public clouds like Azure and AWS to connect with Horizon Cloud. This connection unlocks hybrid cloud capabilities by giving on-prem and cloud-hosted pods access to services in the Horizon Control Plane, including licensing, monitoring, DEX, image management, and Universal Broker. With high-availability support now added, the Gateway provides a more resilient path to Horizon Cloud and helps organizations manage distributed Horizon deployments through a single, cloud-based console.
Image Management Service (IMS) gives IT a single place to create, customize, and publish desktop and server images across Horizon 8, Azure, Amazon WorkSpaces Core, and Horizon vCenter. Teams can import a base image, layer in apps and configurations, publish new versions, and build pools from a consistent, centralized catalog. Version tracking makes updates easier to manage, and images can now replicate across Horizon edges using NFS, helping accelerate deployments in hybrid cloud environments. If you want to see how this comes together in practice, watch the demo.
Workspace ONE Assist is now integrated with Horizon Cloud and supported for Horizon 8 cloud-connected environments, giving admins a direct way to access and troubleshoot end-user VDI sessions from the Horizon Universal Console. This lets IT see exactly what the user is experiencing, resolve issues in real time, and restore productivity faster, all while keeping the session secure and contained within the Horizon environment.
This release continues the work of making Horizon easier to use, easier to manage, and easier to run in any environment. From a more intuitive client experience to deeper hybrid cloud integration, stronger protocol performance, and better tools for IT, Horizon 8 2512 gives teams more flexibility and more confidence in how they deliver virtual desktops and apps. This blog covers only a portion of what’s new. For a full list of everything included in the release, be sure to check out the Horizon 8 2512 release notes.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。