Omnissa Horizon 8 Release Notes

Horizon 8 2512 | 16 DEC 2025 Build: 8.17.0-20167542520

With Horizon 8, IT departments can run remote desktops and applications in the data center and deliver these desktops and applications to employees. End users gain a familiar, personalized environment accessible from any number of devices, anywhere within the enterprise or home. Administrators gain control, efficiency and security by centralizing data in the data center.

Important Notes

• The Horizon 2512 Agent is now supported with both the 2503 ESB Server and the 2512 Server versions. See Compatibility Matrix for Various Versions of Horizon 8 Components for more details.

• Horizon 8 is not supported with vSphere 6.5 or vSphere 6.7, which are both past the end of General Support. Horizon 8 Instant Clones are incompatible with vSphere 6.5 and vSphere 6.7 so you must upgrade to vSphere 7.0 or later before upgrading to Horizon 8 if you are using Instant Clones.

• For information about the combined offering of Omnissa Horizon with VMware vSphere Foundation for VDI, including licensing, packaging, and frequently asked questions, see KB article 6000381.

What's New

Support for Nutanix AHV

Horizon 8 support for Nutanix AHV is now generally available. This release also adds the following features to Horizon’s support for Nutanix AHV:

• Support for Automated RDSH Farms, including published applications and desktops
• App Volumes published apps on demand
• ClonePrep customization for Pools and Farms
• Sysprep profile management through Horizon Console
• Overlay network support
• VM Hosted Apps (published Apps against Nutanix single-session Desktop pools)
• Horizon in FIPS-enabled mode
• Horizon Recording
• Workspace ONE Intelligence Horizon monitoring
• Horizon Cloud Help Desk
• DEX for Horizon

Note: Customers upgrading from Horizon 8 2506 with Nutanix Limited Availability functionality enabled will need to upgrade Horizon Agents immediately after upgrading Horizon Connection Server, due to changes in communication between Server and Agents:

• Non-persistent pools: Upgrade (or create new) Golden Image with 2512 Agent, initiate a Push Image task to update the pool
• Persistent pools: Upgrade Horizon Agent from 2506 to 2512 on each deployed VM. Upgrade (or create new) Golden Image with 2512 Agent for future pool expansion.

Horizon Connection Server

• This release includes Workspace ONE Assist integration for Horizon 8 with Horizon Cloud-connected customers. Administrators can now initiate secure remote support sessions directly from the Horizon Cloud Universal Console to an active Horizon 8 VDI desktop. This enhancement streamlines troubleshooting, eliminates the need for third-party tools, and boosts support efficiency across all environments.

• This release enhances the Helpdesk REST API to return detailed log-on segment metrics in a structured format. The updated endpoint provides breakdowns for Authentication, Brokering, Protocol Connection, GPO Load, Logon Script, Profile Load, and Interactive Session. This enables you to better monitor, diagnose, and reduce VDI log-on delays.

• This release adds per-Pod SAML configuration in Horizon, allowing administrators to define SAML settings at the Pod level instead of for each individual Connection Server. This enhancement increases flexibility, supports tenant- or Pod-specific identity requirements, and maintains full backward compatibility. It also strengthens security, improves customization options, and better aligns with varied enterprise authentication needs. Additionally, this release now fully supports the use of special characters in Dynamic Metadata URLs.

• Starting with Horizon 8 2512, encrypted backup files are not recoverable by earlier installations once the data recovery password has been modified. When upgrading to 2512 or later, it is important to ensure that all Connection Servers in the pod or cluster are upgraded before changing the data recovery password.

• This release improves accessibility compliance in Horizon 8 Connection Server in alignment with DCSA and WCAG 2.0 standards. Enhancements address previously unmet guidelines to raise the VPAT compliance score above 50%. This work supports an inclusive user experience, ensures continued eligibility for federal use, and meets mandated requirements from the CIO and federal agencies.

• The installer now automatically transfers the Schema Master FSMO role to the local LDAP instance before uninstalling existing Connection Server services during an upgrade. This prevents upgrade failures that could otherwise leave the server unresponsive. If the Schema Master role cannot be transferred, the installer aborts safely and preserves the existing services, ensuring stability during parallel upgrades.

• Favicon health checks have been moved from Tomcat to a secure gateway, providing a more efficient process. Originally, /favicon.ico polling was being processed by Tomcat, which increased load during frequent health checks. By implementing this change, overall response times are faster, back-end load is reduced, and load balancers can now poll more frequently without the previous constraint of two balancers at 30-second intervals.

• Horizon 8 now supports the policy Access Based on User Location for Automated Desktop, Manual Desktop, RDS Desktop, and Application Pools. Administrators can configure settings for Internal Access (via Horizon Connection Server), External Access (via UAG), or both. For instance, bank users on the office network may access all banking applications, whereas those connecting from home have access to email only.

• This release enhances Horizon logging for client restrictions. New audit events are recorded in the Events DB and forwarded to Syslog for SIEM visibility. Logs capture client block/warn actions details with version, IP, policy, and reason metadata. Event types include version recommendations, unsupported clients, and certificate policy outcomes.

• The default lifetime of the vdm certificate is now set to 6 months. This change enhances security by requiring certificates to be renewed more frequently, reducing the risk associated with long-lived credentials. This update aligns with current industry trends favoring shorter certificate lifetimes.

• Added role-based access control (RBAC) feature to Horizon Recording, to help admins to configure who can access Horizon Recording Console and what tasks different user groups are authorized to perform. With role-based access control, you can create roles and selectively assign privileges and create permissions and access level to specific Active Directory user groups.

• This release adds support for Single Sign-On to Entra ID joined desktops and applications when the Windows client is launched using Omnissa Workspace ONE Access. Users authenticate through Omnissa Access and can launch their Horizon desktops and applications without needing to re-enter Entra ID credentials inside the desktop. This streamlines access for environments built on Entra ID and gives on-prem organizations a smoother path when delivering Azure-based Horizon resources. ​Awaiting Microsoft GA rollout (tentative: By end of Jan 2026). See SSO to Entra ID joined desktops and applications through Workspace ONE Access section in the Desktop and Applications Guide.

• Broker-Managed Client Upgrade: Horizon Connection Server now supports the management of client upgrades for Windows and Mac clients. Administrators can enforce version policies, host installer files for desktop clients, and prompt users to update when their client version is blocked.

• This release introduces the ability to Find Machines with the grid showing the assigned users of a particular group based on group ID. Filtering and sorting is not available across columns in the Find Machines grid for the REST API in the Users and Groups workflow.

Horizon Console

• Administrators can now disable/enable load index-based RDSH session load balancing at an RDSH Farm level through Horizon Console or Horizon REST API. Previously, administrators could only disable load index-based RDSH session load balancing at a Pod level via an ADAM DB change. Additionally, the RDSH session bucketing attributes now adapt as required to ensure an even load distribution during both low and high usage periods. See Load Balancing Settings for more details.

• This release introduces server-side column-level filtering and sorting support for grid views, replacing the previous global client-side filter. The enhanced REST API now enables accurate filtering and sorting across individual columns in workflows such as Machines and Inventory. This improves data clarity, usability, and consistency as more workflows transition to server-driven UI operations.

• Administrators can now select a vGPU profile directly in the Horizon console during Instant Clone desktop pool creation or push image workflows. Previously, vGPU profiles were inherited from snapshots. This enhancement adds a vGPU profile dropdown as part of the compute profile definition when creating an Instant Clone pool, or when preparing a push image operation. This allows a single vGPU golden image to be used with different pools whilst allowing for different vGPU profiles, and removes the need to update golden images just to change vGPU profile.

• Administrators can now enable Workspace ONE UEM management directly from the Horizon Console when creating persistent (dedicated) desktop pools. This enhancement extends Workspace ONE UEM across physical devices, mobile endpoints, and Horizon VDI, delivering a unified Day-2 management experience through a single console. The integration ensures consistent policy application from day one, simplifies operations, enhances compliance and security, and reduces total cost of ownership.

• Auto Agent Upgrade is now available with expanded agent source support. In addition to Omnissa-hosted CDS and full URLs, administrators can define a UNC path to use an SMB file share for agent delivery. The Horizon console allows downloading the agent, selecting the share, and configuring it as the upgrade source.

Horizon Agent for Linux

• Support for NVIDIA Blackwell GPUs: The Horizon Agent for Linux now supports NVIDIA Blackwell GPUs in all Linux distributions. This means that Linux VDI workloads can use the latest GPU architecture.

• This release includes the URL redirection feature for the Linux Agent. Now, URLs opened in the Omnissa Horizon Linux agent's browser can be redirected to open on the Omnissa Horizon client machine, based on user-configurable settings.

• Updated NVIDIA vGPU Support: Horizon Agent 2512 adds support for NVIDIA vGPU versions 16.12, 18.5, 19.3, and 19.4.

Horizon Agent for Windows

• Passwordless installation: Unmanaged agents can now be installed on domain-joined machines without Horizon Administrator credentials, using pre-allocation. The agent installer can also discover its pre-allocated pod or cluster.

• Horizon clients can now get and report their public IP addresses. The Horizon Agent for Windows now gets and reports the client machine's public IP address as part of the DEX telemetry. The Horizon Client DEEM plug-in obtains the public IP from the DEEM agent when a user connects to a remote session and forwards it to the agent, which then reports it to Workspace ONE Intelligence (INTEL/WS1). Administrators gain improved visibility into connection sources, helping them monitor user activity, respond to incidents, and maintain compliance requirements.

• Windows 10 End of Support: Microsoft ended mainstream support for Windows 10 in October 2025 and now offers Extended Security Updates (ESU). Horizon extends its support for Windows 10 from release 2512 through Agent 2603, but only when the operating system is covered by Microsoft ESU. For more information, see KB 6001105.

• Agent Auto Upgrade: Agent Auto Upgrade now includes pre-flight validation checks. If a pre-flight check fails, both the agent update and the VM update are marked as failed. Pre-flight checks include:

  • Insufficient disk space detection
  • Windows Update in-progress check
  • Pending reboot validation
  • Invalid or unreachable UNC path checks

• Support for NVIDIA Blackwell GPUs: The Horizon Agent for Windows now supports NVIDIA Blackwell GPUs on Windows 10, Windows 11, and Windows Server guest operating systems. This allows high-performance graphics workloads on the latest GPU generation.

• Horizon V2 Agent now supports the ability to run a post-customization script. Administrators can configure a script to run after the Agent has completed customization, including Azure AD join, on-prem AD join, hybrid join, Instant Clone domain join, and LCM "skip domain join" scenarios. This capability is controlled using new JSON configuration fields and registry values for execution and status tracking.

• Enhanced USB Redirection for RDS Hosts: The Horizon Agent for Windows (RDSH) now supports redirecting multiple USB devices that share the same Vendor ID (VID) and Product ID (PID). Previously, only a single device with a matching VID/PID pair could be redirected to a session. This enhancement allows environments using identical USB hardware (such as scanners, HID devices, or custom peripherals) to attach multiple instances simultaneously.

• Updated NVIDIA vGPU Support: Horizon Agent 2512 adds support for NVIDIA vGPU versions 16.12, 18.5, and 19.3.

• Windows 11 25H2 and Windows Server 2025 Support: Full support has been added for Windows 11 25H2 and Windows Server 2025, including Single-Session Desktops, Multi-Session Farms, and App Mode configurations. Support for Windows 11 22H2 has ended.

Horizon 8 on Amazon WorkSpaces Core

• Provisioning operations have been enhanced to deliver significantly faster pool creation times. In some cases, provisioning time has been reduced by as much as 60%, improving efficiency and scalability. See KB 600123 for additional information.

• Agent Auto Upgrade for Horizon 8 on Amazon WorkSpaces Core dedicated pools is now supported. This feature allows administrators to automatically update the Horizon agents on WorkSpaces instances. The WorkSpaces instances need to be in the available state to use this feature. See Auto Upgrade Horizon Agent for more information.

• Administrators can now configure Power Optimized - Hourly Pools with zero online spares to reduce costs. By setting the spare count to “0” and selecting the option to provision all machines up front, all machines will be provisioned and then suspended to minimize ongoing expenses. When a user entitlement is launched, the WorkSpaces instance is powered on and delivered to the user on demand, ensuring cost efficiency without compromising availability. Power Scheduler is no longer needed and your entitlements are available whenever required.

• Administrators can now enable Workspace ONE UEM management and enroll machines directly from the Horizon Console when creating dedicated desktop pools.

• Helpdesk Remote Assistance is now available with Horizon 8 on Amazon WorkSpaces Core. You can generate remote assistance tickets for connected desktop or application sessions. Administrators can use remote assistance to take control of a user’s desktop and troubleshoot problems.

• Omnissa Horizon 8 on Amazon WorkSpaces Core now supports hybrid Microsoft Entra deployments in both Federated and Managed modes

Remote Desktop Features

• This release introduces GPO-based control to map URL redirection to an existing connected VDI session. URLs redirect to the most recently connected VDI when multiple sessions exist, or fall back to a defined default VDI when none are active. If no default applies, users can choose to launch in a VDI or local browser.

• Enhanced BENIT Transport Switching: The enhancement of BENIT switching to maintain performance amidst fluctuating network conditions.The BENIT transport switching logic can use the TCP connection quality to help it switch the active transport between TCP and BEAT. This approach allows for a more flexible adaptation of the Blast transport to the current network conditions, enhancing the end-user experience in varying network environments. This enhancement applies only to Windows Horizon Agent and All Clients.

• Blast Compatibility with NVIDIA GPUs on vSphere/VCF 9.x: Horizon now supports Blast connections using NVIDIA vGPUs on vSphere and VMware Cloud Foundation (VCF) 9.x. This update enables GPU-accelerated Blast performance across supported guest operating systems, including Windows 10, Windows 11, Windows Server, and supported Linux distributions.

• Horizon now supports Blast Extreme Adaptive Transport (BEAT) over Reverse Connection. Previously, Reverse Connection supported only TCP-based Blast. BEAT now works in Reverse Connection deployments without requiring any additional configuration, aside from ensuring outbound UDP connectivity from the agent to the UAG.

• Updated NVIDIA VideoSDK Support and Enhanced Blast Encoding Capabilities: Blast now upgrades to NVIDIA VideoSDK 13, replacing the legacy SDK 8 support and enabling use of both SDK 12 and SDK 13. This update includes improvements to encoder presets and tuning profiles as recommended by NVIDIA, resulting in improved compression efficiency to deliver higher video quality at lower bitrates.

• Dynamic Time Zone Redirection for RDSH: Added support for dynamic time zone redirection in RDSH (multi-session) environments to ensure the user’s client time zone, including dynamic DST rules, is accurately applied in the session. (This is already supported in VDI single session.)

• Vvc Raw Channel support for Blast MKS/Audio is now supported on Mac and mobile clients, and in deployments using UAG.

• Some of the performance enhancements in Vvc Raw Channels have been extended to all other Vvc-based features on TCP.

• Support for MS Teams Zoom Feature: Horizon Agent now supports the Zoom feature when using the Omnissa WebRTC Teams Optimization.

• Manual Noise Suppression Control: Horizon now adds support for manually disabling Noise Suppression when using Horizon Teams Optimization (WebRTC 1.0).

Windows OS Optimization Tool for Omnissa Horizon

• This release adds support for Windows 11, version 24H2 and later.

Resolved Issues

The numbers included before the resolved issues refer to the issues logged in the Omnissa internal issue tracking system.

• HZN-7190 - Horizon Connection server may experience high CPU usage caused by SamlReconfigure.
• HZN-5129 - Unable to change AD container from default of CN=Computers in Horizon Console when creating a Nutanix pool.
• HZN-5146 - Spare VMs are generated during the reprovisioning phase following a push operation in an on-demand instant-clone pool.
• HZN-5409 - Users may observe that machine assignments changed from readable username to GUID.
• HZN-5591 - Slow loading of user sessions in the Admin UI is significantly impacting helpdesk staff productivity and user access.
• HZN-5776 - Users may experience intermittent issues with on-demand power on/off functionality within their Horizon VDI sessions.
• HZN-6120 - Unable to save vTPM flag value set during push operation scheduled through REST API.
• HZN-6137 - The Helpdesk tool is failing to properly disconnect VMs between pods, resulting in session errors.
• HZN-6202 - Some users experienced upgrade failures requiring replica server removal and subsequent standard server upgrades.
• HZN-6331 - Provisioning error banner not cleared on admin console though provisioning was sucessful later after fixing provisioning error.
• HZN-6444 - An instant clone becoming unavailable and reporting as "Agent Disabled" in the Horizon console, even though the VDI appears to be functioning correctly
• HZN-6726 - Cluster Identity certificate shows not in use in the Horizon console even after replacing it with a CA-signed cert.
• HZN-6733 - A maximum of 10 networks are shown for selection during Nutanix pool creation workflow.
• HZN-6734 - RDS servers with active user sessions are moved into disabled state when push operation is performed with “wait for users to log off”; however, their status continues to appear as “Available” in the Horizon admin UI.
• HZN-6911 - The pool power policy is configured to power off; however, when users log off, the VDI desktops remain powered on instead of shutting down.
• HZN-6931 - Some users may have experienced difficulties associating network labels with Full Clone desktops during pool creation.
• HZN-6958 - New full-clone persistent VDIs created via API or Network Label Tool deploy on the master template’s VLAN instead of the pool’s updated VLAN.
• HZN-7024 - Logon segment metric data may intermittently disappear within a few minutes, impacting reporting accuracy.
• HZN-7053 - The Horizon Admin console incorrectly displays no events, preventing users from quickly identifying issues within the cluster.
• HZN-7075 - Despite Password Cache being enabled and TrueSSO mode being disabled in Workspace ONE, TrueSSO login is still being initiated.
• HZN-7189 - When administrators search for users and try to select the user's VM session, they may encounter an error if the VM is running RHEL 9.6.
• HZN-7275 - Users reported a slow System Health Dashboard after upgrading to 2503.1.
• HZN-7356 - Some users are unable to reset their desktops from the Workspace ONE Access Hub Console.
• HZN-7365 - Connection via F5 to connection server is not working after upgrade to 2503.
• UBI-585 - Refresh OS disk after n days setting for Nutanix pools causes refresh after logoff.
• UBI-680 - Unable to re-register a Nutanix golden image with Connection Server.

Known Issues

The numbers included before the known issues refer to the issues logged in the Omnissa internal issue tracking system.

Before upgrading to this release, please review the information in KB 6000681 and Upgrading to Omnissa Horizon 8 2412 and Later.

Horizon Connection Server

• HZN-5160: Sorting and filtering capabilities have been removed for specific columns in administrative grids. This results in a loss of functionality compared to previous releases and may impact administrative workflows.

  Workaround: None

• HZN-7443: If a VM is stuck in Customization state, delete the VM from Horizon Admin Console or Horizon REST API. Horizon will then recreate the VM.

• When there are more than ten global dedicated entitlements available to a user, the machine host name will sometimes not be visible in global entitlements if the "Show assigned host name" option is enabled.

• Scheduling an upgrade for an RDS host may complete successfully, but the upgrade itself can fail when the scheduled time is reached.

  Workaround: See KB article 6000992.

• If Horizon Events Database is hosted by an instance of Microsoft SQL Server (any version), do not disable TLS 1.2. This connection cannot be made over TLS 1.3.

• HZN-2542: When changing the browser locale and refreshing the Horizon Console UI, error alerts fail to display for the newly selected language.

  Workaround: Log in to Horizon Console in a new browser tab.

• HZEC-2336: View API consumers like the MP4H Adapter invoke MachineDetailsView. This API fails intermittently with user data not found error.

  Workaround: None

• HZEC-2873: Number of issues reported for ESXi Hosts in the dashboard summary may not match with number of issues reported in the dedicated ESXi Host issues section in the dashboard.

  If NVIDIA vGPU support detects a mismatch with the supported vGPUs for the given host, the issue count should be incremented but the count may not display in the UI.

  Workaround: View the warnings in Dashboard > System Health > View > vSphere > ESX Hosts.R

Horizon Agent for Linux

This section describes issues that might occur with Horizon Agent for Linux or when you configure a Linux desktop.

• VCART-9593: Linux VDI sessions fail to launch when FIPS mode is enabled on RHEL 8.10. There is no workaround for this issue.

• VCART-1502: The Session Collaboration icon disappears from the system tray after resizing a Debian 12.x desktop.

  Workaround: Disconnect from and reconnect to the desktop. The Session Collaboration icon usually appears after reconnection to the desktop. Alternatively, you can try restarting GNOME Shell with the following steps:

  1. Press Alt+F2 to display the Run a Command dialog box.

  2. Type "r" in the dialog box.

  3. Press Enter.

• VCART-9623: Sometimes the Collaboration window might not appear after you connect to a remote desktop and click the Collaboration UI icon.

  Workaround: Resize the desktop window or reconnect to the remote desktop.

• VCART-9624: The Linux agent's keyboard layout and locale do not synchronize with the client if the Keyboard Input Method System is set to fcitx.

  Workaround: Set the Keyboard Input Method System to iBus.

• VCART-9625: If you configure two monitors with different resolutions, and the resolution of the primary screen is lower than that of the secondary screen, you might not be able to move the mouse or drag application windows to certain areas of the screen.

  Workaround: Make sure that the primary monitor's resolution is at least as large as the secondary monitor's.

• VCART-9626: If a client user minimizes the window of a Linux published application using the Minimize command and then selects the Maximize command, the window is restored to its previous size instead of changing to full-screen mode as expected.

  Workaround: To change to full-screen mode, select the Maximize command again.

• VCART-9627: Linux published applications do not support using the window taskbar to divide the work area in a multiple-monitor display. For example, suppose a client user has two monitors arranged side by side. If the user moves the taskbar to the right side of the left monitor's screen or the left side of the right monitor's screen, the work area is divided into two parts. However, if the user then maximizes the application window, the window is displayed incorrectly in relation to the taskbar.

• VCART-9638: When connecting to a Linux published application from Horizon Client for Mac, the application window is displayed with square corners instead of rounded corners.

• VCART-9639: If a client user leaves a nonmodal dialog box open in a Linux published application and then makes active a native application on the client system, part of the dialog box will appear to be missing when the user returns to the published application.

• VCART-9640: If the client user minimizes a Linux published application window or brings another application in front of the published application window, the taskbar fails to display the thumbnail preview of the published application window. Hovering over the published application icon in the taskbar displays a blank thumbnail instead of the contents of the published application window.

• VCART-9641: Linux published applications do not support the Aero Snap feature on Windows client systems. Users connecting to a Linux published application from Horizon Client for Windows do not have the capability to snap or fix windows to the edges of the computer screen using the keyboard or mouse.

• VCART-9642: Linux published applications do not support the jump list feature on Windows client systems. If a user connects to a Linux published application from Horizon Client for Windows and right-clicks the taskbar icon for the application, no jump list is displayed.

• VCART-9643: Due to a limitation in the work area, Linux published application windows cannot be moved partially off the edge of the client's screen or work area. If the user attempts to move a published application window past the edge of the screen, the window will bounce back inside the screen's boundaries.

• VCART-9644: If the client user opens a modal dialog box from a Linux published application, that dialog box might not appear in front of native windows.

• VCART-9645: When connecting to a published application from a Windows client system, there are some differences between the context menus of the Windows taskbar and the application window's title bar. Shift + right-clicking the application icon in the Windows taskbar displays a menu with the items: Restore, Move, Size, Minimize, Maximize, Close. Right-clicking the application window's title bar displays a menu with the items: Minimize, Maximize, Move, Resize, Close.

• VCART-9646: Published applications do not support the Move and Size context commands for the taskbar on Windows client systems. When a user Shift + right-clicks the published application icon in the Windows taskbar, Move and Size appear in the menu but neither command has any effect if selected.

• VCART-9647: Published applications do not support the Size command from the application window's context menu. When a user right-clicks the title bar of the application window, Size appears in the menu of commands but has no effect if selected.

• VCART-9648: When a user opens multiple session windows for the same published application on a Windows client system, the Cascade all windows command has no effect.

• VCART-9649: If a Windows client user with a dual monitor configuration maximizes a published application in the lower-resolution monitor's work area, the Windows taskbar turns black.

• VCART-9650: After publishing a LibreOffice application as an application pool, duplicate LibreOffice icons might appear in Horizon Client.

  Workaround: From the Connection Server, manually assign the icon for the LibreOffice application.

• VCART-9651: Linux published applications do not support the Multi-Session Mode option in the application pool settings in Horizon Console.

• VCART-9652: When connected to a Linux published application, if the user opens a dialog box related to user account controls (such as when editing firewall settings), the desktop will not show.

• VCART-9653: Horizon Agent for Linux does not support session stealing between published desktops and published applications. For example, if a user has opened a published desktop session and then attempts to open an application session based on the same farm, the desktop session remains active and the application session is not established. Likewise, if the user has opened an application session and then attempts to open a published desktop session based on the same farm, the application session remains active and the desktop session is not established.

• VCART-9628: If a user types an entry into the Session Collaboration invitation text box and moves the cursor away from the text box, the original entry is cleared.

• VCART-9629: If a client user with a multi-monitor system opens a published application in seamless window mode, display problems might occur when moving the application window between monitors.

  Workaround: Shift + right-click the application icon in the client's task bar and select Maximize to enlarge and refresh the window display.

• VCART-9644: Display problems might occur when a client user opens published applications in seamless window mode on a multi-monitor system where some monitors have portrait orientation and other monitors have landscape orientation. If the user maximizes the application windows in all the monitors, the task bar appears black in the landscape monitors.

• VCART-9630: When client users copy content containing images in rich text format and then paste the content into an application on a remote Linux desktop, the images might be missing from the pasted content. This issue is caused by a limitation in certain third-party applications such as OpenOffice or LibreOffice, not by Horizon Agent for Linux.

  Workaround: Use a clipboard manager to retrieve the missing content from the clipboard.

• VCART-9632: The Enter Ctrl + Alt + Del control in Horizon Client does not take effect when connected to a RHEL 7.9 desktop with MATE desktop environment.

  Workaround: Use the default keyboard shortcut for logging out of a MATE desktop. Or, define a custom keyboard shortcut for logging out.

• VCART-9633: A small blank recording (2-3 kb) is sometimes created when a blast session running on Linux agent is being recorded by the Horizon Recording solution.

  Workaround: None. There is no adverse effect on the functionality except that a small recording can be seen in the recordings page for some of the sessions during a fresh logon.

Horizon Agent for Windows

• VCART-7428: Scheduling an upgrade for an RDS host may complete successfully, but the upgrade itself can fail when the scheduled time is reached.

  Workaround: See KB article 6000992.

Horizon Client

This section describes problems that end users might encounter when using Horizon Client or Horizon Web Client to connect to remote desktops and applications. For problems that occur only in a specific Horizon Client platform, see the Horizon Client release notes in the Omnissa Product Documentation portal.

• VCART-9656: When you connect to a Linux desktop, some keyboard inputs do not work. For example, if you are using a non-English IME on both the client device and the remote desktop, some non-English keys are not displayed correctly.

  Workaround: None.

• VCART-9655: When you use the Ambir Image Scan Pro 490i to perform a scan on a remote desktop or application, the dialog box always displays “Scanning…” and does not complete.

  Workaround: Perform a scan on the client. The client scan calibrates the scanner. After the calibrate operation is finished, save the calibration file and deploy it in ProgramData\AmbirTechnology\ImageScanPro490i.

• VCART-4245: HDR support for full screen mode is limited to a scenario where the selected monitor is the primary monitor.

  Workaround: None.

Windows OS Optimization Tool

• When the exported analysis report is exported to the same VM where you're running the Optimization Tool EXE, the report is auto-deleted after running the tool's Generalize task. Even though you'll still be able to view the report inside the Optimization Tool user interface, the exported report is deleted after Sysprep runs (Sysprep runs as part Generalize).

  Workaround: Export the analysis report to another location on the network instead of saving the report into the current user folders on the same VM. Because those user folders get deleted as part of Sysprep, if saved in those folders on the VM, the report is deleted during the Generalize run. If you specify to redirect the report to another location on the network, the report will be retained after running Generalize.

APIs

• HZN-3296: REST API ObjectGUIDs change after certain events, such as disaster recovery and pod rebuilding.

  Workaround: Do not rely on ObjectGUIDs as persistent identifiers. After an event such as disaster recovery and pod rebuilding, resync any third-party applications to the new ObjectGUIDs.

Nutanix

• HZN-6730: Desktops are not able to refresh when the connection server is down and the replica server is up.

  Workaround: None

• HZN-6964: Registered machines can be deleted when pools exist.

  Workaround: None

• HZN-7169: Farms can be created using the Windows 10 GI template.

  Workaround: None

Horizon 8 API

For the latest set of Horizon 8 APIs, see Omnissa Developer Portal and navigate to the current release in the drop down. Click on the Documentation tab for more details and examples on how to use the API.

Horizon Edge and Horizon Cloud Connector

Applicable to customers with Horizon Universal Subscription, Horizon Enterprise Plus Subscription, Horizon Standard Plus Subscription, Horizon Apps Universal Subscription, or Horizon Apps Standard Subscription.

The Horizon Edge is a required component for connecting Horizon 8 to Horizon Control Plane next-gen for subscription licensing enablement and additional control plane SaaS services.

The Horizon Cloud Connector virtual appliance is a required component for connecting Horizon 8 to the first-gen Horizon Control Plane for subscription licensing enablement and additional control plane services.

Horizon 8 Deployed on Public Cloud SDDCs

For a list of Horizon 8 features supported on Azure Omnissa Solution (AVS), see KB 80850.

For a list of Horizon 8 features supported on VMware Cloud on AWS, see KB 58539.

For a list of Horizon 8 features supported on Google Cloud VMware Engine (GCVE), see KB 81922.

For a list of Horizon 8 features supported on Oracle Cloud Omnissa Solution, see KB 88202.

For a list of Horizon 8 features supported on Alibaba Cloud Omnissa Service (ACVS), see KB 92140.

Before You Begin

• Important note about installing VMware Tools: If you plan to install a version of VMware Tools downloaded from the product downloads page, rather than the default version provided with vSphere, make sure that the VMware Tools version is supported. To determine which VMware Tools versions are supported, go to the Omnissa Product Interoperability Matrix. (Supported versions: 11.1.0, 11.0.6, 10.3.22, 10.3.21). There are also performance issues with the 11.x versions of VMware Tools. For more information, see KB 78434.

• When you deploy an instant clone as a RDS host, do not reboot the RDS host directly from within the Windows Server OS. Instead, refresh the instant clone VM using the push image workflow.

• To use View Storage Accelerator in a vSphere environment, a desktop virtual machine must be 512GB or smaller. View Storage Accelerator is disabled on virtual machines that are larger than 512GB. Virtual machine size is defined by the total VMDK capacity. For example, one VMDK file might be 512GB or a set of VMDK files might total 512GB. This requirement also applies to virtual machines that were created in an earlier vSphere release and upgraded to vSphere 5.5.

• For best practices on using Carbon Black with Horizon 8, see KB 95512.

• Horizon 8 supports a maximum of 500 virtual machines per ESXi host when using vSAN 8 ESA datastore. The achievable maximum depends on the workload and specifics of the hardware. For information on all Horizon configuration maximums, see VMware Configuration Maximums.

Upgrade

Check the Omnissa Product Interoperability Matrix before upgrading your Horizon deployment. Note the following guidance:

• You can only upgrade to a version with a release date later than your current deployment.

• When upgrading from a non-ESB version to an ESB version, the target ESB version must be later that your current non-ESB release. For example, you cannot upgrade from Horizon 8 2203 (non-ESB) to Horizon 8 2111.1 (ESB) even though 2111.1 was released after 2203 (or you will lose features). You can only upgrade to Horizon 8 2212 or later versions.

• Important: Please allow for extra time and preparation when you upgrade from a VMware-branded Horizon version to an Omnissa-branded Horizon version. For more details, see KB 6000681 and Upgrading to Omnissa Horizon 8 2412 and Later.

Compatibility Notes

The table below contains specific compatibility information as well as links to information located elsewhere.

Topic	Compatibility Information or Link
Horizon Client
Horizon Client with Windows 10 and 11	https://kb.omnissa.com/s/article/58096
Horizon Agent
Horizon Agent with Windows 10 and 11 - guest operating systems on single-user machines and RDS hosts	https://kb.omnissa.com/s/article/78714
Horizon Agent with OSs other than Windows 10 and 11 - guest operating systems on single-user machines and RDS hosts	https://kb.omnissa.com/s/article/78715
Horizon with Windows 10 - update or upgrade requirements	https://kb.omnissa.com/s/article/2148176
Horizon Agent with Linux guest operating systems	System Requirements for Horizon Agent for Linux https://kb.omnissa.com/s/article/87277
Horizon Server
Horizon with Operating Systems, MSFT Active Directory Domain Functional Levels, and Events Databases	https://kb.omnissa.com/s/article/78652
Horizon Software Interoperability
Antivirus executable exclusion list for Omnissa Horizon	https://kb.omnissa.com/s/article/2082045
Horizon 8 2512 interoperability with Omnissa products	Omnissa Product Interoperability Matrix - Horizon 8
Horizon 8 with third-party products	Omnissa Product Interoperability Matrix - Horizon 8 - 3rd Party
Horizon Hardware Compatibility
Horizon with third-party peripherals	Omnissa Validated Peripherals
Horizon with NVIDIA GPU cards	https://docs.nvidia.com/vgpu/latest/product-support-matrix/index.html

Use of Open Source

As part of the installation process, an open_source_licenses.txt file is written to the file system. Key open-source components included in this release are:

• Horizon Connection Server 2512 is built on the Apache Tomcat implementation of Jakarta EE, version 10.1.49.
• Horizon Agent for Linux 2512, Horizon Agent for Windows 2512, and Horizon Connection Server 2512 all utilize the BellSoft Liberica distribution of OpenJDK, version 17.0.16.0.1 (CPU).

Documentation

Horizon 8 documentation is in the Omnissa Product Documentation portal.

Localized Content for Omnissa Docs

For details on Omnissa's localization strategy, see Announcing Omnissa Localization Support.

Support Contact Information

To receive support and to learn more about support policies, see Omnissa Customer Connect.

For information on filing a support request in Customer Connect and via Cloud Services Portal, see KB 6000005.