User manual

2 Congure the decoding and network condition options.
Option Action
H.264
Congure this option, before or after connecting to Connection Server, to
allow H.264 decoding in Horizon Client.
When this option is selected (the default seing), Horizon Client uses H.
264 decoding if the agent supports H.264 software or hardware encoding.
If the agent does not support H.264 software or hardware encoding,
Horizon Client uses JPG/PNG decoding.
Deselect this option to use JPG/PNG decoding.
Select your network condition for
the best experience
You can only congure this option before connecting to Connection Server.
Select one of the following network condition options:
n
Excellent - Horizon Client uses only TCP networking. This option is
ideal for a LAN environment.
n
Typical (default) - Horizon Client works in mixed mode. In mixed
mode, Horizon Client uses TCP networking when connecting to the
server and uses Blast Extreme Adaptive Transport (BEAT) if the agent
and Blast Security Gateway (if enabled) support BEAT connectivity.
This option is the default seing.
n
Poor - Horizon Client uses only BEAT networking if the BEAT Tunnel
Server is enabled on the server, otherwise it switches to mixed mode.
N In Horizon 7 version 7.1 and earlier, Connection Server and
Security Server instances do not support the BEAT Tunnel Server. VMware
Access Point 2.9 and later supports the BEAT Tunnel Server.
Blast Security Gateway for Connection Server and Security Server
instances do not support BEAT networking.
3 Click OK to save your changes.
Changes for H.264 take eect the next time a user connects to a remote desktop or application and selects
the VMware Blast display protocol. Your changes do not aect existing VMware Blast sessions.
Using Internet Explorer Proxy Settings
Horizon Client automatically uses proxy seings congured in Internet Explorer.
Bypassing Proxy Settings
Horizon Client uses the Internet Explorer proxy bypass seings to bypass HTTPS connections to a
Connection Server host, security server, or Access Point appliance.
If the secure tunnel is enabled on the Connection Server host, security server, or Access Point appliance, you
must use the Tunnel proxy bypass address list group policy seing in the Horizon Client Conguration
ADM or ADMX template le to specify a list of addresses to bypass the tunnel connection. The proxy server
is not used for these addresses. Use a semicolon (;) to separate multiple entries. This group policy seing
creates the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\VMware, Inc.\VMware VDM\Client\TunnelProxyBypass
You cannot use this group policy seing for direct connections. If applying the group policy seing does not
work as expected, try bypassing the proxy for local addresses. For more information, see
hps://blogs.msdn.microsoft.com/askie/2015/10/12/how-to-congure-proxy-seings-for-ie10-and-ie11-as-
iem-is-not-available/.
Proxy Fail Over
Horizon Client supports proxy fail over with the Use automatic  script seing under
Automatic  in Internet Options > Connections > LAN  in Internet Explorer. To use this
seing, you must create an automatic conguration script that returns multiple proxy servers.
Chapter 1 System Requirements and Setup for Windows-Based Clients
VMware, Inc. 21