You can configure H.264 decoding and network condition options for remote desktop and application sessions that use the VMware Blast display protocol.
The maximum resolution that is supported depends on the capability of the graphical processing unit (GPU) on the client. A GPU that can support 4K resolution for JPEG/PNG might not support 4K resolution for H.264. If a resolution for H.264 is not supported, Horizon Client uses JPEG/PNG instead.
H.264 decoding is supported on AMD, NVIDIA, and Intel GPUs. H.264 decoding requires that the graphics library OpenGL 3.2 or later is installed for AMD and NVIDIA GPUs.
If you plan to use H.264 decoding with a NVIDIA GPU, install VDPAU (Video Decode and Presentation API for Unix). VDPAU is no longer included with the latest NVIDIA driver and must be installed separately.
mks.enableGLBasicRenderer = TRUEto /etc/vmware/config, /usr/lib/vmware/config, or ~/.vmware/config. The configuration files are processed in the following order:
H.264 is not supported on SLED 11 SP4 with Intel GPU because the xorg version is too old.
You cannot change the network condition option after you log in to a server. You can configure H.264 decoding before or after you log in to a server.
This feature requires Horizon Agent 7.0 or later.
- Select from the menu bar.
- Configure the decoding and network condition options.
Configure this option, before or after connecting to Connection Server, to allow H.264 decoding in Horizon Client.
When this option is selected (the default setting), 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 configure this option before connecting to Connection Server. Select one of the following network condition options:
Note: In Horizon 7 version 7.1 and earlier, Connection Server and Security Server instances do not support the BEAT Tunnel Server. Unified Access Gateway 2.9 and later supports the BEAT Tunnel Server.
- Excellent - Horizon Client uses only TCP networking. This option is ideal for a LAN environment.
- 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 setting.
- Poor - Horizon Client uses only BEAT networking if the BEAT Tunnel Server is enabled on the server, otherwise it switches to mixed mode.
Blast Security Gateway for Connection Server and Security Server instances do not support BEAT networking.
- Click OK to save your changes.
Changes for H.264 take effect the next time a user connects to a remote desktop or application and selects the VMware Blast display protocol. Your changes do not affect existing VMware Blast sessions.