Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
VMware supports running the Horizon Client inside a Horizon VM. This flow, commonly called “nested mode,” involves two hops. However, not all combinations or features are validated by VMware. This document is intended to clarify what has been verified. This KB has been updated for Horizon 8. Introduction An end user logs in to a physical end point machine and uses the Horizon Client to connect to a Windows remote desktop, which can be a virtual desktop or a published desktop. Inside that remote desktop, he then launches the Horizon Client and connects to a Horizon published desktop or remote applications from this remote desktop session. This setup is called nested mode because the Horizon Client connects to a remote desktop that also has Horizon Client installed.In this document, we will be using the terminology in the below diagram for precision.
Terms virtual Desktop: VDI desktop running on vSpherepublished desktop: RDSH desktopendpoint: physical machine where the Horizon Client is installedfirst Hop remote desktop: The remote desktop where both Horizon Client and Horizon Agent are installed.second-hop remote desktop/application: The published desktop/published application or virtual desktop the second-hop client (client 2) connects to A1,A2: Agent 1, Agent 2C1, C2: Client 1, Client 2 What Is Validated? The below table shows what combinations are validated in nested mode. Limitations are marked with a notation. Feature ListEndpointFirst-hop Remote DesktopSecond-hop Remote Desktop/ApplicationClient [10] [12]Protocol 1 [6]Validated OS [7]Agent 1/Client 2Protocol 2 [6]Validated OSBasic Connections [1]Horizon Client for WindowsBlast,PCoIP Win10 x 64[15]Win11 x64 Windows Server VDI[11]Windows Server RDSH Desktop[14] Horizon Agent/Horizon Client for WindowsBlast,PCoIP Win10 x64[15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 10 VM Hosted App [8]Windows 11 VM Hosted App Horizon Client for LinuxBlast,PCoIP Win10 x 64[15]Win11 x64 Windows Server VDI[11]Windows Server RDSH Desktop[14] Horizon Agent/Horizon Client for WindowsBlast,PCoIP Win10 x64[15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 10 VM Hosted App [8]Windows 11 VM Hosted App Horizon Client for MacBlast,PCoIP Win10 x 64[15]Win11 x64 Windows Server VDI[11]Windows Server RDSH Desktop[14] Horizon Agent/Horizon Client for WindowsBlast,PCoIP Win10 x64[15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 10 VM Hosted App [8]Windows 11 VM Hosted App Real-Time Audio-Video (RTAV)Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent/Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Horizon Client for LinuxBlast, PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent/Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Horizon Client for MacBlast, PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent/Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Log in as Current User(LACU)Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent /Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server RDSH Desktop [14]Windows 10 VM Hosted App [8] Passthrough information in nested mode for EPIC [9]Horizon Client for WindowsBlast, PCoIp Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent /Horizon Client for WindowsBlast, PCoIP Windows Server RDSH App [13]Windows Server RDSH Desktop [14]Windows 10 VM Hosted App [8] URL Content Redirection Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server RDSH Desktop [14]Windows 10 VM Hosted App [8] HTML5 MMR [2]Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64 Horizon Agent / Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13] Audio OutHorizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Horizon Client for LinuxBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Clipboard Redirection [3]Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server RDSH Desktop [14]Windows 10 VM Hosted App [8] Horizon Client for LinuxBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server RDSH Desktop [14]Windows 10 VM Hosted App [8] Localization based PrintingHorizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Horizon Client for LinuxBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Horizon Client for MacBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App USB Redirection [4]Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11] Horizon Agent / Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Horizon Client for LinuxBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11] Horizon Agent / Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Horizon Client for MacBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11] Horizon Agent / Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App File Association (Open local files in published application) [5]Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast,PCoIP Windows Server RDSH App [13]Windows 10 VM Hosted App [8] Horizon Client for LinuxBlast,PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast,PCoIP Windows Server RDSH App [13]Windows 10 VM Hosted App [8] Serial RedirectionHorizon Client for WindowsBlastWindows Server RDSH Desktop [14]Horizon Agent / Horizon Client for WindowsBlast Windows Server RDSH App [13]Windows Server RDSH Desktop [14] Horizon Client for LinuxBlastWindows Server RDSH Desktop [14]Horizon Agent / Horizon Client for WindowsBlast Windows Server RDSH App [13]Windows Server RDSH Desktop [14]Windows 10 VM Hosted App [8] Scanner RedirectionHorizon Client for WindowsBlastWindows Server RDSH Desktop [14]Horizon Agent / Horizon Client for WindowsBlast Windows Server RDSH App [13]Windows Server RDSH Desktop [14] Horizon Client for LinuxBlastWindows Server RDSH Desktop [14]Horizon Agent / Horizon Client for WindowsBlast Windows Server RDSH App [13]Windows Server RDSH Desktop [14]Windows 10 VM Hosted App [8] VMware Integrated PrintingHorizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Horizon Client for LinuxBlast, PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast, PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App Horizon Client for LinuxBlast, PCoIP Win10 x64 [15]Win11 x64 Windows Server VDI [11]Windows Server RDSH Desktop [14] Horizon Agent / Horizon Client for WindowsBlast,PCoIP Win10 x64 [15]Win11 x64Windows Server RDSH App [13]Windows Server VDI [11]Windows Server RDSH Desktop [14]Windows 11 VM Hosted App [1] Basic connection under nested mode refers to the connection from C1 to A1/C2 and C2 to A2 with the same protocol. Single Sign On is supported from C1 to A1. But when the user connects to C2, she will have to authenticate again. No smart card support on A1/C2. Basic keyboard and mouse operations will work and also basic display with one monitor and no DPI sync for second-hop.[2] URL content redirection in nested works from C1 to A2 or from A2 to C1, and it depends on installation configuration. It can't work bidirectionally under one installation configuration. HTML5MMR in nested works from A1 to C1 or from A2 to C2, and it depends on installation configuration. For installation instructions, please refer to Installation, Uninstallation and Upgrade below.[3] To make clipboard redirection work between C1 and A2, the end users must first direct the input focus to A1/C2 desktop as a bridge. For example, if the end user wants to copy some text from C1 to A2, the steps are: (1) copy the text at C1; (2) move mouse to A1/C2 for input focus, e.g. click the desktop; (3) paste the text to A2.[4] For the USB redirection feature to work in nested mode, the first-hop remote desktop must be a VDI. RDSH desktops are not supported. The following USB devices have been tested and verified: USB storage, TOPAZ Signature Pad, Wacom signature pad and Olympus Dictation Foot pedal. [5] When opening local files in published applications in nested mode, you can open files from the first-hop remote desktop with a second-hop published application. You cannot open files on the endpoint in a second-hop published application.[6] Protocol 1 and Protocol 2 should either both be Blast or PCoIP.[7] Win10 supported version follows the Horizon Agent and Client's support list. We recommend customers to deploy the Win10 versions in this table that we’ve tested and verified. [8] Windows 10 VM Hosted App indicates that the virtual application is being hosted from vSphere running a VM with Windows 10 Enterprise 2016 LTSB, Windows 10 64-bit Enterprise version 1809 and later. [9] For how to passthough client information in a nested session, please refer to the "Disallow passing through client information in a nested session" section in this documentation link . [10] Windows 10 endpoint OS support includes the X64-bit versions of Home, Pro, Pro for Workstations, Enterprise, Internet of Things (IoT) Enterprise, and Education. Thin client vendors often customize Windows 10, so check the client compatibility matrix for additional information. For more information, see https://www.vmware.com/resources/compatibility/search.php?deviceCategory=vdm.[11] Windows Server VDI includes support for Windows Server 2022, Windows Server 2012 R2, Windows Server 2016 and Windows Server 2019[12] For the Horizon Client for Linux and the Horizon Client for Mac, refer to the client documentation to find the supported OS versions.[13] Windows Server RDSH Apps includes support for Windows Server 2022, Windows Server 2012 R2, Windows Server 2016 and Windows Server 2019[14] Windows Server RDSH Desktop includes support for Windows Server 2022,, Windows Server 2012 R2, Windows Server 2016 and Windows Server 2019[15] Win10 x64 includes both Windows 10 Enterprise x64 and Windows 10 Pro x64. Setting up the Remote Desktop The remote desktop running the agent and client (A1 & C2) must be configured carefully. Below are instructions on supported version numbers and install instructions. Supported version mapping of Horizon Client and Horizon Agent Beginning with the 2106 release, it is no longer required that A1 and C2 be the exact same version. We now support A1 and C2 when they match or when they are off by a version. In other words, in the first hop desktop, you can run the Horizon Agent 2111 with the Horizon Client 2111 or the Horizon Client 2106. Similarly the first hop desktop could also be the Horizon Agent 2106 running the Horizon Client 2106 or the Horizon Client 2111. Horizon Client that ships with Horizon 8 and follows a year-month version number is backwards compatible with Horizon 7. However to use Horizon 8 you must have a newer client, you cannot use a 5.X Horizon Client. For this reason, we support the following: First hop A1 Horizon 7 Agent/C2 Client 5.X; second hop A2 Horizon 7 AgentFirst hop A1 Horizon 8 Agent/C2 Client YYMM; second hop A2 Horizon 7 AgentFirst hop A1 Horizon 8 Agent/C2 Client YYMM; second hop A2 Horizon 8 Agent However, this combination is not supported: First hop A1 Horizon 7 Agent/C2 Client 5.X; second hop A2 Horizon 8 Agent In addition, beginning with the 2312 Horizon ESB release, an ESB Agent will be supported with all future Client releases( in nested mode) until a new ESB release is available. This will provide additional flexibility and will remove dependency on frequent Client upgrades. As an example, let's assume the next ESB version is called 2412. So 2312 Agents will be supported with every future Client release until the next ESB release (2412) is available. At that point, 2312 Agents will not be supported with 2412 Client and beyond Client releases. Note that this applies to only nested mode. Installation, Uninstallation and Upgrade Beginning with Horizon 8 2106, you can install, uninstall, or upgrade A1 and C2 in any order.However, consider the following if you’re using the URL content redirection feature in nested mode (applicable to all Horizon versions).URL Content Redirection: To redirect URL content from C1 to A2: Install the URL Content Redirection feature during client installation for both C1 and C2.Do not run it during agent installation on A1 (even if it’s installed with A2). To redirect URL content from A2 to C1: Install the URL Content Redirection feature during agent installation for both A1 and A2.Do not install it with the client on C2 (even if it’s part of C1’s client install) IP Rules and Browser: If configuring URL redirection with IP Rules, ensure that Internet Explorer (IE) Mode is enabled in Microsoft Edge (Chromium) and Edge is the default web browser on the A1/C2 machine. Below requirements must be followed to have double-hop work properly for any versions earlier than Horizon 8 2106: A1 must be installed before C2 Uninstallation: C2 must be uninstalled first, then uninstall Agent 1Upgrade: A1/ C2 upgrade is NOT supported. If you want to use a newer version of A1/C2, you need to uninstall the previous C2 and A1, then kick off a fresh install the new A1 then C2For URL Content Redirection, see above listed instructions What Is Not Supported Multiple hops beyond 2 is not supported.The supported systems in this document pertain to Horizon Client for Windows, Horizon Client for Linux and Horizon Agent. Many VMware partners offer thin and zero client devices, or other system integration for Horizon deployments. Double-hop features supported for each thin or zero client device and other 3rd-party systems are determined by the vendor and the configuration that an enterprise chooses to use. For information about features supported in these client devices and systems, please consult the specific vendors and refer to the VMware Compatibility Guide, which is available on the VMware web site. Horizon Cloud Service on Azure supports nested mode but only for Basic Connection [1].It is not supported to use different remote protocols for the two hops. 32-bit OSes (for C1(Windows 10), A1/C2, A2) are not supported.Double-hop is tested under standard Horizon configuration (IPv4, non-FIPS), not under complex environments such as IPv6, FIPS, VBS, VGPU etc. Non-standard environments are not recommended. Mixed usage of remote redirection features in nested mode is not supported. For example, sharing a scanner from C1 to A1 using USB redirection but then switching to scanner redirection from C2 to A2; or using USB redirection from C1 to A1 followed by serial redirection to an RDSH app is not supported. Both hops must use the same redirection method: USB device - both hops use USB; scanners - both hops use scanner redirection; serial devices - both hops use serial redirection.For scanner, printer, serial devices, we don’t recommend USB redirection in either nested or non-nested mode. Any latency on the network will lead to errors.Keylogger Blocking . With the client and agent software installed together on a machine, key input is not protected.
For more information on supported nested functionality for Horizon 7, see VMware Horizon Guidelines for Nested ModePage last reviewed: October 2023Next review due: December 2023