Installation and Setup Guide

Considerations for Nested Sessions
In a nested mode or double-hop scenario, a user connects from their physical client system to a remote
desktop, launches Horizon Client inside the remote desktop (the nested session), and connects to another
remote desktop. In this scenario, you must congure the USB policy seings in the same way on both the
physical client machine and in the nested session to make the device work as expected in the nested session.
PCoIP Client Session Variables ADMX Template Settings
The PCoIP Client Session Variables ADMX template le (pcoip.client.admx) contains policy seings related
to the PCoIP display protocol. You can congure seings to computer default values that can be overridden
by an administrator, or you can congure user seings to values that cannot be overridden. The seings that
can be overridden are in the PCoIP Client Session Variables > Overridable Administrator Defaults folder
in the Group Policy Management Editor. The seings that cannot be overridden are in the PCoIP Client
Session Variables > Not Overridable  folder in the Group Policy Management Editor.
The ADMX les are available in a bundled .zip le named VMware-Horizon-Extras-Bundle-x.x.x-
yyyyyyy.zip, which you can download from the VMware download site at
hps://my.vmware.com/web/vmware/downloads. Under Desktop & End-User Computing, select the
VMware Horizon 7 download, which includes the bundled .zip le.
Table 3‑10. PCoIP Client Session Variables
Setting Description
Configure PCoIP
client image cache
size policy
Controls the size of the PCoIP client image cache. The client uses image caching to store
portions of the display that were previously transmied. Image caching reduces the amount
of data that is retransmied.
When this seing is not congured or when it is disabled, PCoIP uses a default client image
cache size of 250MB.
When you enable this seing, you can congure a client image cache size from a minimum
of 50 MB to a maximum of 300 MB. The default value is 250MB.
Configure PCoIP event
log cleanup by size
in MB
Enables the conguration of the PCoIP event log cleanup by size in MB. When this seing is
congured, it controls the log le cleanup by size in MB. For example, for a non-zero seing
of m, log les larger than m MB are silently deleted. A seing of 0 indicates no le cleanup
by size. When this seing is disabled or not congured, the default event log cleanup by size
in MB seing is 100.
Configure PCoIP event
log cleanup by time
in days
Enables the conguration of the PCoIP event log cleanup by time in days. When this seing
is congured, it controls the log le cleanup by time in days. For example, for a non-zero
seing of n, log les older than n days are silently deleted. A seing of 0 indicates no le
cleanup by time. When this policy is disabled or not congured, the default event log
cleanup by time in days seing is 7.
The log le cleanup is performed once at session startup. Any change to the seing is be
applied until the next session.
Configure PCoIP event
log verbosity
Sets the PCoIP event log verbosity. The values range from 0 (least verbose) to 3 (most
verbose).
When this seing is enabled, you can set the verbosity level from 0 to 3. When the seing is
not congured or disabled, the default event log verbosity level is 2.
When this seing is modied during an active PCoIP session, the new seing takes eect
immediately.
VMware Horizon Client for Windows Installation and Setup Guide
60 VMware, Inc.