Setting Up for Linux Desktops
Table Of Contents
- Setting Up Horizon 7 for Linux Desktops
- Contents
- Setting Up Horizon 7 for Linux Desktops
- Features and System Requirements
- Preparing a Linux Virtual Machine for Desktop Deployment
- Setting Up Active Directory Integration for Linux Desktops
- Setting Up Graphics for Linux Desktops
- Installing Horizon Agent
- Configuration Options for Linux Desktops
- Create and Manage Linux Desktop Pools
- Bulk Deployment of Horizon 7 for Manual Desktop Pools
- Overview of Bulk Deployment of Linux Desktops
- Overview of Bulk Upgrade of Linux Desktops
- Create a Virtual Machine Template for Cloning Linux Desktop Machines
- Input File for the Sample PowerCLI Scripts to Deploy Linux Desktops
- Sample Script to Clone Linux Virtual Machines
- Sample Script to Join Cloned Virtual Machines to AD Domain
- Sample Script to Join Cloned Virtual Machines to AD Domain Using SSH
- Sample Script to Upload Configuration Files to Linux Virtual Machines
- Sample Script to Upload Configuration Files to Linux Virtual Machines Using SSH
- Sample Script to Upgrade Horizon Agent on Linux Desktop Machines
- Sample Script to Upgrade Horizon Agent on Linux Virtual Machines Using SSH
- Sample Script to Perform Operations on Linux Virtual Machines
- Troubleshooting Linux Desktops
- Collect Diagnostic Information for Horizon 7 for Linux Machine
- Troubleshooting Copy and Paste between Remote Desktop and Client Host
- Configuring the Linux Firewall to Allow Incoming TCP Connections
- View Agent Fails to Disconnect on an iPad Pro Horizon Client
- SLES 12 SP1 Desktop does not Auto Refresh after Drag and Drop
- SSO Fails to Connect to a PowerOff Agent
- Unreachable VM After Creating a Manual Desktop Pool for Linux
FIPS 140-2 Mode The Federal Information Processing Standard (FIPS) 140-2 mode support,
although not yet validated with the NIST Cryptographic Module Validation
Program (CMVP), is available beginning with Horizon 7 version 7.2.
The Horizon 7 Agent for Linux implements cryptographic modules that are
designed for FIPS 140-2 compliance. These modules were validated in
operational environments listed in CMVP certificate #2839 and #2866, and
were ported to this platform. However, the CAVP and CMVP testing
requirement to include the new operational environments in VMware's NIST
CAVP and CMVP certificates remains to be completed on the product
roadmap.
Note The Transport Layer Security (TLS) protocol version1.2 is required
to support FIPS 140-2 mode.
UDP Support for
VMware Blast Extreme
Beginning with the release of Horizon 7 version 7.3 for Linux desktop, the
User Datagram Protocol (UDP) is supported for VMware Blast Extreme and
is enabled by default. Initially, Blast Extreme only supported Transmission
Control Protocol (TCP).
If one of the inline components used does not support UDP, connections
will fall back to using TCP over UDP. For example, if your connection is
using the Blast Security Gateway component of the Horizon Connection
Server or Security Server, the connection uses TCP, even if both client and
agent enabled UDP, because Blast Security Gateway does not support
UDP. If users are connecting from outside the corporate network, the UDP
component requires the VMware Unified Access Gateway (formerly called
Access Point), which supports UDP.
Use the following information to establish a UDP-based Blast Extreme
connection.
n
If the client connects to a Linux desktop directly, enable the UDP in
both the client and agent. UDP is enabled by default in both the client
and agent.
n
If the client connects to a Linux desktop using Unified Access Gateway,
enable UDP in the client, agent, and Unified Access Gateway.
In a local area network (LAN), TCP performs better than UDP. You must
disable UDP in the client or agent if you want to continue using TCP. In a
wide area network (WAN), the UDP performance is better than the TCP
performance.
Setting Up Horizon 7 for Linux Desktops
VMware, Inc. 10