Omnissa Horizon 8 Release Notes

Horizon 8 2506.1 | 3 NOV 2025

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.

Upgrading Changes

For upgrades to Horizon 8 2506, review these important considerations:

• Beginning with the Horizon 8 2412 release, there is a new licensing module for term and perpetual licenses. Review the License Activation section in these release notes for details.

• It is very important for you to thoroughly review KB 6000681 before starting your Connection Server upgrade. To ensure compatibility with existing system components, third-party integrations, and automated workflows, follow the recommendations outlined in that KB 6000681, and in Upgrading to Omnissa Horizon 8 2412 and Later.

• Omnissa recommends that you validate the upgrade in a UAT environment before deploying it to your production environment.

Important Notes

• The Horizon 2506 Agent is now supported with both the 2503 ESB Server and the 2506 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.

• Microsoft security update (KB 5014754) will impact customers using certificate-based authentication to Horizon 8, such as smartcard authentication. Horizon 8 True SSO is not impacted by this security update. If you have applied this update to your Windows Domain Controllers but have not mapped certificates to one of the strong mapping types described in the Microsoft KB, then users will be denied authentication after Full Enforcement mode is activated by Microsoft in a future Windows Update. See the above KB for further details, including the expected Full Enforcement mode date. To address this issue, Horizon 8 2309 introduced the ability for administrators to configure strong certificate mappings from the Horizon console. If you are using certificate-based authentication, upgrade to Horizon 8 2309 or later in order to configure certificate mappings. See KB 91595 for details.

• Horizon Agent no longer supports Windows Server 2012 R2 within a guest OS whether it be for new or existing deployments. Also starting with Horizon 8 2312, the use of Windows Server 2012 R2 is no longer supported for Horizon Connection Server and Horizon Enrollment Server deployments. Please use Windows Server 2016 or later. See https://learn.microsoft.com/en-us/lifecycle/announcements/windows-server-2012-r2-end-of-support for details.

• Microsoft released security updates KB5008383 and KB5020276. While Omnissa has determined that KB5008383 does not impact Horizon Full Clones and Instant Clones, KB 5020276 does if you have selected “Allow Reuse of Existing Computer Accounts”. See KB 92214 for details.

What's New

Horizon 8 version 2506.1 is a Horizon Agent for Windows release. It includes the following new feature.

Horizon Agent for Windows

• Dynamic Timezone Redirection in RDSH sessions is now supported.

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

• You cannot mix IPv4 and IPv6 pods in a single CPA federation. They have to all be IPv4 or IPv6.

• Microsoft Internet Explorer is no longer supported for Omnissa Horizon Console from Horizon 2111 onward. As Horizon Console is migrating to clarity widgets which do not support Internet Explorer, we have removed Internet Explorer from the list of supported browsers for Horizon Console.

• The Horizon Virtualization Pack for Skype for Business is no longer supported in this release. When using this release of Horizon Client with Horizon Agent 2212 or earlier, the Virtualization Pack for Skype for Business will continue to run in fallback mode.

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

• Downgrading Connection Server instances is not supported. To revert to a previous version after an upgrade, restore from backup. For more information, see Create a Replicated Group After Reverting Connection Server to a Snapshot.

• It is possible that the ordering of cipher suites can be enforced by Connection Server. For more information, see Horizon Security.

• Connection Server must be able to communicate on port 32111 with other Connection Servers in the same pod. If this traffic is blocked during installation or upgrade, installation will not succeed.

• TLS handshakes on port 443 must complete within 10 seconds, or within 100 seconds if smart card authentication is enabled. In previous releases of Horizon, TLS handshakes on port 443 were allowed 100 seconds to complete in all situations. You can adjust the time for TLS handshakes on port 443 by setting the configuration property handshakeLifetime. Optionally, the client that is responsible for an over-running TLS handshake can be automatically added to a blacklist. New connections from blacklisted clients are delayed for a configurable period before being processed so that connections from other clients take priority. You can enable this feature by setting the configuration property secureHandshakeDelay. For more information about setting configuration properties, see Horizon Security.

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

• In Horizon 8, internal validation checks determine if the instant clone and internal template have valid IP addresses and a network connection. If a virtual machine has a NIC that cannot be assigned an IP address during provisioning, instant-clone provisioning fails.

  The forwarding rules for HTTP requests received by Connection Server instances have changed at this release. If you have defined custom frontMapping entries in locked.properties , you should remove them before upgrading. If you wish to disallow administrator connections to certain Connection Server instances, then instead of defining custom frontMapping entries, add this entry to locked.properties :

  frontServiceWhitelist = tunnel|ajp:broker|ajp:portal|ajp:misc|moved:*|file:docroot

• In Horizon 8, the HorizonDbChk tool will not have access to vCenter credentials and will prompt for this information when needed.

• Microsoft Windows Server requires a dynamic range of ports to be open between all Connection Servers in the Horizon 8 environment. These ports are required by Microsoft Windows for the normal operation of Remote Procedure Call (RPC) and Active Directory replication. For more information about the dynamic range of ports, see the Microsoft Windows Server documentation.

• Screen DMA is disabled by default in virtual machines that are created in vSphere 6.0 and later. Horizon 8 requires screen DMA to be enabled. If screen DMA is disabled, users see a black screen when they connect to the remote desktop. When Horizon 8 provisions a desktop pool, it automatically enables screen DMA for all vCenter Server-managed virtual machines in the pool. However, if Horizon Agent is installed in a virtual machine in unmanaged mode (VDM_VC_MANAGED_AGENT=0), screen DMA is not enabled. For information about manually enabling screen DMA, see KB 2144475.

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

• The Global Policy, Multimedia redirection (MMR), defaults to Deny. To use MMR, you must open Horizon Console, edit Global Policies, and explicitly set this value to Allow. To control access to MMR, you can enable or disable the Multimedia redirection (MMR) policy globally or for an individual pool or user. Multimedia Redirection (MMR) data is sent across the network without application-based encryption and might contain sensitive data, depending on the content being redirected. To ensure that this data cannot be monitored on the network, use MMR only on a secure network.

• The USB Redirection setup option in the Horizon Agent installer is deselected by default. You must select this option to install the USB redirection feature. For guidance on using USB redirection securely, see Deploying USB Devices in a Secure Horizon Environment.

• For information on security considerations and disallowing inter-virtual machine transparent page sharing, see KB 2080735.

• If a PCoIP Secure Gateway (PSG) has been deployed for PCoIP connections, zero client firmware must be version 4.0 or later.

• RC4, SSLv3, TLSv1.0 and TLSv1.1 are disabled by default in Horizon 8 components, in accordance with RFC 7465, "Prohibiting RC4 Cipher Suites," RFC 7568, "Deprecating Secure Sockets Layer Version 3.0," PCI-DSS 3.1, "Payment Card Industry (PCI) Data Security Standard", and SP800-52r1, "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations." If you need to re-enable RC4, SSLv3, TLSv1.0 or TLSv1.1 on a Connection Server or Horizon Agent machine, see Older Protocols and Ciphers Deactivated in Horizon.

• Horizon 8 uses version m86 of Microsoft WebRTC source code.

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

• Horizon 8 supports vSAN 8 Express Storage Architecture (ESA) for both full and instant clones. For more information on vSAN 8 ESA, see https://techzone.omnissa.com.

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

• Cross-origin resource sharing is enabled by default. If you experience connection issues from Horizon Web Client, you might need to add the connection URL to the known origins list. For more information, see KB 85801.

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 2506 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/grid/15.0/product-support-matrix/index.html

Resolved Issues

The list below indicates major issues resolved in this release.

• Fixed an Outlook Window Sharing Privacy issue with Teams Optimization to correctly stop window sharing when the shared window is closed.

• The following open source software packages have been upgraded: OpenSSL, OpenJDK, Libxml, and libcurl.

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

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

• 3073725: 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 GRID 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.

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

  Workaround: None

• 1850273: When you set up True SSO in an environment with CAs and SubCAs with different templates set up on each of them, you are allowed to configure True SSO with a combination of templates from a CA or SubCA with another CA or SubCA. As a result, the dashboard might display the status of True SSO as green. However, it fails when you try to use True SSO.

Horizon Recording

• HZN-3928: Conflict issues will occur when you upgrade from Horizon Recording Agent RPM 1.12 to 1.13.

  Workaround: Instead of upgrading, uninstall Horizon Recording Agent RPM 1.12 and install Horizon Recording Agent RPM 1.13.

Horizon Agent for Linux

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

• VCART-3894: Installation of Horizon Recording Agent fails when using the RPM installer on a RHEL 8.10 machine.

  Workaround: Before running the RPM installer for Horizon Recording Agent on a RHEL 8.10 machine, downgrade the rpm-plugin-selinux package with this command: yum downgrade rpm-plugin-selinux-4.14.3-26.el8.x86_64
  For more information, see Red Hat Knowledge Base article 3739361.

• VCART-3920: After logging into an Ubuntu 24.04 desktop, a black screen sometimes appears.

  Workaround: Enter the Ctrl+Alt+D shortcut to fix this problem. If the problem persists, enter Ctrl+Alt+T several times, and then enter Ctrl+Alt+D again.

• VCART-2404: After creating a full-clone or instant-clone desktop pool from an Ubuntu 24.04 machine, desktops are unavailable and the base machine appears to have no IP address and a disconnected network adapter.

  Workaround: This issue is related to the hardware clock setting on the machine. Apply the workaround documented in Knowledge Base article 95091.

• HIX-374: When a user opens a remote session to a physical Linux machine, the local monitors for the machine go blank and the local console cannot be accessed.

  Workaround: To restore access to the local monitors and console, disconnect from the remote session. If the remote session cannot be disconnected, unplug the network cable from the physical machine. After about 5 minutes, the agent will return control to the physical machine and allow logins to the console.

• 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-438: Pressing Ctrl+Alt+F1 or Ctrl+Alt+F2 does not display the graphical desktop on a physical host machine after Horizon Agent is installed. Since TTY1 is reserved for the Gnome Display Manager, Horizon Agent uses TTY7 instead.

  Workaround: To display the graphical desktop on a physical host machine, press Ctrl+Alt+F7.

• 2969881: NVIDIA GRID 14.0 GPU with P100 vGPU profile is not supported for Linux desktops.

  Workaround: Use NVIDIA GRID 14.1 GPU instead.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• 2668258, 2576341: 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.

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

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

• 2975449: When a Microsoft Teams user selects background blur image for their video call or meeting, that setting does not persist after user disconnects/logs off from the desktop or restarts the Teams service inside the desktop.

  Workaround: User needs to remember to preselect Background blur when they log in or restart Teams.

• 1993397: If a collaborator joins a multi-monitor session and enables relative mouse mode on their client, it is possible for the mouse to move to a secondary monitor that the collaborator cannot see.

  Workaround: Move the mouse back on to the screen. Alternatively, don't use relative mouse mode in a multi-monitor session.

• 1799790: A warning message about applications in use appears when you uninstall Horizon Agent on Windows Server 2016.

  Workaround: Click “Ignore” in the dialog box that appears when you use Windows Add or Remove Programs to uninstall Horizon Agent. If you uninstall Horizon Agent from the command line, use the command msiexec /x /qn {GUID of Agent} instead of the command msiexec /x {GUID of Agent}.

• 1874531, 1699275: When you uninstall the Horizon Agent, the mouse speed becomes slow and jerky. Uninstalling Horizon Agent also uninstalls the vmkbd.sys driver.

  Workaround: Repair VMware Tools on the Horizon Agent virtual machine.

• 1993397: If a collaborator joins a multi-monitor session and enables relative mouse mode on their client, it is possible for the mouse to move to a secondary monitor that the collaborator cannot see.

  Workaround: Move the mouse back on to the screen. Alternatively, don't use relative mouse mode in a multi-monitor session.

• 2003328: If you use Chrome with URL Content Redirection, and you set "..google." for the https protocol in filtering rules and you set Google as your home page in Chrome, redirection to google.com occurs each time you open a new tab.

  Workaround: Change the home page or the filtering rules.

• 2022449, 2022448: When setting up a collaborative session, adding a collaborator by the email address from a two-way trusted domain fails.

  Workaround: Add the collaborator by using domain\user.

• 2390130: After you connect to a remote desktop that has the Real-Time Audio-Video feature enabled, you might see the following message: "Your PC needs to be restarted to finish setting up this device: devicename (VDI)."

  Workaround: You can ignore this message as the device is usable in the remote desktop. Alternatively, you can turn off the Windows Settings notifications to prevent the message from being displayed.

• 2512363, 2401690: sysprep fails for full clones with Windows 10 1903, Windows 10 1909 guest OS with error:

  SYSPRP Sysprep_Clean_Validate_Opk: Audit mode can't be turned on if there is an active scenario.; hr = 0x800F0975

  Workaround: Apply these instructions on the golden image and then provision the desktop.

• 2481953: When you update the OS from Windows 1809 to 1903, you might see a black screen on Horizon Agent.

  Workaround: Apply the procedure in this KB article on the OS image. If Horizon Agent is installed on an RDS host, and the Printer Name for RDSH Agents group policy setting for the Integrated Printing feature is configured to use the client machine name as a suffix, the client machine name supports only English-language characters. If the client machine name contains characters in a non-English language, the Integrated Printing feature does not work in published desktops and published applications.

• 2591431, 2588938: Windows 10 2004 remote desktops respond very slowly when VBS is enabled.

  Workaround: None

• 2590496, 2588784: Updating the None guest customization to any other guest customization on a desktop pool causes existing virtual machines to go into an unreachable state after a reboot or power cycle operation.

  Workaround: In Horizon Console Desktop Pool settings, set the guest customization to None , then reboot the existing unreachable agent VMs.

• 2593663, 2589371: With Horizon desktops using Nvidia GRID, Windows 10 build 2004, PCoIP protocol, and in multi-monitor mode, some areas of the desktop might appear black and need to be manually refreshed.

  Workaround: Use Blast protocol if available, or continue using Windows 10 build 1909.

• 2590453, 2585527: Switching the agent desktop from window mode to multi-monitor mode with 4x4k monitors can sometimes take a few seconds.

  Workaround: None.

• 2539025, 2357111: HTML5 Multimedia Redirection does not work with an Edge browser in an IPv6 environment.

  Workaround: None.

• 2682571, 2672155: Remote desktops and published applications configured in Horizon 8 do not sync when using Workspace One Access Connector 19.03.0.1.

  Workaround: Revert to Workspace One version 19.03.0 and perform the sync operation again.

• 2770035, 2744714: HTML5 Multimedia Redirection does not work with https://www.glamour.com/video.

  Workaround: None.

• 2776478, 2708700: When the URL Content Redirection feature is configured, Horizon Client presents an alert message that asks you to change your default web browser to Horizon URL Filter for using third-party apps, not including the Chrome and Microsoft Edge (Chromium) browsers. You must click Yes to use the URL Content Redirection feature. In macOS 11 (Big Sur), even when you click Yes to the alert message, the Horizon URL Filter user interface is not shown in the default web browser of the general option, which means you cannot change the default web browser from another browser to Horizon URL Filter manually, and you must connect to the server again. In macOS 10, the user interface is shown in the default web browser of the general option. The URL Content Redirection extensions for the Chrome and Microsoft Edge (Chromium) browsers are not influenced by macOS 11.

  Workaround: None. This problem is a third-party issue.

• 2783745: If you disable the IE browser URL Plugin, enable the Edge browser URL Content Redirection extension, and input a URL in the IE mode of the Edge address bar, Edge stops responding.

  Workaround: None.

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.

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

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

• 2761441, 2739372: 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.

On-Premises Environments

• HZN-4839: Occasionally, the health check response for /favicon.ico may be delayed.

  Workaround: This issue can occur during periods of LDAP congestion. To mitigate it, consider adjusting the timing of LDAP backups. For more information, see Horizon Configuration Backup Settings.

  A permanent fix is planned for the Horizon 2512 release.

Use of Open Source

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

Key open-source components included in this release are:

• Horizon Connection Server 2506 is built on the Apache Tomcat implementation of Jakarta EE, version 10.1.43.
• Horizon Agent for Windows 2506, and Horizon Connection Server 2506 uses the BellSoft Liberica distribution of OpenJDK, version 17.0.15.0.1 (CPU).
• Horizon Agent for Linux 2506.1 and Horizon Agent for Windows 2506.1 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.