Sometimes nested mode is used for zero clients or thin clients. When an end user logs in to a zero client, Horizon Client starts automatically and connects to a remote desktop. The user starts published applications from this remote desktop session. The remote desktop can be a virtual desktop or a published desktop.
To provide published applications, Horizon Client must be installed in the remote desktop. This setup is called nested mode because Horizon Client connects to a remote desktop that also has Horizon Client installed.
The remote desktop where both Horizon Client and Horizon Agent are installed is called the first-level remote desktop. The machine where only Horizon Client is installed is called the host.
The following operating systems are supported when running Horizon Client in nested mode.
Windows Server 2008 R2.
Windows Server 2012 R2.
Windows 7 Enterprise SP1.
All Windows 10 operating system versions that Horizon Client supports. See System Requirements for Windows Client Systems.
The following features are supported when a user uses Horizon Client in nested mode.
VMware Blast, PCoIP, and RDP display protocols
Single sign-on (without smart card)
URL Content Redirection
Log in as current user
Open local files in published applications
The following features have certain limitations in nested mode.
For the USB redirection feature to work in nested mode, the first-level remote desktop must be a virtual desktop. Published desktops are not supported.
With USB redirection in nested mode, only the following USB devices are supported: TOPAZ Signature Pad, Olympus Dictation Foot pedal, and Wacom signature pad.
When opening local files in published applications in nested mode, you can open files from the first-level remote desktop in a second-level published application. You cannot open files on the host in a second-level published application.