Horizon Client for Windows 2503 | 15 APR 2025$$$With Horizon® Client™ for Windows 2503; you can access remote desktops and published applications from your Windows computer with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).$$$$$$What’s New$$$Horizon Client for Windows is released along with the Horizon 8 2503 release.$$$$$$Before You Begin$$$For the Windows operating systems that this release of Horizon Client for Windows supports; see the Horizon Client for Windows Guide.$$$$$$Horizon Client for Windows is supported with the latest maintenance release of the following deployment types:$$$$$$Omnissa Horizon 8 version 2006 and later$$$$$$Omnissa Horizon Cloud Service - Next-Gen$$$$$$Horizon Cloud in Microsoft Azure$$$$$$To use Horizon Client in FIPS mode; you must use Connection Server version 2309 or later; if using Unified Access Gateway; you must also use Unified Access Gateway 2309 or later. For more information; see Omnissa Knowledge Base (KB) article 95144.$$$$$$To install Horizon Client for Windows; download the installer from the Horizon Clients download page.$$$$$$For installation instructions; see the Horizon Client for Windows Guide.$$$$$$For information about the features that are supported in nested mode; see Omnissa Knowledge Base article 80509; “Horizon Guidelines for Nested Mode.”$$$$$$Limitations$$$This release may not work with existing Zoom; Cisco; Nuance; and Imprivata integrations.$$$$$$Resolved Issues$$$There are no major issue resolutions to report in this release.$$$$$$Known Issues$$$Horizon Client for Windows Auto-Update The auto-update for Horizon Client for Windows versions 2406.1 (8.13.1) or earlier to 2503 will not work.$$$$$$Workaround: Perform a two-step upgrade. You need to be on a minimum version of 2406.1 (8.13.1) to auto-update Horizon Client for Windows. The auto-update for Horizon Client for Windows versions 2406.1 (8.13.1) and later to the 2503 Omnissa-branded Client for works.$$$$$$UDP and IPv6 conflict$$$UDP-only mode does not work in IPv6 environments.$$$$$$Workaround: None.$$$$$$Enable Relative Mouse feature does not work on touch-enabled screen$$$If you use a touch-enabled screen on your client system to work in a remote desktop; do not use the Enable Relative Mouse feature. This feature provides improved mouse performance for 3D and CAD applications; but for touch-enabled screens and tablets; the mouse coordinates are not translated properly; even in 3D and CAD applications.$$$$$$Workaround: None.$$$$$$Tax issues for IBM Credit Memos$$$N/A$$$$$$Remote application launches and displays a black area after legal notice confirmation$$$After confirming the legal notice; the remote application launches and displays a black area in the UI.$$$$$$Workaround: Disconnect then reconnect the remote application.$$$$$$Keylogger blocking does not work in nested sessions$$$When users attempt to open a nested session in which both the host and guest desktops have keylogger blocking enabled and all required drivers installed; the connection is denied.$$$$$$Workaround: None.$$$$$$When a remote desktop is reconnected; Powermic Speechmic does not work with DMO 2022.2$$$When a remote desktop is reconnected after being disconnected; Powermic device does not work with dictation on DMO 2022.2. This happens when using a USB split and RTAV solution.$$$$$$Workaround: Use Nuance extension to redirect Powermic devices on the remote desktop.$$$$$$Horizon Client for Windows quits when launching a remote desktop$$$Horizon Client for Windows might quit unexpectedly when launching a remote desktop with multiple monitors at a high resolution.$$$$$$Workaround : Check the supported multiple monitor configurations in the documentation to resolve this issue. If you still encounter this issue; consider the following workarounds:$$$$$$Configure your monitor layout so that it’s not very wide or very tall (for example; use a tile/matrix layout instead of using single row/column of monitors).$$$$$$Try not to launch multiple desktops with mult

Horizon Client for Windows 2412 | 23 DEC 2024$$$With Horizon® Client™ for Windows 2412; you can access remote desktops and published applications from your Windows computer with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).$$$$$$What’s New$$$Horizon Client for Windows 2412 includes the following new features:$$$$$$Omnissa branding$$$The Horizon Client user interface; configuration strings; and file paths have been updated to reflect the new Omnissa brand.$$$$$$OS support$$$Horizon Client is supported on Windows 11 2024 Update (also known as Windows 11; version 24H2) and Windows 11 Enterprise LTSC 2024. This release removes support for the following Windows 11 versions: Enterprise 21H2; IoT Enterprise 21H2; and Education 21H2.$$$$$$Improved session stability$$$This release provides stability improvements when running desktop and application sessions.$$$$$$Lock the Server URL option$$$The new Lock the Server URL option in the Server URL GPO policy allows you to control whether the Server URL policy takes priority over other server connection settings during client login.$$$$$$Autoconnect icon in server list$$$The server list window now displays an “A” icon to indicate the server specified by the Autoconnect to This Server setting.$$$$$$Access to Horizon Cloud Service - next-gen from networks without internet access$$$Horizon Client supports private connections to Horizon Cloud Service - next-gen using a private brokering endpoint through an ExpressRoute or VPN connection.$$$$$$Improved user experience with keylogger blocking$$$This release provides several enhancements that make the keylogger blocking feature easier to use. Horizon Client automatically turns on keylogger blocking whenever a remote session requires the feature. Horizon Client also displays assistance screens to guide users through any restart operations needed for the feature.