Omnissa Horizon 8 Release Notes

Horizon 8 2606 | 24 AUG 2026 Server Build: 8.19.0-32260804026 Agent Build: 8.19.0-32216675775

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 2606 Agent is supported with both the 2603 ESB Server and the 2606 Server versions. See Compatibility Matrix for Various Versions of Horizon 8 Components for more details.

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

• 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

• The Connection Server installer now automatically stops and disables Active Directory Web Services (ADWS) during installation, reducing the default security exposure surface. ADWS is not required for normal Connection Server operation and can be enabled when temporarily needed through the Horizon Advisor AD LDS Operations menu.

• This release introduces next preferred site logic in Cloud Pod Architecture (CPA). Administrators can define an explicit preferred site order so that when an initial site reaches capacity, sessions are routed to the next configured site rather than falling back randomly.

• The new AD LDS migration script allows customers with large CPA deployments to move from the legacy AD LDS partition to the new Horizon partition over extended migration period. It supports staged migration, so independent pods can be migrated in separate maintenance windows while CPA remains functional. Administrators can add or remove local pools from global entitlements, create or delete global entitlements, and perform site operations during migration, reducing risk and downtime for large, multi-pod deployments. This script is now delivered as part of Horizon Advisor and is no longer available as a standalone script.

• PSG (PCoIP Secure Gateway) is now selectable as an optional component during the Horizon Connection Server installation.

• Microsoft introduced Microsoft Entra Hybrid Join using Microsoft Entra Kerberos that significantly improves sync wait time for Entra ID Hybrid Managed mode. For details, see Support for Microsoft Entra (Azure Active Directory).

• New password requirements have been introduced for Connection Server LCM API installations and upgrades, varying depending on the installation type and hosting method.

• True SSO unlock now supports any third-party SAML Identity Provider, in addition to Workspace ONE Access. The Identity Provider must support SP-initiated SSO using the HTTP POST binding for AuthnRequests.

• Administrators can now create App Volumes published apps on demand using manual RDSH Farms in addition to the existing support for Instant Clone automated RDSH Farms.

• Horizon 8 now calculates Concurrent Connection User (CCU) license consumption using the same logic as Horizon Cloud, giving administrators and license teams accurate, consistent usage counts across both platforms. A new REST API also lets the UI and Edge Gateway retrieve historical peak and daily CCU data, reducing reliance on manual or unreliable tracking and giving license teams data for compliance and capacity planning.

• Horizon components have been updated to use OpenSSL 3.5, replacing the previous OpenSSL 3.0.x libraries which are approaching end of life. This includes the Blast Secure Gateway (BSG) for both Connection Server and Unified Access Gateway (UAG).

Horizon Console

• Administrators can now monitor Unified Access Gateway (UAG) health and utilization at the pod level directly from the Horizon Console, displaying real-time availability status, service health, error details, and certificate expiration status for each UAG appliance.

• A new Isolated App Launch setting is available for published applications. When enabled, each application launch starts in a new, independent RDSH session rather than reusing an existing session.

• JWT authenticator configuration has been relocated to Global Settings > Authenticators in the Horizon Console, providing a single location for managing all authentication methods.

• Administrators can now apply an Allowed User Access Location to multiple desktop pools or application pools in a single action from the Horizon Console.

• Horizon Console UI behavior: Rows Per Page preferences are automatically saved in the Horizon Console.

• Certificate management for SAML certificates is now available within the Horizon Console, enabling administrators to view, update, and manage SAML certificate lifecycles without leaving the console.

• Horizon Console tables, including session grids, now support a "Select All Pages" option, restoring the ability to select rows across all pages of a multi-page table rather than only the currently visible page. This allows bulk actions, such as sending messages to all sessions, to operate on the full result set instead of requiring page-by-page selection.

Horizon Agent for Linux

• Horizon now supports application-based URL redirection for the Linux Agent, enabling URLs clicked in applications such as Slack and email clients to redirect to the Horizon Client on Mac, Linux, and Windows.

• Horizon Agent for Linux 2606 adds support for ECDSA certificate types for the agent TLS endpoint. Both RSA (default) and ECDSA key types are now supported via installer flags.

• Horizon Agent for Linux 2606 upgrades the bundled OpenSSL libraries from the 3.0.x series to the latest available 3.5.x release to support continued compliance with cryptographic library requirements.

• Administrators can now configure the sample rate used for redirected (virtual) microphone audio on Horizon Agent for Linux VDI desktops.

• FIPS 140-3 mode is now supported on RHEL 9.x (9.6 and later).

• This release adds support for Debian 13.4, RHEL 9.8, and Rocky Linux 9.8, and drops support for Debian 13.3. Wayland support for RHEL 10.0 on Horizon 8 on vSphere is added as Beta, For more details, please check beta.omnissa.com.

Horizon Agent for Windows

• The "Instant Clone Agent" feature in the “Horizon Agent for Windows” installer has been renamed to “Provisioning and Customization Agent” to reflect that this feature is required for provisioning other types of pools and farms besides vSphere. Existing deployments are not affected by this change.

• Horizon Agent for Windows 2606 upgrades the bundled OpenSSL libraries from the 3.0.x series to the latest available 3.5.x release to support continued compliance with cryptographic library requirements.

Horizon Agent for Mac - LIMITED AVAILABILITY

• Horizon Agent for macOS enters Limited Availability (LA) for production environments in 2606. Administrators can install the macOS Agent on physical macOS devices and enroll them with Workspace ONE UEM to centrally manage required macOS privacy permissions, including Screen Recording and Accessibility, through MDM policies. This eliminates the need for end users to manually approve permission prompts during Horizon login or remote session workflows.

Horizon 8 on Amazon WorkSpaces Core

• Improved WorkSpaces quota validation: Before creating or editing a pool, the system verifies that the requested number of WorkSpaces fits within the AWS regional quota based on current usage. If the quota or current usage cannot be retrieved because of a transient AWS API issue, the validation allows the operation to proceed, improving pool creation reliability while preserving AWS-side quota enforcement.

• Horizon 8 on Amazon WorkSpaces Core now supports encrypting the WorkSpaces instance within the automated pools workflow. Administrators can chose either the AWS managed KMS key or a Customer managed KMS key. When choosing to encrypt a WorkSpace instance, both root and user volumes will be encrypted. Doing so ensures that the data stored at rest, disk I/O to the volume, and snapshots created from the volumes are all encrypted. Encrypted WorkSpaces instances take longer to provision than unencrypted instances. For more information see Encrypted WorkSpaces in WorkSpaces Personal - Amazon WorkSpaces

• Administrators can now perform pool bundle maintenance operations directly from the Horizon console, improving operational efficiency and reducing reliance on external workflows. Pool maintenance scheduling enables updates to the bundle or image associated with a pool, with changes in Horizon automatically synchronized to AWS. For non-persistent pools, refresh operations now offer flexibility to either force user logoff or wait for users to log off naturally. Additionally, the pool machines tab has been enhanced to display WorkSpace ID, Bundle ID, and Image ID, providing clear visibility into current configuration and maintenance status.

Horizon 8 on Nutanix

• Improved provisioning retry and recovery logic for Nutanix virtual machines that experience customization failures.

• Administrators can now upgrade, modify, repair, or reinstall Horizon Agent on a Nutanix Golden Image without needing to change its Windows hostname (computer name). Existing registration is preserved, pool operations are unaffected, and installer workflows have been optimized to avoid unnecessary re-registration and pairing actions.

• Horizon Agent Auto-Upgrade (AAU) now supports Nutanix AHV environments. Administrators can extend automated agent lifecycle management to Nutanix AHV-hosted desktop pools in addition to existing vSphere support.

• There is no longer a requirement for a Horizon Pod to use the new Omnissa ADAM Database partition naming when configuring and using Horizon 8 to provision pools and farms on Nutanix.

Remote Desktop Features

• Cache Size Enforcement for Linux Client Redirection Features: Added support for cache size limits for Browser Content Redirection (BCR) and HTML5 Multimedia Redirection (HTML5MMR) on Linux clients. Administrators can configure maximum cache sizes to prevent excessive disk usage from client-side browser processes.

• Blast protocol now supports ECDSA Certificates.

• Storage Drive Redirection (SDR) has been removed from the Horizon Agent installer and is no longer available in Horizon Client. To share local drives and folders with remote desktops and published applications, use Global Sharing (Client Drive Redirection) instead.

Windows OS Optimization Tool for Omnissa Horizon

• New Security tab options: Turn Off Device Encryption and Disable BitLocker
  Two new options have been added to the Common Options Security tab to support golden image preparation in VDI environments.

  • Turn Off Device Encryption decrypts all the encrypted volumes on the VM. The tool waits for the decryption to completed before moving on to the next step. The decryption may take some time to complete depending on the size of the volume.
  • Disable BitLocker prevents Windows from automatically enabling device encryption on the image.

• The Windows OS Optimization Tool has been enhanced for the golden image creation workflow, streamlining the end-to-end preparation process.

• OSOT SCCM integration now supports VMware Tools management within SCCM task sequences. Administrators can include VMware Tools installation and configuration steps in SCCM-based golden image creation workflows.

Resolved Issues

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

• AST-14744: Remote Assistant Support broken due to Microsoft patch update
• HZN-10522: Connection Server TCP ephemeral port exhaustion after prolonged uptime causing vCenter connectivity failure and VM status errors

• HZN-10304: VLAN subnets from multi-cluster virtual switches were not displayed in the network selection UI (Nutanix pool management).
• HZN-10301: REST API intermittently returned "This application is currently not available" when connecting to a published application.
• HZN-10257: The inventory page loaded slowly in large-scale deployments.
• HZN-9969: Expanding a pool with an NVIDIA vGPU could fail with the error "Host or cluster does not support the same GRID vGPU type as the template or snapshot."
• HZN-9966: The Connection Server favicon request returned a 502 error after a replica server restart.
• HZN-9950: In the Instant Clone pool Schedule Push Image flow, the Push to Specific Machines grid displayed all data on a single page and did not honor pagination.
• HZN-9909: The REST API Push Image endpoint for Instant Clone pools was missing MAINTENANCE_ADMIN validation.
• HZN-9771: Moving between pages cleared the selected items in Users and Groups for a Global Entitlement.
• HZN-9764: Smart Card authentication with a custom altSecId mapping failed to pass userNameHint to the AD lookup.
• HZN-9705: Users could not access VDI via Workspace ONE Access after upgrading the Horizon environment.
• HZN-9525: After a silent install, first logon to Horizon Console with an administrator account from a child domain could cause errors under Settings.
• HZN-9471: Editing pools could fail with the error "Host or cluster with requested id was not found."
• HZN-9467: Authentication to Linux desktops failed after upgrading Horizon.
• HZN-9392: A Connection Server upgrade could fail with an "Allow_ntlmfallback cannot be null" error.
• HZN-9277: Unable to edit pools or provision VMs on pools after upgrading.
• HZN-9179: Desktop pool provisioning failed with an LDAP runtime error (Nutanix).
• HZN-9158: Desktop pool creation issue with Horizon Connection Server on Ubuntu (duplicate of another tracked issue).
• HZN-9149: Universal Broker JWT-based authentication broke when upgrading Connection Server from 2506 to 2603 (duplicate of another tracked issue).
• HZN-9139: Horizon did not connect reliably to Nutanix.
• HZN-9133: Adding virtual machines to a Full Clone pool failed with the error "delete_or_refresh_machine_after_logoff can be set to REFRESH only for instant clone desktop pools."
• HZN-9124: Creating a new RDS Host could fail with "A desktop pool or farm named [name] already exists" even when no such pool or farm existed.
• HZN-9061: Unable to access the second page of the Applications inventory in Horizon Console after upgrade.
• HZN-9036: The GET external/v1/ad-users-or-groups API did not return correct data depending on how pages were requested.
• HZN-9004: Instant Clone Push Image Applies to Only a Few VMs While Remaining VMs Retain Old Image
• HZN-8915: Connection Server did not properly handle Nutanix machine cache updates when the PendingOperation owner changed to another Connection Server.
• HZN-8893: Creating a new Linux OS desktop pool did not display the Customization Specification option (duplicate of another tracked issue).
• HZN-8883: The InternalVMSweeper job running concurrently on multiple nodes could cause provisioning failures (NGVC).
• HZN-8871: Machine status in the Summary tab was inaccurate for Capacity Provider-based VMs (Nutanix).
• HZN-8793: Horizon memory data was missing from the Pool view.
• HZN-8790: Authentication to Linux desktops failed after upgrading Horizon.
• HZN-8785: Constant async commit events were written to the error.log-.old file on the Connection Server.
• HZN-8772: The Connection Server Admin UI became unavailable.
• HZN-8749: The domain changed unexpectedly when editing a pool.
• HZN-8747: Log collection using Horizon Console failed with an internal server error.
• HZN-8686: Log collection using Horizon Console failed with an internal server error.
• HZN-8432: After disconnecting from a Horizon desktop session, a new desktop was assigned on reconnection instead of the original one.
• HZN-8336: Unable to view domain accounts under Horizon Console > Domains; displayed "An internal server error occurred."
• HZN-8253: Removed unnecessary fetching of counts from the historical table, improving performance.

• HZN-988: ADMIN_LIMIT_EXCEEDED error occurs when more than 1273 global entitlements gets local resource assignments in one pod

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

• HZN-19589: CPA join fails for a pod if the “Default First Site” is removed from the federation/pod it joins.

  Workaround: Perform the join after setting pae-LDAPSchemaVersion to a lower value than the current one under CN=common,OU=Global,OU=Properties,DC=vdiglobal,DC=horizon,DC=internal

• 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

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

• HZM-10760: Server requirement checks in remote mode: When prechecks are run remotely against a target server, the Static IP, OS Edition, OS Version, and Installed Features results reflect the machine running Horizon Advisor rather than the target server.

  Workaround: Run the precheck locally on the target server to get accurate results for these four checks.

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 VMware 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 VMware Solution, see KB 88202.

For a list of Horizon 8 features supported on Alibaba Cloud VMware 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 2606 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 2606 is built on the Apache Tomcat implementation of Jakarta EE, version 10.1.57 and on the BellSoft Liberica distribution of OpenJDK, version 21.0.11.0.1 (CPU).
• Horizon Agent for Linux 2606 and Horizon Agent for Windows 2606 use the BellSoft Liberica distribution of OpenJDK, 21.0.11.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.