Omnissa Horizon 8 Release Notes

Horizon 8 2603 | 14 APR 2026 Build: 8.18.0-24169897839

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

• For customers running Horizon 8 2512 with Nutanix automated pools or farms: A pairing mechanism change in 2603 requires that Connection Servers and Agents must both be updated to 2603 for ongoing provisioning operations to work. To prepare your environment for limited backward compatibility, see KB article 6001315. Does not apply if you have already upgraded to 2512.1.

• 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 these vSphere versions, and you must upgrade to vSphere 7.0 or later before upgrading to Horizon 8 to use Instant Clones.

What's New

Horizon Connection Server

• This release introduces next preferred site logic in CPA to improve routing when a site is full. Instead of random fallback, admins can now define a preferred site order. CPA will follow this order to select the next available site, providing more predictable routing, better performance, and improved load balancing.

• Administrators can create published applications delivered by unmanaged manual pools.

• Horizon now gathers entitlements across pods that are not federated. This gives users a single view of desktops and applications from both on-premises and hosted environments through the Horizon Client.

• The SAML Metadata feature enables administrators to configure Security Assertion Markup Language (SAML) authentication settings at the Cloud Pod Architecture (CPA) level. This functionality provides centralized control over SAML metadata distribution, certificate management, and entity identification across multiple pod deployments within your Omnissa environment.

• Connection Server now supports uploading elliptic curve (EC) certificates for the “vdm” certificate when compatible cipher suites are configured.

Horizon Console

• Added support for Windows Integrated Authentication (IWA) for MS SQL Event Databases in Horizon 8, removing the need to store or rotate DB credentials. Admins can choose SQL Authentication or IWA directly in the Horizon console. Username/password fields are hidden when IWA is selected. PostgreSQL 17 for Event DB is also supported in this release.

This release adds a new interface in the Horizon Console for managing Global SAML Authenticators. This allows administrators to view, create, change, and manage authenticators and their connected Connection Servers from one place.

• An option to Copy from Golden Image for network selection during Nutanix pool and farm workflows is now available.

• Post-synchronization and power-off scripts can be specified during Nutanix pool and farm workflows.

• This release improves accessibility across the Horizon Console with enhanced keyboard navigation, screen reader support, focus handling, contrast, and form labeling to better align with WCAG 2.2 AA guidelines.

• The Horizon Console now displays basic health information for UAGs registered with the Connection Server, including service status and gateway certificate health, providing essential infrastructure visibility.

• Enhanced security by preventing exposure of database passwords in the Recording Server UI and API responses. Added masked display and improved password handling across configuration workflows.

• Added the ability to search unassigned VMs and support custom filters in the Advanced Filter modal.

• Administrators can now enable Workspace ONE UEM management directly from the Horizon Console when creating non-persistent desktop pools, as support for persistent desktop pools is already available. 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.

Horizon Agent for Linux

• Horizon now supports VM names longer than 15 characters for Linux VDI desktop pools, removing previous naming‑pattern limits. Windows VDI continues to support a maximum of 15 characters.

• Added support for the MATE desktop environment on Red Hat Enterprise Linux (RHEL) 8.x and 9.x for Horizon Linux virtual desktops.

• The Horizon Linux Agent now uses an isolated, agent‑specific smart card service (pcscd-horizon) instead of overwriting the system /usr/sbin/pcscd, ensuring safe coexistence with the OS smart card service and improving system stability.

• Added support for Debian 12.13, Debian 13.3, and Rocky 9.7.

• Updated NVIDIA vGPU Support: Horizon Agent 2603 adds support for NVIDIA vGPU versions 16.13, 18.6, 19.4, and 20.0.

Horizon Agent for Windows

• The Horizon Windows Agent now includes a Blast system tray icon for desktop sessions. This icon provides at-a-glance visibility into the session experience, including network connection quality, and serves as a convenient entry point for Blast-related session information. An administrative policy (Blast System Tray) is available to disable the icon if needed.

• Added support for end users to immediately disconnect from a remote desktop or application session by pressing the Ctrl+Alt+F12 keyboard shortcut. This feature is disabled by default. Administrators can enable it through the viewClient.enableSessionDisconnectHotKey setting.

• Improved IP address selection logic in the Horizon Windows Agent to prioritize routable IPv4/IPv6 pairs for Blast connections, eliminating failures caused by non-routable interfaces (example, Internal Hyper-V NICs) without requiring additional configuration.

• Updated NVIDIA vGPU Support: Horizon Agent 2603 adds support for NVIDIA vGPU versions 16.13, 18.6, 19.4, and 20.0.

Remote Desktop Features

• Horizon now introduces Enforced Identity Consistency, a security enhancement that ensures only the entitled user who launches a desktop or published application can log in to that session even when Single Sign-On (SSO) is unavailable. For details on how to configure it, See GPO "Restrict Logon To Entitled Horizon Users Only" under Agent Configuration Policy Settings.

• Some performance enhancements from previous releases are now extended to support BSG.

• This release improves Universal Broker by allowing you to create Pool Groups that contain Horizon 8 RDSH farm desktops directly from the Horizon Cloud Universal Console. By synchronizing RDSH farms and enhancing integration with the Control Plane, you can more seamlessly incorporate multi-session resources, optimize resource utilization, and manage hybrid environments from a central location.

• Added support for URL Content Redirection in Workspace ONE mode.

Windows OS Optimization Tool for Omnissa Horizon

• Added support for using the OSOT SCCM plugin to streamline integration with SCCM and simplify task sequence creation and deployment workflows. The plugin is supported on Windows 11 24H2 and Windows 11 25H2.

• Added support for using a custom unattend.xml during sysprep in SCCM task sequences, allowing configuration of language, locale, time zone, user accounts, and other Windows setup parameters. This replaces the default Apply Windows Settings step.

• Added support for using a task sequence import script to streamline OSOT deployment and automate task sequence configuration.

Resolved Issues

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

• AST-6712: Horizon attempts to reconnect user with session "already used"
• AST-7962: Blast crashes and prevents user from reconnecting to their session
• AST-11503: Users unable to launch Horizon VDIs after upgrading Horizon client to version 2512
• HV2-193943: When deleting a pool or farm running on Nutanix AHV 11.0, the associated internal template VM and category are not deleted
• HZN-4903: Admin user is unable to login to admin console after stale entries remain for local custom role in global database
• HZN-6021: User lookup and Machines Tab Takes Extremely Long Time or Time-Out
• HZN-6250: Users unable to connect to Application pool associated with App Volumes application when no local AVM assignment is present for user
• HZN-6785: Events are not displayed correctly in Horizon Admin console
• HZN-6912: Pool Power policy of power off after logoff is not working due to COLLISON
• HZN-6964: Registered machines can be deleted when pools exist.
• HZN-7229: TrueSSO login is being triggered even though the Password cache option is enabled on WS1 and TrueSSO mode is disabled on WS1
• HZN-7357: Horizon console only lists 100 home site user assignments, whereas the report pulled shows 151 user assignments
• HZN-7386: Custom icon associated with Published application gets removed if the application is edited
• HZN-7416: Horizon recorded assignment to dedicated systems changed from readable username to GUID
• HZN-7492: Connection Server returns false Horizon Client compatibility Error due to improper supportedFeatures validation
• HZN-7591: NVIDIA machines not added to a vCenter-managed, manual desktop pool
• HZN-7599: Idle timeout is sending a logoff before sending a stopAWS API call
• HZN-7633: Section under "System Health" in one of the horizon pods says "ESX Hosts". However, when attempting to expand this, there is no information, and an error message about "Internal server error" pops up
• HZN-7833: After upgrading Horizon 2406 -> Omnissa Horizon 2512, internal Connection Servers no longer display any AD/domain accounts in the Admin Console when domains are excluded from Connection Server
• HZN-7991: The Horizon weekly backup schedule is set to perform backups at midnight on Sunday instead of midnight on Saturday
• HZN-7995: Intermittently observing error "An internal server error occurred" while assigning a manual desktop to a user
• HZN-8041: In Horizon Admin Console Remote Access page will not load for over 30 minutes
• HZN-8088: The Activate > Term/Perpetual button opens the license entry modal without switching the system’s license mode from SUBSCRIPTION to PERPETUAL_ONLY. As a result, term license activation fails
• HZN-8091: Unable to add new application from the existing farms. When adding application, the drop-down list shows no RDS hosts with an error “Internal Error Occurred“
• HZN-8132: If a user is not entitled to the pool but assigned to a dedicated VDI, there is a pop-up box mentioning the user is not entitled to the pool and an error message
• HZN-8134: Refresh fails after a user logs off. According to the logs from both CSs, commitRequests sometimes conflict, resulting in a VoteAbort for both
• HZN-8178: Adding vms with L2 gpu profile "VM is on a host that doesn't support NVIDIA GRID vGPUs or the vGPU type"
• HZN-8179: Users added from secondary domain are not listing under Desktop Pool > Policy Override tab is stuck on a spinning wheel
• HZN-8196: Outfit variable font used in Horizon admin console is displayed incorrectly in Firefox running on Windows 2019 and Windows Server 2016
• HZN-8275: Ad user or groups get by ids api required for assign users flow for machines
• HZN-8283: Installer fails when attempting to upgrade from 2506 -> 2512.1
• HZN-8361: Creation of an instant clone desktop pool is failing
• HZN-8382: Admin UI fails to load after upgrading Horizon Connection Server from 2506 to 2512.1
• VCART-7428: Scheduling an upgrade for an RDS host may complete successfully, but the upgrade itself can fail when the scheduled time is reached.

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-9004: Instant Clone Push Image Applies to Only a Few VMs While Remaining VMs Retain Old Image

  Workaround: See KB article 6001424.

• HZN-8048: After restarting a Connection Server, the error "Cannot look up datacenter from Virtual Center." is displayed in the Horizon Console.

  Workaround: See KB article 6001328.

• 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.

Horizon Agent for Windows

• Rendering and scaling issues may occur in DPI-sensitive applications when using the Blast protocol with the IDD (Indirect Display Driver).

  Workaround: See KB 6001433.

• HZN-8997: The Admin UI displays an incorrect GOS type for the Agent VM following the upgrade from Windows 10 to Windows 11.

  Workaround: Remove the machine from the Admin UI (under Registered Machines > Others), then reinstall the unmanaged agent. After completing these steps, the Admin UI correctly displays the operating system as Windows 11.

• When a QoS policy is configured on the Horizon Agent, the Bypass Blast Service TCP proxy feature is disabled.

  Workaround: None.

Horizon Agent for Linux

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

• VCART-9623: 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 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

• LCM APIs aren't available in the 2603 release.

• 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-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 2603 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

Horizon 8 uses several open-source software packages. For more information about what packages are used in this release, see Open source notices.

• Horizon Connection Server 2603 is built on the Apache Tomcat implementation of Jakarta EE, version 10.1.52 and on the BellSoft Liberica distribution of OpenJDK, version 17.0.17.0.1 (CPU).
• Horizon Agent for Linux 2603 and Horizon Agent for Windows 2603 use the BellSoft Liberica distribution of OpenJDK, version 21.0.9.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.