User manual

Table 3‑10. PCoIP Client Session Variables (Continued)
Setting Description
Configure the PCoIP
session bandwidth
floor
Species a lower limit, in kilobits per second, for the bandwidth that is reserved by the
PCoIP session.
This seing congures the minimum expected bandwidth transmission rate for the
endpoint. When you use this seing to reserve bandwidth for an endpoint, the user does not
have to wait for bandwidth to become available, which improves session responsiveness.
Make sure that you do not over-subscribe the total reserved bandwidth for all endpoints.
Make sure that the sum of bandwidth oors for all connections in your conguration does
not exceed the network capability.
The default value is 0, which means that no minimum bandwidth is reserved. When this
seing is disabled or not congured, no minimum bandwidth is reserved.
This seing applies to the agent and the client, but the seing only aects the endpoint on
which it is congured.
When this seing is modied during an active PCoIP session, the change takes eect
immediately.
Configure the PCoIP
session MTU
Species the Maximum Transmission Unit (MTU) size for UDP packets for a PCoIP session.
The MTU size includes IP and UDP packet headers. TCP uses the standard MTU discovery
mechanism to set MTU and is not aected by this seing.
The maximum MTU size is 1500 bytes. The minimum MTU size is 500 bytes. The default
value is 1300 bytes.
Typically, you do not have to change the MTU size. Change this value if you have an
unusual network setup that causes PCoIP packet fragmentation.
This seing applies to the agent and the client. If the two endpoints have dierent MTU size
seings, the lowest size is used.
If this seing is disabled or not congured, the client uses the default value in the
negotiation with the agent.
Configure SSL
connections to
satisfy Security
Tools
Species how SSL session negotiation connections are established. To satisfy security tools,
such as port scanners, enable this seing and do the following:
1 Store the certicate for the Certicate Authority that signed any Server certicate to be
used with PCoIP in the Trusted Root certicate store.
2 Congure the agent to load certicates only from the Certicate Store. If the Personal
store for the Local Machine is used, leave the CA Certicate store name unchanged with
the value ROOT, unless a dierent store location was used in step 1.
If this seing is disabled or not congured, the AES-128 cipher suite is not available and the
endpoint uses Certication Authority certicates from the machine account's MY store and
Certication Authority certicates from the ROOT store.
Configure SSL
protocols
Congures the OpenSSL protocol to restrict the use of certain protocols before establishing
an encrypted SSL connection. The protocol list consists of one or more OpenSSL protocol
strings separated by colons. All cipher strings are case insensitive.
The default value is TLS1.1:TLS1.2, which means that TLS v1.1 and TLS v1.2 are enabled
and SSL v2.0, SSLv3.0, and TLS v1.0 are disabled.
If this seing is set in both the client and the agent, the OpenSSL protocol negotation rule is
followed.
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 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.
Using VMware Horizon Client for Windows
60 VMware, Inc.