VMware Horizon 7.4 Quick Start Guide

Setting Up Horizon 7 for
Linux Desktops

Modified on 4 JAN 2018
VMware Horizon 7 7.4

Setting Up Horizon 7 for Linux Desktops

You can find the most up-to-date technical documentation on the VMware website at:

https://docs.vmware.com/

If you have comments about this documentation, submit your feedback to

[e-mail]

VMware, Inc.

3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com

Copyright © 2016, 2018 VMware, Inc. All rights reserved. Copyright and trademark information.

VMware, Inc. 2

Contents

Setting Up Horizon 7 for Linux Desktops 5

Features and System Requirements 6

1

Features of Horizon Linux Desktops 6

Overview of Configuration Steps for Horizon 7 for Linux Desktops 12

System Requirements for Horizon 7 for Linux 13

Preparing a Linux Virtual Machine for Desktop Deployment 25

2

Create a Virtual Machine and Install Linux 25

Prepare a Linux Machine for Remote Desktop Deployment 26

Install Dependency Packages for Horizon Agent 28

Setting Up Active Directory Integration for Linux Desktops 30

3

Integrating Linux with Active Directory 30

Setting Up Single Sign-on and Smart Card Redirection 33

Setting Up Graphics for Linux Desktops 36

4

Configure Supported RHEL Distributions for vGPU 36

Configure RHEL 6 for vDGA 42

Configure RHEL 7 for vSGA 46

Installing Horizon Agent 50

5

Install Horizon Agent on a Linux Virtual Machine 50

Configure the Certificate for Linux Agent 53

Upgrading the Horizon Agent on a Linux Virtual Machine 54

Uninstall Horizon 7 for Linux Machines 56

Configuration Options for Linux Desktops 57

6

Setting Options in Configuration Files on a Linux Desktop 57

Example Blast Settings for Linux Desktops 66

Examples of Client Drive Redirection Options for Linux Desktops 66

Suppress the vSphere Console Display of a Linux Desktop 67

Create and Manage Linux Desktop Pools 68

7

Create a Manual Desktop Pool for Linux 68

Manage Desktop Pool for Linux 69

Create an Automated Full-Clone Desktop Pool for Linux 71

Create an Instant-Clone Floating Desktop Pool for Linux 73

VMware, Inc.

3

Setting Up Horizon 7 for Linux Desktops

Broker PowerCLI Commands 76

Bulk Deployment of Horizon 7 for Manual Desktop Pools 79

8

Overview of Bulk Deployment of Linux Desktops 79

Overview of Bulk Upgrade of Linux Desktops 81

Create a Virtual Machine Template for Cloning Linux Desktop Machines 82

Input File for the Sample PowerCLI Scripts to Deploy Linux Desktops 84

Sample Script to Clone Linux Virtual Machines 84

Sample Script to Join Cloned Virtual Machines to AD Domain 88

Sample Script to Join Cloned Virtual Machines to AD Domain Using SSH 91

Sample Script to Upload Configuration Files to Linux Virtual Machines 95

Sample Script to Upload Configuration Files to Linux Virtual Machines Using SSH 98

Sample Script to Upgrade Horizon Agent on Linux Desktop Machines 103

Sample Script to Upgrade Horizon Agent on Linux Virtual Machines Using SSH 107

Sample Script to Perform Operations on Linux Virtual Machines 113

Troubleshooting Linux Desktops 117

9

Collect Diagnostic Information for Horizon 7 for Linux Machine 117

Troubleshooting Copy and Paste between Remote Desktop and Client Host 118

Configuring the Linux Firewall to Allow Incoming TCP Connections 118

View Agent Fails to Disconnect on an iPad Pro Horizon Client 118

SLES 12 SP1 Desktop does not Auto Refresh after Drag and Drop 119

SSO Fails to Connect to a PowerOff Agent 119

Unreachable VM After Creating a Manual Desktop Pool for Linux 119

VMware, Inc. 4

Setting Up Horizon 7 for Linux Desktops

The Setting Up Horizon 7 for Linux Desktops document provides information about setting up a Linux
virtual machine for use as a VMware Horizon® 7 desktop, including preparing the Linux guest operating
system, installing Horizon Agent on the virtual machine, and configuring the machine in View
Administrator for use in a Horizon 7 deployment.

Intended Audience

This information is intended for anyone who wants to configure and use remote desktops that run on
Linux guest operating systems. The information is written for experienced Linux system administrators
who are familiar with virtual machine technology and datacenter operations.

VMware, Inc.

5

Features and System

Requirements 1

With Horizon 6 or later, users can connect to remote desktops that run the Linux operating system.

This chapter includes the following topics:

n

Features of Horizon Linux Desktops

n

Overview of Configuration Steps for Horizon 7 for Linux Desktops

n

System Requirements for Horizon 7 for Linux

Features of Horizon Linux Desktops

Horizon 7 version 7.4 introduces several new features for Linux desktops.

The following new features are supported beginning with Horizon 7 version 7.4 release.

n

Creation of a Linux-based desktop pool with an instant-clone floating desktop pool. This feature is
supported only on Ubuntu 14.04 and 16.04 systems.

n

Integration of Linux desktops with Active Directory using PowerBroker Identity Services Open
(PBISO). This feature is supported only on Ubuntu 14.04 and 16.04 systems.

n

Support of SUSE Linux Enterprise Server and Desktop 12 SP3.

n

Support of the 3Dconnexion mouse.

VMware, Inc.

6

Setting Up Horizon 7 for Linux Desktops

The following list presents the key features for Horizon Linux Desktops.

Active Directory

Integration with PBIS

Open

Beginning with Horizon 7 version 7.4 release, Linux-based desktops can
authenticate with Active Directory using PowerBroker Identity Services
Open (PBISO). This feature is supported only on Ubuntu 14.04 and 16.04
systems. See the PowerBroker Identity Services Open (PBISO)
Authentication section in Integrating Linux with Active Directory for more
information.

Instant-Clone Floating

Desktop Pool

Beginning with Horizon 7 version 7.4 release, you can create instant-clone
floating desktop pools for Linux desktops. This feature is supported only on
Ubuntu 14.04 and 16.04 systems. For more information, see Create an

Instant-Clone Floating Desktop Pool for Linux.

Note A Linux VDI instant-clone agent has a 4096x4096 resolution

limitation.

Automated Full-Clone

Desktop Pool

Beginning with Horizon 7 version 7.0.2 release, you can create automated
full-clone desktop pools for Linux desktops.

Manual Desktop Pool Machine source.

n

Managed Virtual Machine - Machine source of the vCenter virtual
machine. A managed virtual machine is supported for new and upgrade
deployment.

Multiple Monitors

n

Unmanaged Virtual Machine - Machine source of other sources. An
unmanaged virtual machine is only supported when the upgrade is from
an unmanaged virtual machine deployment.

Note To ensure the best possible performance, do not use an unmanaged

virtual machine.

n

vDGA/vGPU desktop supports a maximum resolution of 2560x1600 on
four monitors.

n

2D/vSGA desktop on VMware vSphere® 6.0 or later supports a
maximum resolution of 2048x1536 on four monitors or a maximum
resolution of 2560x1600 on three monitors.

For Ubuntu 14.04/16.04, you must use Gnome, KDE, or the MATE desktop
environment to use the multiple monitors feature. See

http://kb.vmware.com/kb/2151294 for more information.

VMware, Inc. 7

Setting Up Horizon 7 for Linux Desktops

For SLES 12 SP1, you must use the default package with kernel level
kernel-default-3.12.49-11.1. If you upgraded the package, the multi-monitor
feature fails and the desktop is shown in one monitor.

VMware Horizon HTML Access does not support the multi-monitor feature
in Horizon 7 for Linux desktops.

Lossless PNG Images and videos that are generated on a desktop are rendered on the

client device in a pixel-exact manner.

H.264 Encoder

H.264 can improve the Blast Extreme performance for a Horizon desktop,
especially under a low-bandwidth network. If the client side disabled H.264,
Blast Extreme automatically falls back to JPEG/PNG encoding.

From Horizon 7 version 7.3 for Linux release, hardware H.264 encoder
support is added with the software H.264 encoder support. The hardware
H.264 support has the following requirements.

n

The vGPU is configured with the NVIDIA graphics card.

n

The NVIDIA driver 384 series or later is installed in the NVIDIA
graphics card.

When the system meets the preceding requirements, Horizon 7 for Linux
uses the hardware H.264 encoder. Otherwise, the software H.264 encoder
is used.

3D Graphics 3D graphics is supported with the following combinations of Linux versions

and graphics cards:

n

vSGA is supported on RHEL 7 Workstation x64 with NVIDIA GRID K1
or K2 graphics cards.

n

vDGA is supported on RHEL 6 Workstation x64 with NVIDIA GRID K1
or K2 graphics cards.

n

vGPU is supported on RHEL 6 Workstation x64 with NVIDIA Maxwell
M60 graphics cards.

n

vGPU is supported on RHEL 7 Workstation x64 with NVIDIA Maxwell
M60 graphics cards.

n

vGPU is supported on RHEL 6 Workstation x64 with NVIDIA M6
graphics cards.

n

vGPU is supported on RHEL 7 Workstation x64 with NVIDIA M6
graphics cards.

3Dconnexion Mouse The 3Dconnexion mouse is supported beginning with Horizon 7 version 7.4

for Linux release. To begin using your 3Dconnexion mouse, you must install
the appropriate device driver and pair the mouse using the Connect USB
Device menu on your Linux desktop.

VMware, Inc. 8

Setting Up Horizon 7 for Linux Desktops

Clipboard Redirection With the clipboard redirection feature, you can copy and paste a rich text or

a plain text between a client host and a remote Linux desktop. You can set
the copy/paste direction and the maximum text size using Horizon Agent
options. This feature is enabled by default. You can disable it during
installation.

Single Sign-on Single sign-on (SSO) is supported on the following Linux distributions.

n

RHEL 6/7 Workstation x64

n

CentOS 6/7 x64

n

SLED 11 SP3/SP4 x64

n

Ubuntu 14.04/16.04 x64

Smart Card Redirection

with SSO

Smart card redirection is supported on RHEL 6 Workstation x64. Personal
Identity Verification (PIV) cards and Common Access Cards (CAC) are
supported. Mac client is not supported.

Audio-in Audio input redirection from a client host to a remote Linux desktop is

supported. This feature is not based on the USB redirection function. If you
want this feature enabled, you must select it during installation. You must
select the system default audio in device "PulseAudio server (local)" in your
application for the audio input. This feature is supported on the following
Linux distributions.

n

Ubuntu 14.04 x64 with MATE, KDE, or Gnome Fallback (Metacity)
desktop environment

n

Ubuntu 16.04 x64 with MATE or Gnome Flashback (Metacity) desktop
environment

n

RHEL 7 Workstation x64 with KDE or Gnome desktop environment

Audio-out Audio output redirection is supported. This feature is enabled by default. To

disable this feature, you must set the RemoteDisplay.allowAudio option
to false. Beginning with Horizon 7 version 7.2 release, VMWare Horizon
HTML Access accessed using Chrome and Firefox browsers provides
audio-out support for Linux desktops.

Client Drive Redirection The Client Drive Redirection (CDR) feature is available beginning with the

Horizon 7 version 7.2 release. When you enable the CDR feature, your
local system's shared folders and drives become available for you to
access. You use the tsclient folder that is located in your home directory
in the remote Linux desktop. To use this feature, you must install the CDR
components.

VMware, Inc. 9

Setting Up Horizon 7 for Linux Desktops

USB Redirection The USB Redirection feature is available beginning with the Horizon 7

version 7.2 release. The feature gives you access to locally attached USB
devices from remote Linux desktops. You must install the USB Redirection
components and USB VHCI driver kernel module to use the USB feature.
Ensure that you have been granted sufficient privileges to use the USB
device that you want to redirect.

Note USB 3.0 protocol is supported in Horizon 7 version 7.2 release.

Keyboard Layout and

Locale Synchronization

This feature specifies whether to synchronize a client's system locale and
current keyboard layout with the Horizon Linux Agent desktops. When this
setting is enabled or not configured, synchronization is allowed. When this
setting is disabled, synchronization is not allowed.

This feature is supported only for Horizon Client for Windows, and only for
the English, French, German, Japanese, Korean, Spanish, Simplified
Chinese and Traditional Chinese locales.

K Desktop Environment Beginning with Horizon 7 version 7.2 release, the K Desktop Environment

(KDE) is supported. The following are the currently supported Linux
distributions.

n

CentOS 6 and 7

n

RHEL 6 and 7

n

Ubuntu 14.04 and 16.04

n

SLED 11 SP4

MATE Desktop

Environment

As of Horizon 7 version 7.3 release, the MATE Desktop Environment is
supported on the following Linux distributions.

n

Ubuntu 14.04

n

Ubuntu 16.04

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.

VMware, Inc. 10

Setting Up Horizon 7 for Linux Desktops

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, the connection uses TCP 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.

Linux desktops and desktop pools have the following limitations:

n

Virtual Printing, location-based printing, and Real-Time Video are not supported.

n

The VMware HTML Access file transfer feature is not supported.

Note When a security server is used, port 22443 must be open in the internal firewall to allow traffic

between the security server and the Linux desktop.

VMware, Inc. 11

Setting Up Horizon 7 for Linux Desktops

Overview of Configuration Steps for Horizon 7 for Linux
Desktops

When you install and configure Horizon 7 for Linux desktops, you must follow a different sequence of
steps depending on whether you install 2D graphics or 3D graphics on the virtual machines.

2D Graphics - Overview of Configuration Steps

For 2D graphics, take the following steps:

1 Review the system requirements for setting up a Horizon 7 for Linux deployment. See System

Requirements for Horizon 7 for Linux.

2 Create a virtual machine in vSphere and install the Linux operating system. See Create a Virtual

Machine and Install Linux.

3 Prepare the guest operating system for deployment as a desktop in a Horizon 7 environment. See

Prepare a Linux Machine for Remote Desktop Deployment.

4 Configure the Linux guest operating system to authenticate with Active Directory. This step is

implemented with 3rd-party software, based on the requirements in your environment. See Integrating

Linux with Active Directory for more information.

5 Install Horizon Agent on the Linux virtual machine. See Install Horizon Agent on a Linux Virtual

Machine.

6 Create a desktop pool that contains the configured Linux virtual machines. See Create a Manual

Desktop Pool for Linux.

3D Graphics - Overview of Configuration Steps

You must complete the NVIDIA GRID vGPU, vDGA, or vSGA configuration on the Linux virtual machines
before you install Horizon Agent on the machines and deploy a desktop pool in View Administrator.

1 Review the system requirements for setting up a Horizon 7 for Linux deployment. See System

Requirements for Horizon 7 for Linux.

2 Create a virtual machine in vSphere and install the Linux operating system. See Create a Virtual

Machine and Install Linux.

3 Prepare the guest operating system for deployment as a desktop in a Horizon 7 environment. See

Prepare a Linux Machine for Remote Desktop Deployment.

4 Configure the Linux guest operating system to authenticate with Active Directory. This step is

implemented with 3rd-party software, based on the requirements in your environment. See Integrating

Linux with Active Directory for more information.

5 Configure 3D capabilities on your ESXi hosts and the Linux virtual machine. Follow the procedures

for the 3D feature you intend to install.

n

See Configure Supported RHEL Distributions for vGPU.

VMware, Inc. 12

Setting Up Horizon 7 for Linux Desktops

n

See Configure RHEL 6 for vDGA.

n

See Configure RHEL 7 for vSGA.

6 Install Horizon Agent on the Linux virtual machine. See Install Horizon Agent on a Linux Virtual

Machine.

7 Create a desktop pool that contains the configured Linux virtual machines. See Create a Manual

Desktop Pool for Linux.

Bulk Deployment

With View Administrator, you can only deploy Linux virtual machines in a manual desktop pool. With
vSphere PowerCLI, you can develop scripts that automate the deployment of a pool of Linux desktop
machines. See Chapter 8 Bulk Deployment of Horizon 7 for Manual Desktop Pools.

System Requirements for Horizon 7 for Linux

To install Horizon 7 for Linux, your Linux system must meet certain requirements for the operating system,
Horizon 7, and vSphere platform.

Supported Linux Versions for Horizon Agent

Table 1‑1 lists the Linux operating systems that are supported on virtual machines in a desktop pool.

Table 1‑1. Supported Linux Operating Systems for Horizon Agent

Linux Distribution Architecture

Ubuntu 14.04 and 16.04

Note You must apply one of the solutions described in VMWare

KB article http://kb.vmware.com/kb/2151294.

Ubuntu 12.04 x64

RHEL 6.6, 6.7, 6.8, 6.9, 7.2, 7.3, and 7.4 x64

CentOS 6.6, 6.7, 6.8, 6.9, 7.2, 7.3, and 7.4 x64

NeoKylin 6 Update 1 x64

SLED 11 SP3/SP4 x64

SLED 12 SP1/SP2/SP3 x64

SLES 12 SP1/SP2/SP3 x64

Note Linux agent has dependency packages on some Linux distributions. See Install Dependency

Packages for Horizon Agent for more information.

x64

Required Platform and Horizon 7 Software Versions

To install and use Horizon for Linux, your deployment must meet certain requirements for the vSphere
platform, Horizon 7, and the Horizon Client software.

VMware, Inc. 13

Setting Up Horizon 7 for Linux Desktops

Table 1‑2. Required Platform and Horizon 7 Software Versions

Platform and Software Supported Versions

vSphere platform version

Horizon environment

Horizon Client software

n

vSphere 6.0 U2 or a later release

n

vSphere 6.5 or a later release

n

Horizon Connection Server 7.4

n

Horizon Client 4.7.0 for Android

n

Horizon Client 4.7.0 for Windows

n

Horizon Client 4.7.0 for Linux

n

Horizon Client 4.7.0 for Mac OS X

n

Horizon Client 4.7.0 for iOS (iPad Pro)

n

HTML Access 4.7.0 on Chrome, Firefox, and Internet
Explorer

n

Zero clients are not supported

TCP Ports Used by Linux Virtual Machines

Horizon Agent and Horizon Clients use TCP ports for network access between each other and various
Horizon server components.

Table 1‑3. TCP Ports Used by Linux Virtual Machines

Source Port Target Port Protocol Description

Horizon Client * Linux Agent 22443 TCP Blast if Blast

Security Gateway is
not used

Security Server,
Horizon Connection
Server, or Access
Point appliance

Horizon Agent * Horizon

* Linux Agent 22443 TCP Blast if Blast

Security Gateway is
used

4001, 4002 TCP JMS SSL traffic.

Connection Server

Note For more information on TCP and UDP ports used by clients, see TCP and UDP Ports Used by

Clients and Horizon Agent in the Horizon Client and Agent Security in document.

Verify the Linux Account Used by Linux Virtual Machines

Table 1‑4 lists the account name and account type used by Linux virtual machines.

VMware, Inc. 14

Setting Up Horizon 7 for Linux Desktops

Table 1‑4. Account Name and Account Type

Account Name Account Type Used By

root Linux OS built-in Java Standalone Agent, mksvchanserver,

shell scripts

vmwblast Created by Linux Agent installer VMwareBlastServer

<current login user> Linux OS built-in or AD user or LDAP

user

Python script

Desktop Environment

Horizon 7 for Linux supports multiple desktop environments on different Linux distributions. Table 1‑5 lists
the default desktop environments for each Linux distribution and the additional desktop environments
supported by Horizon 7 for Linux.

Table 1‑5. Supported Desktop Environments

Default Desktop

Linux Distribution

Ubuntu 16.04 Unity Gnome Flashback (Metacity), K Desktop Environment (KDE), MATE

Ubuntu 14.04 Unity Gnome Fallback (Metacity), KDE, MATE

Ubuntu 12.04 Unity Unity

RHEL/CentOS 6.x Gnome Gnome, KDE

RHEL/CentOS 7.x Gnome Gnome, KDE

SLED 11 SP4 Gnome Gnome, KDE

SLED 12 SP1/SP2/SP3 Gnome Gnome

Environment Desktop Environments Supported by Horizon 7 for Linux Desktops

SLES 12 SP1/SP2/SP3 Gnome Gnome

NeoKylin 6 Update 1 Mate Mate

To change the default desktop environment used on one of the supported Linux distributions, you must
use the following steps and commands appropriate for your Linux desktop.

Note Single sign-on (SSO) for KDE and the MATE Desktop Environment only works when your Linux

desktop is using the default greeter (login screen). You must install KDE and MATE using the commands
listed in Table 1‑6.

When using SLED 11 SP3/SP4, RHEL/CentOS 7, and Ubuntu 14.04/16.04 distributions, SSO fails to
unlock a locked KDE session. You must manually enter your password to unlock the locked session.

1 Install the supported Linux distribution's operating system with the default desktop environment

setting.

VMware, Inc. 15

Setting Up Horizon 7 for Linux Desktops

2 Run the appropriate commands in Table 1‑6 for your specific Linux distribution.

Table 1‑6. Commands to Install Desktop Environments

New Default Desktop

Linux Distribution

Environment Commands to Change the Default Desktop Environment

RHEL/CentOS 6 KDE

RHEL/CentOS 7 KDE

SLED 11 SP4 KDE

Ubuntu 14.04/16.04 KDE

Ubuntu 16.04 MATE 1.16

Ubuntu 14.04 MATE 1.8

Ubuntu 16.04 Gnome Flashback

(Metacity)

# yum groupinstall "X Window System" "KDE Desktop"

# yum groupinstall "KDE Plasma Workspaces"

# zypper install -t pattern desktop-kde

# apt install plasma-desktop

# apt-add-repository ppa:ubuntu-mate-dev/xenial-mate
# apt update
# apt upgrade
# apt install mate
# apt install ubuntu-mate-themes

# apt-add-repository ppa:ubuntu-mate-dev/ppa
# apt-add-repository ppa:ubuntu-mate-dev/trusty-mate
# apt-get update
# apt-get upgrade
# apt-get install mate

# apt install gnome-session-flashback

Ubuntu 14.04 Gnome Fallback

(Metacity)

# apt-get install gnome-session-fallback

3 To begin using the new default desktop environment, restart the desktop.

If you enabled SSO on a Linux desktop that has multiple desktop environments installed, use the
following information to select the desktop environment to use in an SSO session.

n

For Ubuntu 14.04/16.04 and RHEL/CentOS 7.x, use the information in Table 1‑7 to set the
SSODesktopType option in /etc/vmware/viewagent-custom.conf file to specify the desktop
environment to use with SSO.

Table 1‑7. SSODesktopType Option

Desktop Type SSODesktopType Option Setting

MATE SSODesktopType=UseMATE

GnomeFlashback SSODesktopType=UseGnomeFlashback

KDE SSODesktopType=UseKdePlasma

GnomeClassic SSODEsktopType=UseGnomeClassic

VMware, Inc. 16

Setting Up Horizon 7 for Linux Desktops

n

For RHEL/CentOS 6.x and SLED 11 SP3/SP4, for the SSO login session to use KDE, remove all the
desktop startup files, except for the KDE startup file, from the /usr/share/xsession directory. Use
the following set of commands as an example.

# cd /usr/share/xsessions

# mkdir backup

# mv *.desktop backup

# mv backup/kde*.desktop ./

After the initial setup, the end user must log out or reboot their Linux desktop to make KDE as the
default desktop in their next SSO session.

If you disabled SSO on a Linux desktop that has multiple desktop environments installed, you do not
need to perform any of the previously described steps. The end users have to select their desired desktop
environment when they log in to that Linux desktop.

Network Requirements

VMware Blast Extreme supports both User Datagram Protocol (UDP) and Transmission Control Protocol
(TCP), and their performances are affected by the network condition. To receive the best user experience,
select UDP or TCP based on the network condition.

n

Select TCP if the network condition is good, such as in a local area network (LAN) environment.

n

Select UDP if the network condition is poor, such as in a wide area network (WAN) environment with
packet loss and time delay.

Use a network analyzer tool, such as Wireshark, to determine whether VMware Blast Extreme is using
TCP or UDP. Use the following set of steps, which use Wireshark, as a reference example.

1 Download and install Wireshark on your Linux VM.

For RHEL/CentOS 6:

sudo yum install wireshark

For Ubuntu 14.04/16.04:

sudo apt install tshark

For SLE 11/12:

sudo zypper install wireshark

2 Connect to the Linux desktop using VMware Horizon Client.

3 Open a terminal window and run the following command, which displays the TCP package or UDP

package used by VMware Blast Extreme.

sudo tshark -i any | grep 22443

VMware, Inc. 17

Setting Up Horizon 7 for Linux Desktops

USB Redirection and Client Drive Redirection (CDR) features are sensitive to network conditions. If the
network condition is bad, such as limited bandwidth with time delay and packet loss, the user experience
becomes poor. In such condition, the end user might experience one of the following.

n

Copying remote files can be slow. In this situation, transmit smaller sized files instead.

n

USB device does not appear in the remote Linux desktop.

n

USB data does not transfer completely. For example, if you copy a large file, you might get a file
smaller in size than the original file.

VHCI Driver for USB Redirection

The USB redirection feature is supported beginning with Horizon 7 version 7.1 for Linux desktops. The
feature has a dependency on the USB Virtual Host Controller Interface (VHCI) kernel driver. You must
patch the VHCI driver to support USB 3.0.

The Horizon for Linux installer includes the VHCI driver binary for the default kernel of the supported
Linux distributions. The installer installs the VHCI driver when the USB redirection feature is selected.

Table 1‑8 lists the default kernel versions that the Horizon for Linux installer installs.

Table 1‑8. Default Kernel Versions

Linux Distribution Default Kernel Version

RHEL/CentOS 6.9 2.6.32-696.el6.x86_64

SUSE 12 SP2 4.4.21-69-default

RHEL/CentOS 7.3 3.10.0-514.el7.x86_64

Ubuntu 14.04 3.13.0-24-generic

Ubuntu 16.04 4.4.0-21-generic

If your Linux system uses a kernel version that is different from the default versions included with the
Horizon for Linux installer, you must download the USB VHCI source code from

https://sourceforge.net/projects/usb-vhci/files/linux%20kernel%20module/. You must then compile the

VHCI driver source code and install the resulting binary on your Linux system.

Note The VHCI driver installation must be done before the installation of Horizon for Linux.

After you download the latest version of the USB VHCI driver source code, use the commands in

Table 1‑9 to compile and install it on your Linux system. For example, if you unpack the installation file,

VMware-horizonagent-linux-x86_64-<version>-<build-number>.tar.gz, under
the /install_tmp/ directory, the full-path_to_patch-file is /install_tmp/VMware-

horizonagent-linux-x86_64-<version>-<buildnumber>/resources/vhci/patch/vhci.patch
and the patch command to use is

# patch -p1 < /install_tmp/VMware-horizonagent-linux-x86_64-<version>-<build-

number>/resources/vhci/patch/vhci.patch

VMware, Inc. 18

Setting Up Horizon 7 for Linux Desktops

Table 1‑9. Compile and Install USB VHCI Driver

Linux

Distribution Steps to Compile and Install USB VHCI Driver

Ubuntu 14.04

Ubuntu 16.04

RHEL/CentOS

6.9

RHEL/CentOS 7

SUSE 11 SP4

SUSE 12 SP2

Compile and install the VHCI drivers.

# tar -xzvf vhci-hcd-1.15.tar.gz
# cd vhci-hcd-1.15
# patch -p1 < full-path_to_patch-file
# make clean && make && make install

1 Install the dependency packages.

# yum install gcc-c++
# yum install kernel-devel-$(uname -r)
# yum install kernel-headers-$(uname -r)
# yum install patch

2 Compile and install the VHCI drivers.

# tar -xzvf vhci-hcd-1.15.tar.gz
# cd vhci-hcd-1.15
# patch -p1 < full-path_to_patch-file
# make clean && make && make install

1 Find out the version of the current kernel package

# rpm -qa | grep kernel-default-$(echo $(uname -r) | cut -d '-' -f 1,2)

The output is the name of the kernel package currently installed. If, for example, the package name is
kernel-default-3.0.101-63.1, then the current kernel package version is 3.0.101-63.1.

2 Install the dependency packages.

a For SUSE 11, install the kernel-source and kernel-default-devel packages that match the

current kernel; the gcc and the patch packages.

# zypper install --oldpackage kernel-source-<kernel-package-version> \
kernel-default-devel-<kernel-package-version> gcc patch

For example:

# zypper install --oldpackage kernel-source-3.0.101-63.1 kernel-default­devel-3.0.101-63.1 gcc patch

VMware, Inc. 19

Setting Up Horizon 7 for Linux Desktops

Table 1‑9. Compile and Install USB VHCI Driver (Continued)

Linux

Distribution Steps to Compile and Install USB VHCI Driver

b For SUSE 12, install the kernel-devel, kernel-default-devel, kernel-macros, and the patch

packages.

# zypper install --oldpackage kernel-devel-<kernel-package-version> \
kernel-default-devel-<kernel-package-version> kernel-macros-<kernel-package-

version> patch

For example:

# zypper install --oldpackage kernel-devel-4.4.21-90.1 kernel-default­devel-4.4.21-90.1 kernel-macros-4.4.21-90.1 patch

3 Compile and install the VHCI drivers.

# tar -xzvf vhci-hcd-1.15.tar.gz
# cd vhci-hcd-1.15
# patch -p1 < full-path_to_patch-file
# mkdir -p linux/$(echo $(uname -r) | cut -d '-' -f 1)/drivers/usb/core
# cp /lib/modules/$(uname -r)/source/include/linux/usb/hcd.h linux/$(echo $(uname ­r) | cut -d '-' -f 1)/drivers/usb/core
# make clean && make && make install

If your Linux kernel version is changed, you must recompile and reinstall the VHCI driver, but you do not
need to reinstall Horizon for Linux.

You can also add Dynamic Kernel Module Support (DKMS) to the VHCI driver using the steps similar to
the following example for an Ubuntu 16.04 system.

1 Install the kernel headers.

# apt install linux-headers-`uname -r`

2 Install dkms using the following command.

# apt install dkms

3 Extract and patch the VHCI tar file.

# tar xzvf vhci-hcd-1.15.tar.gz

# cd vhci-hcd-1.15

# patch -p1 <full-path_to_patch-file>

# cd ..

4 Copy the extracted VHCI source files to the /usr/src directory.

# cp -r vhci-hcd-1.15 /usr/src/usb-vhci-hcd-1.15

VMware, Inc. 20

Setting Up Horizon 7 for Linux Desktops

5 Create a file named dkms.conf and place it in the /usr/src/usb-vhci-hcd-1.15 directory.

# touch /usr/src/usb-vhci-hcd-1.15/dkms.conf

6 Add the following contents to the dkms.conf file.

PACKAGE_NAME="usb-vhci-hcd

PACKAGE_VERSION=1.15

MAKE_CMD_TMPL="make KVERSION=$kernelver"

CLEAN="$MAKE_CMD_TMPL clean"

BUILT_MODULE_NAME[0]="usb-vhci-iocifc"

DEST_MODULE_LOCATION[0]="/kernel/drivers/usb/host"

MAKE[0]="$MAKE_CMD_TMPL"

BUILT_MODULE_NAME[1]="usb-vhci-hcd"

DEST_MODULE_LOCATION[1]="/kernel/drivers/usb/host"

MAKE[1]="$MAKE_CMD_TMPL"

AUTOINSTALL="YES"

7 Add this VHCI driver in dkms.

# dkms add usb-vhci-hcd/1.15

8 Build the VHCI driver.

# dkms build usb-vhci-hcd/1.15

9 Install the VHCI driver.

# dkms install usb-vhci-hcd/1.15

Virtual Machine Settings for 2D and vSGA Graphics

When you create certain Horizon 7 for Linux virtual machines, you must change the memory settings and
configuration parameters to the minimum values recommended.

Virtual machines that are configured to use NVIDIA vDGA use the NVIDIA physical graphic card. Virtual
machines that are configured to use NVIDIA GRID vGPU use the NVIDIA virtual graphic card, which is
based on the NVIDIA physical graphic accelerator. You do not need to change the Video Memory (vRAM)
settings and configuration parameters for these virtual machines.

Virtual machines that are configured to use 2D or vSGA graphics use the VMware virtual graphic card
and you must change the following settings for these types of virtual machines:

n

Video Memory (vRAM) settings

n

Configuration parameters

VMware, Inc. 21

Setting Up Horizon 7 for Linux Desktops

n

3D Memory settings

n

vCPU and virtual memory settings for performance requirement

Video Memory (vRAM) Settings

When you create a Linux virtual machine in vSphere Client, configure the vRAM size as shown in

Table 1‑10. Set the vRAM size that is recommended for the number and resolution of the monitors that

you configure for the virtual machine.

Table 1‑10. Recommended vRAM Settings for 2D or vSGA Graphics

Number of

vRAM Size

10 MB 1 1600x1200 or 1680x1050

12 MB 1 1920x1440

32 MB 1 2560x1600

48 MB 2 2048x1536

80 MB 2 2560x1600

Monitors Maximum Resolution

128 MB 3 2560x1600

128 MB 4 2048x1536

These vRAM sizes are the minimum recommendations. If more resources are available on the virtual
machine, set the vRAM to larger values for improved video performance.

10 MB is the minimum vRAM size recommendation for a machine that is configured with a single monitor
at the lowest resolution.

You must power off the virtual machine to set the number of displays and the amount of video memory to
use, as described in Create a Virtual Machine and Install Linux.

Horizon Connection Server 7 does not automatically configure the vRAM settings on Linux virtual
machines like it does on Windows virtual machines. You must manually configure the vRAM settings in
vSphere Client.

If a Linux virtual machine is configured with a smaller vRAM size than is recommended, the following
issues might occur:

n

Desktop sessions might be disconnected right after the initial connection is made.

n

Autofit might fail to work. The desktop is then displayed in a small area of the screen.

If a Linux virtual machine's Number of displays value is less than the actual required count, one or more
monitors display blank for the desktop.

If you encounter an autofit issue with the recommended settings, you can specify a larger vRAM size.
vSphere Client permits a maximum vRAM size of 128 MB. If your specified size exceeds 128 MB, you
must modify the vmx configuration file manually. The following example specifies a vRAM size of 256 MB:

svga.vramSize = "268435456"

VMware, Inc. 22

Setting Up Horizon 7 for Linux Desktops

Configuration Parameters

To display the Linux remote desktop on multiple monitors, you must set certain configuration parameters
for the virtual machine. The general steps to set a configuration parameter for a virtual machine are as
follows:

1 Power off the virtual machine.

2 In the vSphere Web Client, right-click the virtual machine and select Edit Settings.

3 Click the VM Options tab and click Advanced.

4 Click Edit Configuration and then Add Row.

5 Enter the configuration parameter name and value.

6 Click OK to save the changes.

You must set the following configuration parameters:

n

Set svga.autodetect to false.

svga.autodetect="false"

n

Calculate the svga.maxWidth and svga.maxHeight values according to the number and orientation
(horizontal or vertical) of the display monitors. The general rule is that the svga.maxWidth and
svga.maxHeight values must be large enough to support all the displays. For example, to support
four displays at the maximum resolution of 2560x1600, you must set the following values:

svga.maxHeight="3200"

svga.maxWidth="10240"

If you have multiple monitors, you must set these configuration parameters. Otherwise, you might
encounter one or more of the following problems:

n

The desktop is displayed on some of the monitors and the other monitors are blank.

n

A keystroke is displayed multiple times.

n

The desktop becomes slow.

n

The desktop is displayed in a small area of the screen.

Screen Size Limitation of 4096x4096 Monitors

For RHEL 6.8/6.9/7.3/7.4, CentOS 6.8/6.9/7.3/7.4, Ubuntu 16.04, SLED 12 SP2/SP3, and SLES 12
SP2/SP3, the maximum screen size for 2D and vSGA is 4096x4096. When you run the xrandr
command, the first line of the output has maximum 4096x4096.

For Ubuntu 14.04, the limitation is also introduced if you install the latest patches from the official Ubuntu
repositories.

VMware, Inc. 23

Setting Up Horizon 7 for Linux Desktops

Multiple-monitor connection might require a screen size larger than 4096x4096. To bypass this limitation,
use one of the following solutions:

n

If you have to use VMware Hardware version 11 (HWv11) or later for your virtual machine, add the
following line into the virtual machine's VMX configuration file:

mks.enable3d = TRUE

With this solution, the Linux operating system can report 3D capabilities to software applications,
such as Chrome. However, doing so might impact the Linux system's performance.

n

If your virtual machine can use VMware Hardware version 10, use the following line in your virtual
machine's VMX file:

virtualHW.version = "10"

This solution is not applicable for RHEL 6.8 and CentOS 6.8.

To make this solution work on Ubuntu 16.04 systems, you must install the latest patches from the
official Ubuntu repositories.

vCPU and Memory Settings

To improve the performance of a 2D or vSGA desktop, set more vCPUs and virtual memory for the Linux
virtual machine. For example, set 2 vCPUs and 2 GB of virtual memory.

For the large screen of multiple monitors, such as four monitors, set 4 vCPUs and 4 GB of virtual memory
for the virtual machine.

For the video playback purpose in a 2D or vSGA desktop, set 4 vCPUs and 4 GB of virtual memory for
the virtual machine.

3D Memory Settings

To improve performance in a vSGA multiple monitor environment, set the 3D Memory setting for the
virtual machine to 1 GB or larger.

VMware, Inc. 24

Preparing a Linux Virtual
Machine for Desktop

Deployment 2

Setting up a Linux desktop involves creating a Linux virtual machine and preparing the operating system
for remote desktop deployment.

This chapter includes the following topics:

n

Create a Virtual Machine and Install Linux

n

Prepare a Linux Machine for Remote Desktop Deployment

n

Install Dependency Packages for Horizon Agent

Create a Virtual Machine and Install Linux

You create a new virtual machine in vCenter Server for each remote desktop that is deployed in Horizon

7. You must install your Linux distribution on the virtual machine.

Prerequisites

n

Verify that your deployment meets the requirements for supporting Linux desktops. See System

Requirements for Horizon 7 for Linux.

n

Familiarize yourself with the steps for creating virtual machines in vCenter Server and installing guest
operating systems. See "Creating and Preparing Virtual Machines" in the Setting Up Virtual Desktops
in Horizon 7 document.

n

Familiarize yourself with the recommended video memory (vRAM) values for the monitors you will
use with the virtual machine. See System Requirements for Horizon 7 for Linux.

Procedure

1 In vSphere Web Client or vSphere Client, create a new virtual machine.

VMware, Inc.

25

Setting Up Horizon 7 for Linux Desktops

2 Configure custom configuration options.

a Right-click the virtual machine and click Edit Settings.

b Specify the number of vCPUs and the vMemory size.

For recommended values, follow the guidelines in the installation guide for your Linux distribution.

For example, Ubuntu 12.04 recommends configuring 2048 MB for vMemory and 2 vCPUs.

c Select Video card and specify the number of displays and the total video memory (vRAM).

Set the vRAM size in vSphere Web Client for virtual machines that use 2D or vSGA, which use
the VMware driver. The vRAM size has no affect on vDGA or NVIDIA GRID vGPU machines,
which use NVIDIA drivers.

For recommended values, follow the guidelines in System Requirements for Horizon 7 for Linux.
Do not use the Video Memory Calculator.

3 Power on the virtual machine and install the Linux distribution.

4 Configure the desktop environment to use for the specific Linux distribution.

See the Desktop Environment section in System Requirements for Horizon 7 for Linux for additional
information.

5 Ensure that the system hostname is resolvable to 127.0.0.1.

Prepare a Linux Machine for Remote Desktop Deployment

You must perform certain tasks to prepare a Linux machine for use as a desktop in a Horizon 7
deployment.

Before a Linux machine can be managed by Horizon 7, the machine must be able to communicate with
Connection Server. You must configure networking on the Linux machine so that the Linux machine can
ping the Connection Server instance using its FQDN (fully qualified domain name).

Open VMware Tools (OVT) are pre-installed on RHEL 7, CentOS 7, SLED 12, and SLES 12 machines. If
you are preparing either of these machines for use as a remote desktop, you can skip steps 1 through 5
in the following procedure, which describe how to install VMware Tools by manually running the installer.

If you are using an Ubuntu16.04 machine, install OVT on it. If you are preparing this machine for use as a
remote desktop, you can skip steps 1 through 5 in the following procedure and manually install OVT on
your Ubuntu 16.04 machine using the following command:

apt-get install open-vm-tools-desktop

Prerequisites

n

Verify that a new virtual machine (VM) was created in vCenter Server and your Linux distribution was
installed on the machine

VMware, Inc. 26

Setting Up Horizon 7 for Linux Desktops

n

Familiarize yourself with the steps for mounting and installing VMware Tools on a Linux VM. See
"Manually Install or Upgrade VMware Tools in a Linux Virtual Machine" in the vSphere Virtual
Machine Administration document.

n

Familiarize yourself with the steps for configuring your Linux machine to be resolvable through DNS.
These steps vary for the different Linux distributions and releases. For instructions, consult the
documentation for your Linux distribution and release.

Procedure

1 In vSphere Web Client or vSphere Client, mount the VMware Tools virtual disk on the VM.

2 Right-click the VMware Tools installer file, VMwareTools.x.x.x-xxxx.tar.gz, click Extract to, and

select the desktop for your Linux distribution.

The vmware-tools-distrib folder is extracted to the desktop.

3 On the VM, log in as root and open a terminal window.

4 Uncompress the VMware Tools tar installer file.

For example:

tar zxpf /mnt/cdrom/VMwareTools-x.x.x-yyyy.tar.gz

5 Run the installer and configure VMware Tools.

The command might vary slightly in different Linux distributions. For example:

cd vmware-tools-distrib

sudo ./vmware-install.pl -d

Usually, the vmware-config-tools.pl configuration file runs after the installer file finishes running.

6 Map the Linux machine's host name to 127.0.0.1 in the /etc/hosts file.

For RHEL, CentOS, SLES, and SLED, you must manually map the host name to 127.0.0.1 because it
is not automatically mapped. For Ubuntu, this step is not necessary because the mapping is there by
default. This step is also not necessary when you bulk deploy desktops because the cloning process
adds this mapping.

Note If you change the Linux machine's host name after installing Horizon Agent, you must map the

new host name to 127.0.0.1 in the /etc/hosts file. Otherwise, the old host name will continue to be
used.

7 For RHEL 7 and CentOS 7, verify that virbr0 is disabled.

virsh net-destroy default

virsh net-undefine default

service libvirtd restart

8 Ensure that the View Connection Server instances in the pod can be resolved through DNS.

VMware, Inc. 27

Setting Up Horizon 7 for Linux Desktops

9 Configure the Linux machine so that the default runlevel is 5.

The runlevel must be 5 for the Linux desktop to work.

10 On an Ubuntu machine that was configured to authenticate with an OpenLDAP server, set the fully

qualified domain name on the machine.

This step ensures that the information can be displayed correctly in the User field on the Sessions
page in View Administrator. Edit the /etc/hosts file as follows:

# nano /etc/hosts

a

b Add the fully qualified domain name. For example: 127.0.0.1 hostname.domainname

hostname.

c Exit and save the file.

11 For SUSE, disable Change Hostname via DHCP. Set the hostname or domain name.

a In Yast, click Network Settings.

b Click the Hostname/DNS tab.

c Deselect Change Hostname via DHCP.

d Enter the hostname and the domain name.

e Click OK.

After installing VMware Tools, if you upgrade the Linux kernel, VMware Tools might stop running. To
resolve the problem, see http://kb.vmware.com/kb/2050592.

Install Dependency Packages for Horizon Agent

Horizon Agent for Linux has some dependency packages unique to a Linux distribution. You must install
these packages before installing Horizon Agent for Linux.

Prerequisites

Verify that a new virtual machine (VM) is created in vCenter Server and your Linux distribution is installed
on the machine.

VMware, Inc. 28

Setting Up Horizon 7 for Linux Desktops

Procedure

1 Install the mandatory packages that are not installed or upgraded by default. The installer breaks the

installation if any package does not meet the requirement.

Table 2‑1. Mandatory Dependency Packages

Linux Distribution Packages

SLED 11 SP3/SP4

Upgrade xorg-x11-server to a
version later than 7.4.27.111.1

SLES 12 SP1/SLED 12 SP1

Upgrade xf86-video-vmware to
a version later than 13.0.2-3.2
from the SUSE repository

SLES 12 Install python-gobject2 is required for SLES 12 Linux desktop when you are installing

Ubuntu 14.04

Upgrade indicator-session to

12.10.5+15.04.20150327,
available in

https://launchpad.net/ubuntu/wil
y/amd64/indicator­session/12.10.5+15.04.2015032
7-0ubuntu1

zypper install xorg-x11-server

1 Register SUSE 12 to enable the SUSE repositories.

SUSEConnect -r Registration Code -e Email

2 Update the xf86-video-vmware version.

zypper install xf86-video-vmware

Horizon Agent.

1 Register SUSE 12 to enable the SUSE repositories.

SUSEConnect -r Registration Code -e Email

2 Install python-gobject2.

zypper install python-gobject2

wget http://launchpadlibrarian.net/201393830/indicator­session_12.10.5+15.04.20150327-0ubuntu1_amd64.deb

sudo dpkg -i ./indicator­session_12.10.5+15.04.20150327-0ubuntu1_amd64.deb

Ubuntu 16.04

apt-get install python-dbus python-gobject

2 Install the optional package for Horizon Agent.

n

By default, RHEL or CentOS 6.7 has glibc-2.12-1.166.el6.x86_64 installed which might cause a
deadlock issue. As a result, the desktop connection is stuck. To overcome this issue, you must
upgrade glibc to the latest version from an online repository.

sudo yum install glibc

VMware, Inc. 29

Setting Up Active Directory

Integration for Linux Desktops 3

View uses the existing Microsoft Active Directory (AD) infrastructure for user authentication and
management. You can integrate the Linux desktops with Active Directory so that users can log in to a
Linux desktop using their Active Directory user account.

This chapter includes the following topics:

n

Integrating Linux with Active Directory

n

Setting Up Single Sign-on and Smart Card Redirection

Integrating Linux with Active Directory

Multiple solutions exist to integrate Linux with Microsoft Active Directory (AD) and Horizon 7 for Linux
Desktop has no dependency on which solution is used.

The following solutions are known to work in a Horizon 7 for Linux desktop environment.

n

OpenLDAP Server Pass-through Authentication

n

System Security Services Daemon (SSSD) LDAP Authentication against the Microsoft Active
Directory

n

Winbind Domain Join

n

PowerBroker Identity Services Open (PBISO) Authentication

If you use the LDAP-based solutions, you must perform the configuration in a template virtual machine
and no additional steps are required in the cloned virtual machines.

Note For ease of deployment, use the SSSD LDAP authentication against the Microsoft Active Directory

solution.

OpenLDAP Server Pass-Through Authentication

At a high level, the OpenLDAP Pass-through authentication solution involves the following steps:

1 To enable LDAPS (Lightweight Directory Access Protocol over SSL), install Certificate Services on

the Active Directory.

2 Set up an OpenLDAP server.

VMware, Inc.

30

Setting Up Horizon 7 for Linux Desktops

3 Synchronize user information (except password) from the Active Directory to the OpenLDAP server.

4 Configure the OpenLDAP server to delegate password verification to a separate process such as

saslauthd, which can perform password verification against the Active Directory.

5 Configure the Linux desktops to use an LDAP client to authenticate users with the OpenLDAP server.

System Security Services Daemon (SSSD) LDAP Authentication
Against the Microsoft Active Directory

The SSSD LDAP authentication against the Microsoft Active Directory solution involves the following
steps:

1 To enable LDAPS, install the Certificate Services on the Active Directory.

2 To use LDAP authentication directly against the Microsoft Active Directory, configure the SSSD in the

Linux desktop.

Winbind Domain Join

The Winbind Domain Join solution involves the following steps:

1 Install the Winbind, Samba, and Kerberos packages on the Linux desktop.

2 Join the Linux desktop to the Microsoft Active Directory.

If you use the Winbind Domain Join solution or other Keberos authentication-based solution, join the
template virtual machine to the Active Directory, and re-join the cloned virtual machine to the Active
Directory. For example, use the following command:

sudo /usr/bin/net ads join -U <domain_user>%<domain_password>

Use the following options to run the domain re-join command on a cloned virtual machine for the Winbind
solution:

n

Remote connect such as SSH or vSphere PowerCLI to each virtual machine and run the command.
For more information on scripts, see Chapter 8 Bulk Deployment of Horizon 7 for Manual Desktop

Pools.

n

Include the command to a shell script and set the script path to the Horizon agent RunOnceScript
option in the /etc/vmware/viewagent-custom.conf file. For more information, see Setting Options

in Configuration Files on a Linux Desktop.

PowerBroker Identity Services Open (PBISO) Authentication

Configuring the PowerBroker Identity Services Open (PBISO) authentication solution involves the
following steps:

1 Download PBISO 8.5.6 or later from https://www.beyondtrust.com/products/powerbroker-

identity-services-open/.

VMware, Inc. 31

Setting Up Horizon 7 for Linux Desktops

2 Install PBISO on your Linux VM.

sudo ./pbis-open-8.5.6.2029.linux.x86_64.deb.sh

3 Install Horizon 7 Agent for Linux.

4 Use PBISO to join the Linux desktop to the AD domain.

In the following example, lxdc.vdi is the domain name and administrator is the domain user
name.

sudo domainjoin-cli join lxdc.vdi administrator

5 Set up the default configuration for domain users.

sudo /opt/pbis/bin/config UserDomainPrefix lxdc

sudo /opt/pbis/bin/config AssumeDefaultDomain true

sudo /opt/pbis/bin/config LoginShellTemplate /bin/bash

sudo /opt/pbis/bin/config HomeDirTemplate %H/%U

6 Edit the /etc/pamd.d/common-session file.

a Locate the line that says session sufficient pam_lsass.so.

b Replace that line with session [success=ok default=ignore] pam_lsass.so.

Note This step must be repeated after you reinstall or update the Horizon Agent for Linux.

7 Edit the /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf file and append the

following lines.

Note If you are using Ubuntu 14.04, the lightdm configuration file is named 60-lightdm-gtk-

greeter.conf.

allow-guest=false

greeter-show-manual-login=true

VMware, Inc. 32

Setting Up Horizon 7 for Linux Desktops

8 Reboot your system and log in.

Note

n

If the /opt/pbis/bin/config AssumeDefaultDomain option is set to false, you must update the
SSOUserFormat=<username>@<domain> setting in the /etc/vmware/viewagent-custom.conf file.

n

When using the Horizon instant-clone floating desktop pool feature, to avoid losing the DNS Server
setting when the new network adapter is added to the cloned VM, modify the resolv.conf file for
your Linux system. Use the following example, for an Ubuntu 16.04 system, as a guide for adding the
necessary lines in the /etc/resolvconf/resolv.conf.d/head file.

nameserver 10.10.10.10

search mydomain.org

Setting Up Single Sign-on and Smart Card Redirection

To set up single sign-on (SSO) and smart card redirection, you must perform some configuration steps.

Single Sign-on

The Horizon single sign-on module communicates with PAM (pluggable authentication modules) in Linux
and does not depend on the method that you use to integrate Linux with Active Directory (AD). Horizon
SSO is known to work with the OpenLDAP and Winbind solutions that integrate Linux with AD.

By default, SSO assumes that AD's sAMAccountName attribute is the login ID. To ensure that the correct
login ID is used for SSO, you must perform the following configuration steps if you use the OpenLDAP or
Winbind solution:

n

For OpenLDAP, set sAMAccountName to uid.

n

For Winbind, add the following statement to the configuration file /etc/samba/smb.conf.

winbind use default domain = true

If users must specify the domain name to log in, you must set the SSOUserFormat option on the Linux
desktop. For more information, see Setting Options in Configuration Files on a Linux Desktop. Be aware
that SSO always uses the short domain name in upper case. For example, if the domain is
mydomain.com, SSO will use MYDOMAIN as the domain name. Therefore, you must specify MYDOMAIN
when setting the SSOUserFormat option. Regarding short and long domain names, the following rules
apply:

n

For OpenLDAP, you must use short domain names in upper case.

n

Winbind supports both long and short domain names.

AD supports special characters in login names but Linux does not. Therefore, do not use special
characters in login names when setting up SSO.

VMware, Inc. 33

Setting Up Horizon 7 for Linux Desktops

In AD, if a user's UserPrincipalName (UPN) attribute and sAMAccount attribute do not match and the
user logs in with the UPN, SSO will fail. The workaround is for the user to log in using the name that is
stored in sAMAccount.

View does not require the user name to be case-sensitive. You must ensure that the Linux operating
system can handle case-insensitive user names.

n

For Winbind, the user name is case-insensitive by default.

n

For OpenLDAP, Ubuntu uses NSCD to authenticate users and is case-insensitive by default. RHEL
and CentOS use SSSD to authenticate users and the default is case-sensitive. To change the setting,
edit the file /etc/sssd/sssd.conf and add the following line in the [domain/default] section:

case_sensitive = false

If your Linux desktop has multiple desktop environments installed on it, refer to Desktop Environment to
select the desktop environment to use with SSO.

Smart Card Redirection

To set up smart card redirection, first follow the instructions from the Linux distributor and from the smart
card vendor. Then update the pcsc-lite package to 1.7.4. For example, run the following commands:

#yum groupinstall "Development tools"

#yum install libudev-devel

#service pcscd stop

#wget https://alioth.debian.org/frs/download.php/file/3598/pcsc-lite-1.7.4.tar.bz2

#tar -xjvf pcsc-lite-1.7.4.tar.bz2

#cd ./pcsc-lite-1.7.4

#./configure --prefix=/usr/ --libdir=/usr/lib64/ --enable-usbdropdir=/usr/lib64/pcsc/drivers

--enable-confdir=/etc --enable-ipcdir=/var/run --disable-libusb --disable-serial --disable-usb

--disable-libudev

#make

#make install

#service pcscd start

For Winbind, add the following statement to the configuration file /etc/samba/smb.conf.

winbind use default domain = true

When you install theHorizon Agent, you must first disable SELinux or enable permissive mode for
SELinux. You must also specifically select the smart card redirection component because the component
is not selected by default. For more information, see install_viewagent.sh Command-Line Options.

Smartcard SSO is enabled in Horizon 7 version 7.0.1 or later. In addition, if the smart card redirection
feature is installed on a virtual machine, vSphere Client's USB redirection does not work with the smart
card.

Smart card redirection supports only one smart card reader. This feature does not work if two or more
readers are connected to the client device.

VMware, Inc. 34

Setting Up Horizon 7 for Linux Desktops

Smart card redirection supports only one certificate on the card. If more than one certificate is on the
card, the one in the first slot is used and the others are ignored. This is a Linux limitation.

Note

n

Smartcard supports the following winbind value. Else the smartcard SSO and manual login fails.

winbind use default domain=true

n

When you use Horizon Client for Linux to authenticate the broker with PIV card, which is supported
by Linux desktop smartcard redirection, you must configure the PIV smart card with TLSv1.2 support
to avoid receiving an SSL error. Use the solution described in VMWare KB article

http://kb.vmware.com/kb/2150470.

VMware, Inc. 35

Setting Up Graphics for Linux

Desktops 4

You can configure the currently supported RHEL distributions to take advantage of NVIDIA capabilities on
ESXi host or on a guest operating system.

VM Clone Requirements for Setting Up 3D Graphics

You must consider the following requirements for VM Clone before setting up 3D graphics.

n

For vGPU and vSGA, complete the graphic setup in the base VM. Clone the VMs. The graphic
settings work for cloned VMs and no further settings are required.

n

For vDGA, complete the graphic setup in the base VM. Clone the VMs. However before you power on
the cloned VMs, you must remove the existing NVIDIA pass-through PCI device from the cloned VM
and add the new NVIDIA pass-through PCI device to the cloned VM. NVIDIA pass-through PCI
device cannot be shared between VMs. Each VM uses a dedicated NVIDIA pass-through PCI device.

This chapter includes the following topics:

n

Configure Supported RHEL Distributions for vGPU

n

Configure RHEL 6 for vDGA

n

Configure RHEL 7 for vSGA

Configure Supported RHEL Distributions for vGPU

You can set up a supported RHEL distirbution to take advantage of NVIDIA vGPU (shared GPU hardware
acceleration) capabilities on the ESXi host.

You must use the NVIDIA Linux VM display driver that matches the ESXi host GPU driver(.vib). See the
NVIDIA Web site for information about driver packages.

Important NVIDIA vGPU is supported on NVIDIA Maxwell M60 graphics cards and NVIDIA M6 graphics

cards. This feature does not work on other NVIDIA graphics cards such as GRID K1 or K2.

Caution Before you begin, verify that Horizon Agent is not installed on the Linux virtual machine. If you

install Horizon Agent before you configure the machine to use NVIDIA vGPU, required configuration
parameters in the xorg.conf file are overwritten, and NVIDIA vGPU does not work. You must install
Horizon Agent after the NVIDIA vGPU configuration is completed.

VMware, Inc.

36

Setting Up Horizon 7 for Linux Desktops

Install the VIB for the NVIDIA GRID vGPU Graphics Card on the ESXi Host

You must download and install the VIB for your NVIDIA GRID graphics card on the ESXi 6.0 U1 or later
host.

NVIDIA provides a vGPU software package that includes a vGPU Manager, which you install on the ESXi
host in this procedure, and a Linux Display Driver, which you will install on the Linux virtual machine in a
later procedure.

Prerequisites

n

Verify that vSphere 6.0 U1 or a later release is installed in your environment.

n

Verify that the NVIDIA Maxwell M60 GPUs or M6 GPUs are installed on the ESXi host.

Procedure

1 Download the VIB for your NVIDIA GRID vGPU graphics card from the NVIDIA Driver Downloads

site.

Select the appropriate VIB version from the drop-down menus.

Option Description

Product Type GRID

Product Series Select NVIDIA GRID vGPU.

Product Select the version (such as GRID K2) that is installed on the ESXi host.

Operating System Select the VMware vSphere ESXi version.

2 Uncompress the vGPU software package .zip file.

3 Upload the vGPU Manager folder to the ESXi 6.0 U1 host.

Note You will install the Linux Display Driver on the Linux virtual machine in a later procedure.

4 Power off or suspend all virtual machines on the ESXi host.

5 Connect to the ESXi host using SSH.

6 Stop the xorg service.

# /etc/init.d/xorg stop

7 Install the NVIDIA VIB.

For example:

# esxcli system maintenanceMode set --enable true

# esxcli software vib install -v /path-to-vib/NVIDIA-VIB-name.vib

# esxcli system maintenanceMode set --enable false

VMware, Inc. 37

Setting Up Horizon 7 for Linux Desktops

8 Reboot or update the ESXi host.

u

For an installed ESXi host, reboot the host.

u

For a stateless ESXI host, take the following steps to update the host. (These steps also work on
an installed host.)

Update vmkdevmgr:

# kill -HUP $(cat /var/run/vmware/vmkdevmgr.pid)

Wait for the update to complete:

# localcli --plugin-dir /usr/lib/vmware/esxcli/int deviceInternal bind

This is a new requirement with the NVIDIA 352.* host driver:

# /etc/init.d/nvidia-vgpu start

Restart xorg, which is used for GPU assignment:

# /etc/init.d/xorg start

9 Verify that the xorg service is running after the host is restarted.

Configure a Shared PCI Device for vGPU on the Linux Virtual
Machine

To use NVIDIA vGPU, you must configure a shared PCI device for the Linux virtual machine.

Prerequisites

n

Verify that the Linux virtual machine is prepared for use as a desktop. See Create a Virtual Machine

and Install Linux and Prepare a Linux Machine for Remote Desktop Deployment.

n

Verify that Horizon Agent is not installed on the Linux virtual machine.

n

Verify that the NVIDIA VIB is installed on the ESXi host. See Install the VIB for the NVIDIA GRID

vGPU Graphics Card on the ESXi Host.

n

Familiarize yourself with the virtual GPU types that are available with NVIDIA vGPU, which you select
with the GPU Profile setting. The virtual GPU types provide varying capabilities on the physical
GPUs installed on the ESXi host. See NVIDIA Virtual GPU Types.

Procedure

1 Power off the virtual machine.

2 In vSphere Web Client, select the virtual machine and, under the VM Hardware tab, click Edit

Settings.

3 In the New device menu, select Shared PCI Device.

4 Click Add and select NVIDIA GRID vGPU from the drop-down menu.

5 For the GPU Profile setting, select a virtual GPU type from the drop-down menu.

6 Click Reserve all memory and click OK.

You must reserve all virtual machine memory to enable the GPU to support NVIDIA GRID vGPU.

VMware, Inc. 38

Setting Up Horizon 7 for Linux Desktops

7 Power on the virtual machine.

NVIDIA Virtual GPU Types

With the GPU Profiles setting on the Virtual Hardware page in vSphere Web Client, you can select a
virtual GPU type that provides specific capabilities on the physical NVIDIA GPU on the ESXi host.

On Linux virtual machines, NVIDIA GRID vGPU is supported on NVIDIA Maxwell M60 GPUs or NVIDIA
M6 GPUs.

Table 4‑1. Virtual GPU Types Available for NVIDIA GRID M60 vGPU on Linux Virtual Machines

Maximum

Virtual

GPUs Per

Virtual GPU

Type

GRID M60-0q GRID M60 two 512M 2 2560x1600 16 32

GRID M60-1q GRID M60 two 1G 2 2560x1600 8 16

GRID M60-2q GRID M60 two 2G 4 2560x1600 4 8

Physical

Board

Physical

GPUs

FB Per

Virtual GPU

Display

Heads

Maximum

Resolution

Physical

GPU

Maximum

Virtual GPUs

Per Physical

Board

GRID M60-4q GRID M60 two 4G 4 3840x2160 2 4

GRID M60-8q GRID M60 two 8G 4 3840x2160 1 2

Table 4‑2. Virtual GPU Types Available for NVIDIA GRID M6 vGPU on Linux Virtual Machines

Maximum

Virtual

GPUs Per

Virtual GPU

Type

GRID M6-0q GRID M6 one 512M 2 2560x1600 16 16

GRID M6-1q GRID M6 one 1G 2 2560x1600 8 8

GRID M6-2q GRID M6 one 2G 4 2560x1600 4 4

GRID M6-4q GRID M6 one 4G 4 3840x2160 2 2

GRID M6-8q GRID M6 one 8G 4 3840x2160 1 1

Physical

Board

Physical

GPUs

FB Per

Virtual GPU

Display

Heads

Maximum

Resolution

Physical

GPU

Maximum

Virtual GPUs

Per Physical

Board

Install the NVIDIA GRID vGPU Display Driver

To install the NVIDIA GRID vGPU display driver, you must disable the default NVIDIA driver, download
the NVIDIA display drivers, and configure the PCI device on the virtual machine.

Prerequisites

n

Verify that you downloaded the vGPU software package from the NVIDIA download site,
uncompressed the package, and have the Linux Display Driver (a package component) ready. See

Install the VIB for the NVIDIA GRID vGPU Graphics Card on the ESXi Host.

VMware, Inc. 39

Setting Up Horizon 7 for Linux Desktops

Also verify that a shared PCI device was added to the virtual machine. See Configure a Shared PCI

Device for vGPU on the Linux Virtual Machine

Procedure

1 Disable and blacklist the default NVIDIA Nouveau driver.

a Edit the grub.conf or grub file.

For RHEL 6, the file is /boot/grub/grub.conf. For RHEL 7, the file is /etc/default/grub.

RHEL Version Command

6

sudo vi /boot/grub/grub.conf

7

sudo vi /etc/default/grub

b Add the rdblacklist=nouveau line at the end of the kernel options.

c Edit the blacklist.conf file.

sudo vi /etc/modprobe.d/blacklist.conf

d Add the following line anywhere in the blacklist.conf file.

blacklist nouveau

2 Restart the virtual machine.

The display has a changed look and feel.

3 (Optional) Verify that the Nouveau driver is disabled.

/sbin/lsmod | grep nouveau

If the grep search does not return any results, the Nouveau driver is disabled.

4 Copy the NVIDIA Linux Display Driver to the virtual machine.

5 Open a remote terminal to the virtual machine, or switch to a text console by typing Ctrl-Alt-F2, log in

as root, and run the init 3 command to disable X Windows.

6 Install additional components that are required for the NVIDIA driver.

sudo yum install gcc-c++

sudo yum install kernel-devel-$(uname -r)

sudo yum install kernel-headers-$(uname -r)

7 Add an executable flag to the NVIDIA GRID vGPU driver package.

chmod +x NVIDIA-Linux-x86_64-version-grid.run

VMware, Inc. 40

Setting Up Horizon 7 for Linux Desktops

8 Start the NVIDIA GRID vGPU installer.

sudo ./NVIDIA-Linux-x86_64-version-grid.run

9 Accept the NVIDIA software license agreement and select Yes to automatically update the X

configuration settings.

What to do next

Install Horizon Agent on the Linux virtual machine. See Install Horizon Agent on a Linux Virtual Machine.

Create a desktop pool that contains the configured Linux virtual machines. See Create a Manual Desktop

Pool for Linux.

Verify That the NVIDIA Display Driver Is Installed

You can verify that the NVIDIA display driver is installed on a RHEL 6 virtual machine by displaying the
NVIDIA driver output in a View desktop session.

Prerequisites

n

Check that you installed the NVIDIA display driver.

n

Verify that Horizon Agent is installed on the Linux virtual machine. See Install Horizon Agent on a

Linux Virtual Machine.

n

Verify that the Linux virtual machine is deployed in a desktop pool. See Create a Manual Desktop

Pool for Linux.

Procedure

1 Restart the Linux virtual machine.

The Horizon Agent startup script initializes the X server and display topology.

You can no longer view the virtual machine display in the vSphere console.

2 From Horizon Client, connect to the Linux desktop.

3 In the Linux desktop session, verify that the NVIDIA display driver is installed.

Open a terminal window and run the glxinfo | grep NVIDIA command.

The NVIDIA driver output is displayed. For example:

[root]# glxinfo | grep NVIDIA

server glx vendor string: NVIDIA Corporation

client glx vendor string: NVIDIA Corporation

OpenGL vendor string: NVIDIA Corporation

OpenGL version string: 4.5.0 NVIDIA 346.47

OpenGL shading language version string: 4.50 NVIDIA

The user can access the NVIDIA graphics capabilities on the remote desktop.

VMware, Inc. 41

Setting Up Horizon 7 for Linux Desktops

After verifying the installation of NVIDIA display driver, perform the following tasks for installation to work
correctly.

n

If you upgrade the Linux kernel, Horizon Agent might not be able to communicate with View
Connection Server. To resolve the problem, reinstall the NVIDIA driver.

n

Set the NVIDIA GRID licensing in the Linux VM. See NVIDIA documentation for more information.
Linux desktop will not work correctly if licensing is not set. For example, auto-fit will not work.

Configure RHEL 6 for vDGA

You can set up an RHEL 6 guest operating system so that Horizon 7 for Linux desktop can take
advantage of vDGA capabilities on the ESXi host.

Caution Before you begin, verify that Horizon Agent is not installed on the Linux virtual machine. If you

install Horizon Agent before you configure the machine to use vDGA, required configuration parameters
in the xorg.conf file are overwritten, and vDGA does not work. You must install Horizon Agent after the
vDGA configuration is completed.

Enable DirectPath I/O for NVIDIA GRID on a Host

Before you configure a Linux virtual machine to use vDGA, you must make the NVIDIA GRID GPU PCI
devices available for DirectPath I/O passthrough on the ESXi host.

Prerequisites

n

Verify that vSphere 6.0 or a later release is installed in your environment.

n

Verify that the NVIDIA GRID K1 or K2 graphics cards are installed on the ESXi host.

Procedure

1 In the vSphere Web Client, browse to the ESXi host.

2 Click the Manage tab and click Settings.

3 In the Hardware section, click PCI Devices.

4 To enable DirectPath I/O passthrough for the NVIDIA GRID GPUs, click Edit.

Icon Description

Green icon The PCI device is active and can be enabled.

Orange icon The state of the device has changed. You must reboot the host before you can

use the device.

5 Select the NVIDIA GRID GPUs and click OK.

The PCI devices are added to the table, DirectPath I/O PCI Devices Available to VMs.

6 Reboot the host to make the PCI devices available for use by the Linux virtual machines.

VMware, Inc. 42

Setting Up Horizon 7 for Linux Desktops

Add a vDGA Pass-Through Device to a RHEL 6 Virtual Machine

To configure a RHEL 6 virtual machine to use vDGA, you must add the PCI device to the virtual machine.
With this step, the physical device on the ESXi host can be passed through for use on the virtual
machine.

Prerequisites

n

Verify that the Linux virtual machine is prepared for use as a desktop. See Create a Virtual Machine

and Install Linux and Prepare a Linux Machine for Remote Desktop Deployment.

n

Verify that Horizon Agent is not installed on the Linux virtual machine.

n

Verify that the NVIDIA GRID GPU PCI device was made available for DirectPath I/O pass-through on
the host. See Enable DirectPath I/O for NVIDIA GRID on a Host.

Procedure

1 Log in to the RHEL 6 guest operating system as a local user configured with sudo rights.

2 In vSphere Web Client, select the virtual machine and, under the VM Hardware tab, click Edit

Settings.

3 In the New device menu, select PCI Device.

4 Click Add and select the PCI device from the drop-down menu.

5 Click Reserve all memory and click OK.

You must reserve all virtual machine memory to enable the GPU to support vDGA.

6 Power on the virtual machine and open vSphere console to connect to the machine.

7 Verify that the NVIDIA GRID device is passed through to the virtual machine.

Open a terminal window and run the following command:

lspci | grep NVIDIA

The XX:00.0 VGA-compatible controller is displayed. For example:

NVIDIA Corporation GK104GL [GRID K2]

Install the NVIDIA Display Driver for vDGA

To install the NVIDIA display driver for vDGA, you must disable the default NVIDIA driver, download the
NVIDIA display drivers, and configure the PCI device on the virtual machine.

Prerequisites

n

Verify that the PCI device was added to the RHEL 6 virtual machine. See Add a vDGA Pass-Through

Device to a RHEL 6 Virtual Machine.

VMware, Inc. 43

Setting Up Horizon 7 for Linux Desktops

Procedure

1 Disable and blacklist the default NVIDIA Nouveau driver.

a Edit the grub.conf file.

For RHEL 6, the file is /boot/grub/grub.conf.

RHEL Version Command

6

sudo vi /boot/grub/grub.conf

b Add the rdblacklist=nouveau line at the end of the kernel options.

c Edit the blacklist.conf file.

sudo vi /etc/modprobe.d/blacklist.conf

d Add the following line anywhere in the blacklist.conf file.

blacklist nouveau

2 Restart the virtual machine.

The display has a changed look and feel.

3 (Optional) Verify that the Nouveau driver is disabled.

/sbin/lsmod | grep nouveau

If the grep search does not return any results, the Nouveau driver is disabled.

4 Download the NVIDIA driver from the NVIDIA Driver Downloads site.

Select the appropriate driver version from the NVIDIA drop-down menus:

Option Description

Product Type GRID

Product Series GRID Series

Product Select the version (such as GRID K2) that is installed on the ESXi host.

Operating System Linux 64-bit or Linux 32-bit

5 Open a remote terminal to the virtual machine, or switch to a text console by typing Ctrl-Alt-F2, log in

as root, and run the init 3 command to disable X Windows.

6 Install additional components that are required for the NVIDIA driver.

sudo yum install gcc-c++

sudo yum install kernel-devel-$(uname -r)

sudo yum install kernel-headers-$(uname -r)

VMware, Inc. 44

Setting Up Horizon 7 for Linux Desktops

7 Add an executable flag to the NVIDIA driver package for vDGA.

chmod +x NVIDIA-Linux-x86_64-version.run

8 Start the NVIDIA installer.

sudo ./NVIDIA-Linux-x86_64-version.run

9 Accept the NVIDIA software license agreement and select Yes to automatically update the X

configuration settings.

What to do next

Install Horizon Agent on the Linux virtual machine. See Install Horizon Agent on a Linux Virtual Machine.

Create a desktop pool that contains the configured Linux virtual machines. See Create a Manual Desktop

Pool for Linux.

Verify That the NVIDIA Display Driver Is Installed

You can verify that the NVIDIA display driver is installed on a RHEL 6 virtual machine by displaying the
NVIDIA driver output in a View desktop session.

Prerequisites

n

Check that you installed the NVIDIA display driver.

n

Verify that Horizon Agent is installed on the Linux virtual machine. See Install Horizon Agent on a

Linux Virtual Machine.

n

Verify that the Linux virtual machine is deployed in a desktop pool. See Create a Manual Desktop

Pool for Linux.

Procedure

1 Restart the Linux virtual machine.

The Horizon Agent startup script initializes the X server and display topology.

You can no longer view the virtual machine display in the vSphere console.

2 From Horizon Client, connect to the Linux desktop.

VMware, Inc. 45

Setting Up Horizon 7 for Linux Desktops

3 In the Linux desktop session, verify that the NVIDIA display driver is installed.

Open a terminal window and run the glxinfo | grep NVIDIA command.

The NVIDIA driver output is displayed. For example:

[root]# glxinfo | grep NVIDIA

server glx vendor string: NVIDIA Corporation

client glx vendor string: NVIDIA Corporation

OpenGL vendor string: NVIDIA Corporation

OpenGL version string: 4.5.0 NVIDIA 346.47

OpenGL shading language version string: 4.50 NVIDIA

The user can access the NVIDIA graphics capabilities on the remote desktop.

After verifying the installation of NVIDIA display driver, perform the following tasks for installation to work
correctly.

n

If you upgrade the Linux kernel, Horizon Agent might not be able to communicate with View
Connection Server. To resolve the problem, reinstall the NVIDIA driver.

n

Set the NVIDIA GRID licensing in the Linux VM. See NVIDIA documentation for more information.
Linux desktop will not work correctly if licensing is not set. For example, auto-fit will not work.

Configure RHEL 7 for vSGA

You can set up an RHEL 7 guest operating system so that a Horizon 7 for Linux desktop can take
advantage of vSGA capabilities.

Install the VIB for the NVIDIA Graphics Card for vSGA on the ESXi Host

You must download and install the VIB for your NVIDIA GRID graphics card on the ESXi 6.0 U1 or later
host.

NVIDIA provides a VMware vSphere ESXi Driver for vSGA. For vSGA, an NVIDIA display driver is not
installed on the Linux virtual machine.

Prerequisites

n

Verify that vSphere 6.0 U1 or a later release is installed in your environment.

n

Verify that NVIDIA driver is installed in your environment.

n

Verify that the NVIDIA GRID K1 or K2 GPUs are installed on the ESXi host.

VMware, Inc. 46

Setting Up Horizon 7 for Linux Desktops

Procedure

1 Download the VIB for your NVIDIA GRID vGPU graphics card from the NVIDIA Driver Downloads

site.

Select the appropriate VIB version from the drop-down menus.

Option Description

Product Type GRID

Product Series Select GRID Series.

Product Select the version (such as GRID K2) that is installed on the ESXi host.

Operating System Select the VMware vSphere ESXi version.

2 Upload the VMware vSphere ESXi Driver for vSGA to the ESXi 6.0 U1 host.

3 Power off or suspend all virtual machines on the ESXi host.

4 Connect to the ESXi host using SSH.

5 Stop the xorg service.

# /etc/init.d/xorg stop

6 Install the NVIDIA VIB.

For example:

# esxcli system maintenanceMode set --enable true

# esxcli software vib install -v /path-to-vib/NVIDIA-VIB-name.vib

# esxcli system maintenanceMode set --enable false

7 Restart xorg, which is used for GPU assignment:

# /etc/init.d/xorg start

8 Reboot the ESXi host.

9 Verify that the xorg service is running after the host is restarted.

Configure 3D Capabilities for vSGA on the Linux Virtual Machine

To configure a RHEL 7 virtual machine to use vSGA, you must configure 3D settings for the virtual
machine's video card in vSphere Web Client.

Prerequisites

n

Verify that the Linux virtual machine is prepared for use as a desktop, Horizon Agent is installed, and
the machine is deployed in a desktop pool.

n

Verify that the NVIDIA VIB is installed on the ESXi host. See Install the VIB for the NVIDIA Graphics

Card for vSGA on the ESXi Host.

VMware, Inc. 47

Setting Up Horizon 7 for Linux Desktops

Procedure

1 Power off the virtual machine.

2 In vSphere Web Client, select the virtual machine and, under the VM Hardware tab, click Edit

Settings.

3 In the Virtual Hardware tab, click Video card to expand the menu settings.

4 Set the Total video memory to 128 MB.

5 For 3D Graphics, select Enable 3D Support.

6 For 3D Renderer, select Hardware from the drop-down menu.

7 For 3D Memory, select a suitable value for your application requirements.

If your users connect to more than 3 monitors, set this value to at least 1024 MB.

8 Click OK.

9 Power on the virtual machine.

What to do next

Verify that vSGA is running on the Linux virtual machine.

Next, install Horizon Agent on the Linux virtual machine. See Install Horizon Agent on a Linux Virtual

Machine.

Verify that vSGA is Running on a Linux Virtual Machine

You can verify that vSGA is running on a RHEL 7 virtual machine by checking the virtual machine log file
and checking the guest operating system.

Procedure

1 Open the vmware.log file for the virtual machine.

If a supported GPU and NVIDIA VIB are installed correctly, the log file displays lines such as those in
the following example:

2015-06-24T22:19:25.259Z| mks| I120: OpenGL Version: "4.0.0 NVIDIA 346.69" (4.0.0)

2015-06-24T22:19:25.259Z| mks| I120: GLSL Version: "4.00 NVIDIA" (4.00.0)

2015-06-24T22:19:25.259Z| mks| I120: OpenGL Vendor: "NVIDIA Corporation"

2015-06-24T22:19:25.259Z| mks| I120: OpenGL Renderer: "Quadro 4000/PCIe/SSE2"

VMware, Inc. 48

Setting Up Horizon 7 for Linux Desktops

If a supported GPU and NVIDIA VIB are not installed correctly, the virtual machine uses the Software
Renderer. The vmware.log file displays lines such as those in the following example:

2015-07-06T17:09:26.423Z| vmx| I120: [msg.mks.noGPUResourceFallback] Hardware GPU resources are

not available. The virtual machine uses software rendering.

2015-07-06T17:09:26.423Z| vmx| I120: ----------------------------------------

2015-07-06T17:09:26.425Z| svga| I120: MKS-SWP: plugin started - llvmpipe (LLVM 3.3, 256 bits)

2015-07-06T17:09:26.426Z| svga| I120: Started Shim3D

2015-07-06T17:09:26.426Z| svga| I120: MKS-RenderMain: Starting SWRenderer

2 In the guest operating system on the virtual machine, type the following command.

glxinfo|grep Gallium

If vSGA is working, the command returns the following text:

OpenGL renderer string: Gallium 0.4 on SVGA3D; build : RELEASE;

If vSGA is not working correctly, the command returns the following text:

OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 256 bits)

What to do next

Install Horizon Agent on the Linux virtual machine. See Install Horizon Agent on a Linux Virtual Machine.

VMware, Inc. 49

Installing Horizon Agent 5

You must install Horizon Agent on the Linux desktops so that View Connection Server can communicate
with and manage the desktops.

This chapter includes the following topics:

n

Install Horizon Agent on a Linux Virtual Machine

n

Configure the Certificate for Linux Agent

n

Upgrading the Horizon Agent on a Linux Virtual Machine

n

Uninstall Horizon 7 for Linux Machines

Install Horizon Agent on a Linux Virtual Machine

You must install Horizon Agent on a Linux virtual machine before you can deploy the machine as a
remote desktop.

Beginning with Horizon 7.0.1 release, Horizon Agent for Linux uses vCenter managed virtual machines.
The managed virtual machines provide the following enhancements.

n

vCenter is a mandatory requirement for Linux desktop deployment.

n

Horizon Agent installation on Linux does not require registration.

n

For a large number of Linux desktop deployment, you can install the Horizon Agent on the base
virtual machine.

Caution If you intend to use NVIDIA GRID vGPU, vDGA, or vSGA, you must configure these 3D

features on the Linux virtual machine before you install Horizon Agent. If you install Horizon Agent first,
required parameters in the xorg.conf file are overwritten, and the 3D graphics features do not work.

See Configure Supported RHEL Distributions for vGPU, Configure RHEL 6 for vDGA, or Configure RHEL

7 for vSGA. Install Horizon Agent after the 3D graphics configuration is completed.

For 2D graphics configuration, you can install Horizon Agent after you complete the steps in Prepare a

Linux Machine for Remote Desktop Deployment.

Prerequisites

n

Verify that the Linux guest operating system is prepared for desktop use. See Prepare a Linux

Machine for Remote Desktop Deployment.

VMware, Inc.

50

Setting Up Horizon 7 for Linux Desktops

n

Familiarize yourself with the Horizon Agent installer script for Linux. See install_viewagent.sh

Command-Line Options.

Procedure

1 Download the Horizon Agent for Linux installer file from the VMware download site at

https://my.vmware.com/web/vmware/downloads.

Under Desktop & End-User Computing, select the VMware Horizon 7 download, which includes the
Horizon Agent for Linux installer.

The installer filename is VMware-horizonagent-linux-x86_64-y.y.y-xxxxxxx.tar.gz for 64-bit Linux
where y.y.y is the version number and xxxxxxx is the build number.

2 Unpack the tarball for your Linux distribution on the guest operating system.

For example:

tar -xzvf <View Agent tar ball>

3 Navigate to the tar ball folder.

4 Run the install_viewagent.sh script as superuser.

See install_viewagent.sh Command-Line Options for a list of the command line options.

For example:

sudo ./install_viewagent.sh

5 Type Yes to accept the EULA if you run install_viewagent.sh without specifying the -A option.

The installer does not run unless you accept the EULA.

6 Reboot Linux for the changes to take effect.

After installation, the viewagent service is started. Verify that the service is started using sudo service
viewagent status.

What to do next

Deploy the virtual machine in a desktop pool. See Create a Manual Desktop Pool for Linux.

install_viewagent.sh Command-Line Options

The install_viewagent.sh script installs Horizon Agent on a Linux guest operating system.

Use the following form of the install_viewagent.sh script in a command window in the gnome desktop
environment.

install_viewagent.sh command_option argument [command_option argument] . . .

The install_viewagent.sh script includes mandatory and optional parameters.

VMware, Inc. 51

Setting Up Horizon 7 for Linux Desktops

Table 5‑1. install_viewagent.sh Optional but Required Parameter

Optional

Parameter

(Required

Information) Description

-A yes |no Accept or refuse the End User License Agreement (EULA) and Federal Information Processing Standards
(FIPS) statement. You must specify yes for the install to proceed.

Table 5‑2. install_viewagent.sh Optional Parameters

Optional

Parameters Description

-a yes|no Install or bypass audio input redirection support. Default is yes.

-f yes|no Install or bypass support of the cryptographic modules designed for Federal Information Processing Standards

(FIPS) 140-2. Default is no. For more information, see the FIPS 140-2 Mode description in Features of

Horizon Linux Desktops.

-j JMS SSL keystore password. By default, installer generates a random string.

-m yes|no Install or bypass the smart card redirection support. Default is no.

-r yes|no Restart the system automatically after installation. Default is no.

-s Self signed cert subject DN. By default, installer uses Blast.

-C yes|no Install or bypass Clipboard Redirection support. Default is yes.

-F yes|no Install or bypass CDR support. Default is yes.

-M yes|no Upgrade the Linux Agent to managed or unmanaged agent. Default is yes.

-S yes|no Install or bypass Single Sign-On (SSO) support. Default is yes.

-U yes|no Install or bypass USB support. Default is no.

VMware, Inc. 52

Setting Up Horizon 7 for Linux Desktops

Table 5‑3. Examples of install_viewagent.sh Parameters

Condition Examples

Fresh Installation

Upgrade from an
unmanaged virtual
machine and retain
the unmanaged
virtual machine
style

Upgrade from an
unmanaged virtual
machine
deployment and
convert to a
managed virtual
machine style. The
upgrade requires
new desktop pool
creation on broker

sudo ./install_viewagent.sh -A yes

Fresh installation always requires a new desktop pool creation.

sudo ./install_viewagent.sh -A yes -M no

This type of upgrade does not require a new desktop pool creation. You can reuse the existing desktop pool.

Note To ensure the best possible performance, do not use an unmanaged virtual machine.

sudo ./install_viewagent.sh -A yes

This type of upgrade requires a new desktop pool creation. You must delete the existing desktop pool.

Configure the Certificate for Linux Agent

When you install Linux Agent, the installer generates a self-signed certificate for VMwareBlastServer.

n

When the Blast Security Gateway is disabled on the broker, VMwareBlastServer presents this
certificate to the browser that uses HTML Access to connect to the Linux Desktop.

n

When the Blast Security Gateway is enabled on the broker, Blast Security Gateway's certificate
presents the certificate to the browser.

To comply with industry or security regulations, you can replace the self-signed certificate with a certificate
that is signed by a Certificate Authority (CA).

Procedure

1 Install the private key and the certificate to VMwareBlastServer.

a Rename the private key to rui.key and the certificate to rui.crt .

b Run sudo chmod 550 /etc/vmware/ssl.

c Copy the rui.crt and rui.key to /etc/vmware/ssl.

d Run chmod 440 /etc/vmware/ssl.

2 Install the root and intermediate Certificate Authority into the Linux OS Certificate Authority store.

Note Check your Linux distribution documentation for the Linux system settings change.

VMware, Inc. 53

Setting Up Horizon 7 for Linux Desktops

Upgrading the Horizon Agent on a Linux Virtual Machine

You can upgrade Horizon Agent on a Linux virtual machine by installing the latest version of Horizon
Agent.

Unmanaged virtual machine: The agent installer registers the virtual machine to the broker which requires
broker admin information. The Desktop Pool Creation wizard uses Other Sources in the Machine
Source page to select the registered virtual machine.

Managed virtual machine: The installer does not communicate with the broker. The Desktop Pool
Creation wizard uses vCenter virtual machines in the Machine Source page to select the virtual
machines through vCenter. The managed virtual machine deployment supports the following functions.

n

Remote Machine Power Policy

n

Allow users to reset their machines

Note Horizon Agent for Linux 7.0.0 and earlier versions functioned as unmanaged virtual machines. The

Horizon Agent for Linux 7.0.1 functions as managed virtual machine support.

You can use the following methods to upgrade from unmanaged to a managed virtual machine
deployment.

n

Retain the unmanaged virtual machine deployment and upgrade to the required version. This type of
upgrade does not require any configuration modifications in View Connection Server.

n

Upgrade from an unmanaged virtual machine deployment to a managed virtual machine deployment
to any version. This type of upgrade requires a new desktop pool creation on the View Connection
Server.

Note For the upgrade from a managed virtual machine deployment, you can retain the managed virtual

machine deployment and upgrade to the required version. However, to convert the managed virtual
machine deployment to an unmanaged virtual machine deployment during an upgrade is not supported.

The following parameters are available for upgrade.

Table 5‑4. Optional Parameters for Upgrading the Horizon Agent

Parameter Description

-A yes EULA and FIPS statement acceptance. You must specify yes for the install to proceed. If this parameter is not

specified, the install script prompts for the value.

-a yes|no Install or bypass audio input redirection support.

-f yes|no Install or bypass support of the cryptographic modules designed for Federal Information Processing Standards

(FIPS) 140-2. Default is no. For more information, see the FIPS 140-2 Mode description in Features of Horizon

Linux Desktops.

-m yes|no Install or bypass the smart card redirection support. Default is no.

-r yes|no Reboot the operating system after installation. The default is no.

-C yes|no Install or bypass Clipboard Redirection support. Default is yes.

VMware, Inc. 54

Setting Up Horizon 7 for Linux Desktops

Table 5‑4. Optional Parameters for Upgrading the Horizon Agent (Continued)

Parameter Description

-F yes|no Install or bypass CDR support. Default is yes.

-M yes|no Upgrade the Linux Agent to managed|unmanaged agent. The default value is yes.

-S yes|no Install or bypass SingleSignOn (SSO) support. Default is yes.

-U yes|no Install or Bypass USB support. Default is no.

Upgrade Horizon Agent on a Linux Virtual Machine

You can upgrade Horizon Agent on a Linux machine by installing the latest version of Horizon Agent..

Prerequisites

n

Verify that the VMwareBlastServer process is not running.

To stop this process, ensure that the user logs off the machine and no desktop session is active, or
reboot the machine.

Procedure

1 Download the latest Horizon Agent for Linux installer file from the VMware download site at

https://my.vmware.com/web/vmware/downloads.

Under Desktop & End-User Computing, select the VMware Horizon 7 download, which includes the
Horizon Agent for Linux installer.

The installer filename is VMware-viewagent-linux-x86_64-y.y.y-xxxxxxx.tar.gz for 64-bit Linux where
y.y.y is the version number and xxxxxxx is the build number.

2 Unpack the tarball for your Linux distribution on the guest operating system.

For example:

tar -xzvf <View Agent tar ball>

3 Navigate to the tar ball folder.

VMware, Inc. 55

Setting Up Horizon 7 for Linux Desktops

4 Run the install_viewagent.sh script to upgrade unmanaged virtual machines using one of the

following deployment scenarios:

Option Description

Upgrade an unmanaged virtual

machine deployment and retain the

unmanaged virtual machine

deployment

sudo ./install_viewagent.sh -A yes -M no

Note To ensure the best possible performance, do not use an unmanaged virtual

machine.

Upgrade an unmanaged virtual

machine deployment and change it to

managed virtual machine deployment

Upgrade a managed virtual machine

deployment

sudo ./install_viewagent.sh -A yes -M yes

Note In View Administrator, delete the existing desktop pool for unmanaged

virtual machine deployment and create a new desktop pool for managed virtual
machine deployment. For more info, see Create a Manual Desktop Pool for Linux.

sudo ./install_viewagent.sh -A yes -M yes

Note After upgrading, your existing desktop pool can be reused.

Uninstall Horizon 7 for Linux Machines

To uninstall Horizon 7 for Linux on a virtual machine, you must uninstall Horizon Agent and remove
configuration files.

Prerequisites

Verify that the VMwareBlastServer process is not running. To stop this process, ensure that you log off the
machine and no desktop session is active, or reboot the machine.

Procedure

1 Open a terminal window on the virtual machine and run the Horizon Agent uninstall script.

sudo /usr/lib/vmware/viewagent/bin/uninstall_viewagent.sh

The script stops the Horizon Agent processes, deletes the Horizon Agent service and software from
installation directory /usr/lib/vmware/viewagent.

2 Manually delete the Horizon 7 for Linux configuration files at /etc/vmware directory.

VMware, Inc. 56

Configuration Options for Linux

Desktops 6

You can configure various options to customize the user experience using configuration files.

This chapter includes the following topics:

n

Setting Options in Configuration Files on a Linux Desktop

n

Example Blast Settings for Linux Desktops

n

Examples of Client Drive Redirection Options for Linux Desktops

n

Suppress the vSphere Console Display of a Linux Desktop

Setting Options in Configuration Files on a Linux Desktop

You can configure certain options by adding entries to the files /etc/vmware/config
or /etc/vmware/viewagent-custom.conf.

During the installation of View Agent or Horizon Agent, the installer copies two configuration template
files, config.template and viewagent-custom.conf.template, to /etc/vmware. In addition,
if /etc/vmware/config and /etc/vmware/viewagent-custom.conf do not exist, the installer copies
config.template to config and viewagent-custom.conf.template to viewagent-custom.conf. In
the template files, all the configuration options are listed and documented. To set an option, simply
remove the comment and change the value as appropriate.

For example, the following line in /etc/vmware/config enables the lossless PNG mode.

RemoteDisplay.alwaysLossless=TRUE

After you make configuration changes, reboot Linux for the changes to take effect.

VMware, Inc.

57

Setting Up Horizon 7 for Linux Desktops

Configuration Options in /etc/vmware/config

VMwareBlastServer and its related plug-ins use the configuration file /etc/vmware/config.

Note The following table includes description for each agent-enforced policy setting for USB in the

Horizon Agent configuration file. Horizon Agent uses the settings to decide if a USB can be forwarded to
the host machine. Horizon Agent also passes the settings to Horizon Client for interpretation and
enforcement according to whether you specify the merge (m) modifier to apply the Horizon Agent filter
policy setting in addition to the Horizon Client filter policy setting, or override the (o) modifier to use the
Horizon Agent filter policy setting instead of the Horizon Client filter policy setting.

Table 6‑1. Configuration Options in /etc/vmware/config

Option Value/Format Default Description

RemoteDisplay.alwaysLossless true or false

mksVNCServer.useUInputButton
Mapping

RemoteDisplay.allowAudio true or false

VVC.ScRedir.Enable true or false

VVC.logLevel fatal error,

VVC.RTAV.Enable true or false

Clipboard.Direction 0, 1, 2, or 3

true or false

warn, info, debug,
or trace

false

false

true

true

info

true

2

Graphic applications, especially graphic design
applications, require pixel-exact rendering of images in
the client display of a Linux desktop. You can configure
a lossless PNG mode for images and video playback
that are generated on a Linux desktop and rendered on
the client device. This feature uses additional
bandwidth between the client and the ESXi host.

Set this option to enable the support of a left-handed
mouse on Ubuntu or RHEL 7. CentOS and RHEL 6
support a left-handed mouse and you do not need to
set this option.

Set this option to enable/disable audio out.

Set this option to enable/disable smart card redirection.

Use this option to set the log level of the VVC proxy
node.

Set this option to enable/disable audio input.

Use this option to specify the clipboard redirection
policy. Valid values are as follows:

n

0 - Disable clipboard redirection.

n

1 - Enable clipboard redirection in both directions.

n

2 - Enable clipboard redirection from client to
remote desktop only.

n

3 - Enable clipboard redirection from remote
desktop to client only.

cdrserver.logLevel error, warn, info,

debug, traceor

verbose

cdrserver.forcedByAdmin true or false

VMware, Inc. 58

info

false

Use this option to set the log level for vmware­CDRserver.log file.

Set this option to control whether the client can share
additional folders that are not specified with the
cdrserver.shareFolders option.

Setting Up Horizon 7 for Linux Desktops

Table 6‑1. Configuration Options in /etc/vmware/config (Continued)

Option Value/Format Default Description

cdrserver.sharedFolders

cdrserver.permissions

file_path1,R;fi

undefined Specify one or more file paths to the folders that the

le-path2,;

file_path3,R; .

..

R RW

client can share with the Linux desktop. For example:

n

For a Windows client:

C:\spreadsheets,;D:\ebooks,R

n

For a non-Windows
client: /tmp/spreadsheets;/tmp/ebooks,;/hom

e/finance,R

Use this option to apply additional read/write
permissions that Horizon Agent has on the folders
shared by Horizon Client. For example:

n

If the folder shared by Horizon Client has read and
write permissions and you set

cdrserver.permissions=R, then Horizon Agent
has only read access permissions.

n

If the folder shared by Horizon Client has only
read permissions and you set
cdrserver.permissions=RW, Horizon Agent still
has only read access rights. Horizon Agent cannot
change the read only attribute that was set by
Horizon Client. Horizon Agent can only remove the
write access rights.

Typical uses are as follows:

n

cdrserver.permissions=R

n

#cdrserver.permissions=R (for example,
comment it out or delete the entry)

cdrserver.cacheEnable true or false

UsbRedirPlugin.log.logLevel error, warn, info,

debug, trace, or

verbose

UsbRedirServer.log.logLevel error, warn, info,

debug, trace, or

verbose

viewusb.AllowAutoDeviceSplitting

{m|o}:

{true|false}

viewusb.SplitExcludeVidPid

{m|o}:vid-

xxx1_pid-

yyy1[;vid-

xxx2_pid-

yyy2;...]

true

Set this option to enable or disable the write caching
feature from the agent towards the client side.

info

Use this option to set the log level for the USB
Redirection plugin.

info

Use this option to set the log level for the USB
Redirection server.

undefined,
which
equates to

Set this option to allow or disallow the automatic
splitting of composite USB devices.

Example: m:true

false

undefined Use this option to exclude or include a specified

composite USB device from splitting by Vendor and
Product IDs . The format of the setting is
vid-xxx1_pid-yyy1[;vid-xxx2_pid-yyy2;...].
You must specify ID numbers in hexadecimal. You can
use the wildcard character (*) in place of individual
digits in an ID.

Example: m:vid-0f0f_pid-55**

VMware, Inc. 59

Setting Up Horizon 7 for Linux Desktops

Table 6‑1. Configuration Options in /etc/vmware/config (Continued)

Option Value/Format Default Description

viewusb.SplitVidPid

viewusb.AllowAudioIn

{m|o}: vid-

xxxx_pid-

yyyy([exintf:zz

[;exintf:ww]])

[;...]

{m|o}:

{true|false}

undefined Set this option to treat the components of a composite

USB device specified by Vendor and Product IDs as
separate devices. The format of the setting is
vid-xxxx_pid-yyyy(exintf:zz[;exintf:ww]).

You can use the exintf keyword to exclude
components from redirection by specifying their
interface number. You must specify ID numbers in
hexadecimal, and interface numbers in decimal
including any leading zero. You can use the wildcard
character (*) in place of individual digits in an ID.

Example:

o:vid-0f0f_pid-

***(exintf-01);vid-0781_pid-554c(exintf:

01;exintf:02)

Note Horizon does not automatically include the

components that you have not explicitly excluded. You
must specify a filter policy such as
Include VidPid Device to include those
components.

undefined,
which
equates to

true

Use this option to allow or disallow audio input devices
to be redirected. Example: o:false

viewusb.AllowAudioOut

viewusb.AllowHIDBootable

viewusb.AllowDevDescFailsafe

viewusb.AllowKeyboardMouse

viewusb.AllowSmartcard

{m|o}:

{true|false}

{m|o}:

{true|false}

{m|o}:

{true|false}

{m|o}:

{true|false}

{m|o}:

{true|false}

undefined,
which
equates to

false

undefined,
which
equates to

true

undefined,
which
equates to

false

undefined,
which
equates to

false

undefined,
which
equates to

false

Set this option to allow or disallow redirection of audio
output devices.

Use this option to allow or disallow the redirection of
input devices other than keyboards or mice that are
available at boot time, also known as HID-bootable
devices.

Set this option to allow or disallow devices to be
redirected even if Horizon Client fails to get the
configuration or device descriptors. To allow a device
even if it fails to get the configuration or device
descriptors, include it in the Include filters, such as
IncludeVidPid or IncludePath.

Use this option to allow or disallow the redirection of
keyboards with integrated pointing devices (such as a
mouse, trackball, or touch pad).

Set this option to allow or disallow smart card devices
to be redirected.

VMware, Inc. 60

Setting Up Horizon 7 for Linux Desktops

Table 6‑1. Configuration Options in /etc/vmware/config (Continued)

Option Value/Format Default Description

viewusb.AllowVideo

viewusb.DisableRemoteConfig

viewusb.ExcludeAllDevices

viewusb.ExcludeFamily

{m|o}:

{true|false}

{m|o}:

{true|false}

{true|false}

{m|o}:family_na

me_1[;family_na

me_2;...]

undefined,
which
equates to

true

undefined,
which
equates to

false

undefined,
which
equates to

false

undefined Use this option to exclude families of devices from

Use this option to allow or disallow video devices to be
redirected.

Set this option to disable or enable the use of
Horizon Agent settings when performing USB device
filtering.

Use this option to exclude or include all USB devices
from being redirected. If set to true, you can use other
policy settings to allow specific devices or families of
devices to be redirected. If set to false, you can use
other policy settings to prevent specific devices or
families of devices from being redirected. If you set the
value of ExcludeAllDevices to true on
Horizon Agent, and this setting is passed to
Horizon Client, the Horizon Agent setting overrides the
Horizon Client setting.

being redirected. For example:

m:bluetooth;smart-card

If you have enabled automatic device splitting, Horizon
examines the device family of each interface of a
composite USB device to decide which interfaces
should be excluded. If you have disabled automatic
device splitting, Horizon examines the device family of
the whole composite USB device.

viewusb.ExcludeVidPid

viewusb.ExcludePath

{m|o}:vid-xxx1_

pid-yyy1[;vid-

xxx2_pid-

yyy2;..]

{m|o}:bus-

x1[/y1].../

port-z1[;bus-

x2[/y2].../port

-z2;...]

Note Mice and keyboards are excluded from

redirection by default and do not need to be excluded
with this setting.

undefined Set this option to exclude devices with specified vendor

and product IDs from being redirected. You must
specify ID numbers in hexadecimal. You can use the
wildcard character (*) in place of individual digits in an
ID.

For example:

o:vid-0781_pid- ****;vid-0561_pid-554c

undefined Use this option to exclude devices at specified hub or

port paths from being redirected. You must specify bus
and port numbers in hexadecimal. You cannot use the
wildcard character in paths.

For
example:m:bus-1/2/3_port-

02;bus-1/1/1/4_port-ff

VMware, Inc. 61

Setting Up Horizon 7 for Linux Desktops

Table 6‑1. Configuration Options in /etc/vmware/config (Continued)

Option Value/Format Default Description

viewusb.IncludeFamily

viewusb.IncludePath

viewusb.IncludeVidPid

mksVNCServer.useXExtButtonMa
pping

mksvhan.clipboardSize An integer 1024 Use this option to specify the clipboard maximum size

RemoteDisplay.maxBandwidthKbpsAn integer 4096000 Specifies the maximum bandwidth in kilobits per

{m|

o}:family_name_

1[;family_name_

2]...

{m|o}:bus-

x1[/y1].../

port-z1[;bus-

x2[/y2].../port

z2;...]

{m|o}:vid-xxx1_

pid-yyy1[;vid-

xxx2_pid-

yyy2;...]

true or false

undefined Set this option to include families of devices that can

be redirected.

For example: o:storage; smart-card

undefined Use this option to include devices at specified hub or

port paths that can be redirected. You must specify bus
and port numbers in hexadecimal. You cannot use the
wildcard character in paths.

For example:
m:bus-1/2_port- 02;bus-1/7/1/4_port-0f

undefined Set this option to include devices with specified Vendor

and Product IDs that can be redirected. You must
specify ID numbers in hexadecimal. You can use the
wildcard character (*) in place of individual digits in an
ID.

For example:

o:vid-***_pid-0001;vid-0561_pid-554c

false

Set this option to enable or disable the support of a left­handed mouse on SLED 11 SP3.

to copy and paste.

second (kbps) for a VMware Blast session. The
bandwidth includes all imaging, audio, virtual channel,
and VMware Blast control traffic. The max value is 4
Gbps (4096000).

RemoteDisplay.maxFPS An integer 60 Specifies the maximum rate of screen updates. Use

this setting to manage the average bandwidth that
users consume. Valid value should be between 3 and

60. The default is 60 updates per second.

RemoteDisplay.enableStats true or false

RemoteDisplay.allowH264 true or false

vdpservice.log.logLevel fatal error,

warn, info, debug,
or trace

RemoteDisplay.qpmaxH264 available range of

values: 0-51

false

true

info

36 Use this option to set the H264minQP quantization

Enables or disables the VMware Blast display protocol
statistics in mks log, such as bandwidth, FPS, RTT,
and so on.

Set this option to enable or disable H.264 encoding.

Use this option to set the log level of the vdpservice.

parameter, which specifies the best image quality for
the remote display configured to use H.264 encoding.
Set the value to greater than the value set for
RemoteDisplay.qpminH264.

VMware, Inc. 62

Setting Up Horizon 7 for Linux Desktops

Table 6‑1. Configuration Options in /etc/vmware/config (Continued)

Option Value/Format Default Description

RemoteDisplay.qpminH264 available range of

values: 0-51

RemoteDisplay.minQualityJPEG available range of

values: 1-100

RemoteDisplay.midQualityJPEG available range of

values: 1-100

RemoteDisplay.maxQualityJPEG available range of

values: 1-100

10 Use this option to set the H264maxQP quantization

parameter, which specifies the lowest image quality for
the remote display configured to use H.264 encoding.
Set the value to less than the value set for
RemoteDisplay.qpmaxH264.

25 Specifies the image quality of the desktop display for

JPEG/PNG encoding. The low-quality settings are for
areas of the screen that change often, for example,
when scrolling occurs.

35 Specifies the image quality of the desktop display for

JPEG/PNG encoding. Use to set the medium-quality
settings of the desktop display.

90 Specifies the image quality of the desktop display for

JPEG/PNG encoding. The high-quality settings are for
areas of the screen that are more static, resulting in a
better image quality.

Configuration Options in /etc/vmware/viewagent-custom.conf

Java Standalone Agent uses the configuration file /etc/vmware/viewagent-custom.conf.

Table 6‑2. Configuration Options in /etc/vmware/viewagent-custom.conf

Option Value Default Description

Subnet NULL or

network
address
and mask
in IP
addres
s/CIDR
format

SSOEnable true or

false

NULL

true

If multiple local IP addresses have different subnets, use this
option to set the subnet that the Linux Agent provides to the
Connection Server instance.

When multiple subnet configurations are detected on a Linux
Agent machine, this option is required to specify the correct
subnet that should be used by the Linux Agent. For example,
if you installed Docker on the Linux machine, it will be
introduced as a virtual network adapter. To avoid Linux Agent
from using Docker as a virtual network adapter, you have to
set this option to use the real physical network adapter.

You must specify the value in IP address/CIDR format. For
example, Subnet=192.168.1.0/24.

NULL implies that the Linux Agent randomly selects the IP
address.

Set this option to enable/disable single sign-on (SSO).

VMware, Inc. 63

Setting Up Horizon 7 for Linux Desktops

Table 6‑2. Configuration Options in /etc/vmware/viewagent-custom.conf (Continued)

Option Value Default Description

SSOUserFormat A text

string

CDREnable true or

false

USBEnable true or

false

KeyboardLayoutSync true or

false

[username] Use this option to specify the format of the login name for

single sign-on. The default is the user name only. Set this
option if the domain name is also required. Typically, the login
name is the domain name plus a special character followed
by the user name. If the special character is the backslash,
you must escape it with another backslash. Examples of login
name formats are as follows:

n

SSOUserFormat=[domain]\\[username]

n

SSOUserFormat=[domain]+[username]

n

SSOUserFormat=[username]@[domain]

true

Set this option to enable or disable the Client Drive
Redirection (CDR) feature.

true

Set this option to enable or disable the USB Redirection
feature.

true

Use this option to specify whether to synchronize a client's
system locale list and current keyboard layout with
Horizon Agent for Linux desktops.

When this setting is enabled or not configured,
synchronization is allowed. When this setting is disabled,
synchronization is not allowed.

This feature is supported only for Horizon Client for Windows,
and only for the English, French, German, Japanese, Korean,
Spanish, Simplified Chinese, and Traditional Chinese locales.

StartBlastServerTime
out

An
integer

SSLCiphers A text

string

SSLProtocols A text

string

SSLCipherServerPref
erence

true or

false

20 This option determines the amount of time, in seconds, that

the VMwareBlastServer process has for initialization. If the
process is not ready within this timeout value, the user's login
will fail.

!aNULL:kECDH
+AESGCM:ECDH
+AESGCM:RSA

Use this option to specify the list of ciphers. You must use the
format that is defined in

https://www.openssl.org/docs/manmaster/man1/ciphers.html.

+AESGCM:kECDH
+AES:ECDH+AES:RSA
+AES

TLSv1_1:TLSv1_2 Use this option to specify the security protocols. The

supported protocols are TLSv1.0, TLSv1.1, and TLSv1.2.

true

Use this option to enable or disable the option

SSL_OP_CIPHER_SERVER_PREFERENCE. For more

information, see

https://www.openssl.org/docs/manmaster/ssl/SSL_CTX_set_o

ptions.html.

VMware, Inc. 64

Setting Up Horizon 7 for Linux Desktops

Table 6‑2. Configuration Options in /etc/vmware/viewagent-custom.conf (Continued)

Option Value Default Description

SSODesktopType

UseMATE

or

UseGnomeFlashback

or

UseKdePlasma

or

UseGnomeClassic

LogCnt An

integer

OfflineJoinDomain pbis or a

text string

This option specifies the desktop environment to use, instead

of the default desktop environment, when SSO is enabled.

You must first ensure that the chosen desktop environment is

installed on your desktop before specifying to use it. After this

option is set in an Ubuntu 14.04/16.04 desktop, the option

takes effect regardless if the SSO feature is enabled or not. If

this option is specified in a RHEL/CentOS 7.x desktop, the

chosen desktop environment is used only if SSO is enabled.

Note This option is not supported on RHEL/CentOS 6 and

SLED 11 desktops. See Desktop Environment for more

information on how to set up KDE as the default desktop

environment when SSO is enabled on these desktops.

-1 Use this option to set the reserved log file count

in /tmp/vmware-root.

n

-1 - keep all

n

0 - delete all

n

> 0 - reserved log count.

pbis

Use this option to set the instant-clone offline domain join.

Currently, the PowerBroker Identity Services Open (PBISO)

authentication is the only way to perform an offline domain

join. If this property has a value other than pbis, the offline

domain join is ignored.

RunOnceScript Use this option to rejoin the cloned virtual machine to Active

Directory.

Set the run once script after the host name has changed. The

specified script is executed only once after the first host name

change. The script is executed as root permission when the

agent service starts and host name has been changed since

agent installation.

For example, for the winbind solution, you must join the base

virtual machine to Active Directory with winbind, and set this

option to a script path. This must contain the domain rejoin

command /usr/bin/net ads join -U <ADUserName>

%<ADUserPassword>. After VM Clone, the operating system

customization changes the host name. When the agent

service starts, the script is executed to join the cloned virtual

machine to Active Directory.

RunOnceScriptTimeo
ut

120 Use this option to set the timeout time in seconds for the

RunOnceScript option.

For example, set RunOnceScriptTimeout=120

VMware, Inc. 65

Setting Up Horizon 7 for Linux Desktops

Note The three security options, SSLCiphers, SSLProtocols, and SSLCipherServerPreference are for

the VMwareBlastServer process. When starting the VMwareBlastServer process, the Java Standalone
Agent passes these options as parameters. When Blast Secure Gateway (BSG) is enabled, these options
affect the connection between BSG and the Linux desktop. When BSG is disabled, these options affect
the connection between the client and the Linux desktop.

Example Blast Settings for Linux Desktops

You can adjust the image quality of your remote desktop display to improve the user experience.
Improving image quality is helpful in maintaining a consistent user experience when there is a bad
network connection.

Example VMware Blast Extreme Protocol Settings

VMwareBlastServer and its related plug-ins use the configuration file /etc/vmware/config.

Table 6‑3. Example Blast Configuration Options in /etc/vmware/config

High-

speed

Option name Parameter

Bandwidth settings RemoteDisplay.maxB

andwidthKbps

Max FPS RemoteDisplay.maxFPS60 30 30 20 15 5

Audio Playback RemoteDisplay.allow

Audio

Display Quality
(JPEG/PNG)

Display Quality
(JPEG/PNG)

Display Quality
(JPEG/PNG)

Display Quality (H.

264)

Display Quality (H.

264)

RemoteDisplay.maxQ
ualityJPEG

RemoteDisplay.midQ
ualityJPEG

RemoteDisplay.minQ
ualityJPEG

RemoteDisplay.qpma
xH264

RemoteDisplay.qpmin
H264

LAN LAN

1000000
(1 Gbps)

TRUE TRUE TRUE TRUE TRUE FALSE

90 90 90 70 60 50

35 35 35 35 35 35

25 25 25 20 20 20

28 36 36 36 36 42

10 10 10 10 10 10

1000000
(1 Gbps)

Dedicated

WAN

1000000
(1 Gbps)

Broadban

d WAN

5000 (5
Mbps)

Low-

speed

WAN

2000 (2
Mbps)

Extremely Low

speed

1000 (1 Mbps)

Examples of Client Drive Redirection Options for Linux Desktops

Configure client drive redirection (CDR) options to determine whether a local system's shared folders and
drives can be accessed from the remote Linux desktops.

Configure CDR settings by adding entries to the /etc/vmware/config file.

VMware, Inc. 66

Setting Up Horizon 7 for Linux Desktops

The following configuration example shares the d:\ebooks and C:\spreadsheets folders, makes both
folders read-only, and prevents the client from sharing more folders.

cdrserver.forcedByAdmin=true

cdrserver.sharedFolders=d:\ebooks,;c:\spreadsheets,

cdrserver.permissions=R

In the previous example, the comma "," placed after ebooks and spreadsheets is mandatory for
correct option parsing.

Any "R" included in the cdrserver.sharedFoldersoption would impact all the folders listed in that
setting. In the following example, the ebooks and spreadsheets folders are both read-only even if the R
value is only placed after /home/jsmith folder path.

cdrserver.sharedFolders=d:\ebooks,;c:\spreadsheets,;/home/jsmith,R

Suppress the vSphere Console Display of a Linux Desktop

When a user connects to a Linux desktop, the desktop can also be displayed in the vSphere console for
the Linux virtual machine. You can configure Linux virtual machines to ensure that the vSphere console is
blank when users connect to their desktops.

Procedure

u

On the ESXi host, add the following line to the Linux virtual machine's vmx file.

RemoteDisplay.maxConnections = "0"

The vSphere console display remains blank even when you connect to the virtual machine when the
user is logged out of the desktop.

VMware, Inc. 67

Create and Manage Linux

Desktop Pools 7

To configure Linux virtual machines for use as remote desktops, you must create a desktop pool with
Linux virtual machines.

Horizon for Linux supports the following desktop pool types:

n

Manual desktop pool with vCenter virtual machine

n

Automated full-clone desktop pool

n

Instant-clone floating desktop pool

To create a manual desktop pool with a vCenter virtual machine, you must install Horizon Agent on all
virtual machines. Then, use the Connection Server desktop pool creation wizard to add the virtual
machines to the desktop pool. To clone a large number of virtual machines, see Overview of Bulk

Deployment of Linux Desktops.

To create an automated full-clone desktop pool, you must install Horizon 7 Agent on a Linux virtual
machine template. Then, use the Connection Server desktop pool creation wizard to clone full virtual
machines.

To create an instant clone floating desktop pool, you must install Horizon 7 Agent on a Linux virtual
machine with PBIS Open environment setup, and create a template from it. Then, use the Connection
Server desktop pool creation wizard to create instant-clone floating desktop pool.

This chapter includes the following topics:

n

Create a Manual Desktop Pool for Linux

n

Manage Desktop Pool for Linux

n

Create an Automated Full-Clone Desktop Pool for Linux

n

Create an Instant-Clone Floating Desktop Pool for Linux

n

Broker PowerCLI Commands

Create a Manual Desktop Pool for Linux

You can create a manual desktop pool for Linux virtual machines.

VMware, Inc.

68

Setting Up Horizon 7 for Linux Desktops

Prerequisites

n

Verify that Horizon Agent is installed on the Linux guest operating systems. See Install Horizon Agent

on a Linux Virtual Machine.

n

Verify that vCenter Server is added to Horizon Connection Server.

Procedure

1 In View Administrator, add a manual desktop pool.

Select Catalog > Desktop Pools > Add .

2 Select Manual Desktop Pool.

3 On the User assignment page, select either dedicated or floating user assignments for the machines

in the desktop pool and click Next.

4 On the Machine Source page, select vCenter virtual machinesand click Next.

5 On the vCenter Server page, select the appropriate vCenter server and click Next.

6 Enter the desktop pool id.

7 On the Desktop Pool Settings page, set the following options.

Option Description

Default display protocol VMware Blast

Allow users to choose protocol No

3D Renderer Manage using vSphere Client for 2D, vSGA, or vDGA desktop and NVIDIA GRID

vGPU for vGPU desktop

Note The pool settings are mandatory. Else, you might fail to connect to the desktop and get a

protocol error or a black screen.

8 On the Add vCenter Virtual Machines page, select the linux virtual machine. Click Add and click

Next.

Note Do not create Windows and Linux virtual machines in the same desktop pool.

9 Follow the prompts to complete the procedure.

Entitle users to the machines in the desktop pool. In View Administrator, select the desktop pool,
select Entitlements > Add entitlement, and add users or groups.

The Linux virtual machines are ready to be used as remote desktops in a Horizon 7 deployment.

Manage Desktop Pool for Linux

When you create a manual desktop pool and add Linux machines to the pool, you can manage the
manual desktop pools by configuring the settings. You must add only Linux guest operating systems to
the manual desktop pool. If the pool contains both Windows and Linux guest operating systems, the pool
if treated as a Windows pool, and you will be unable to connect to the Linux desktops.

VMware, Inc. 69

Setting Up Horizon 7 for Linux Desktops

Support for Managing Operations

n

Disable or Enable desktop pool

n

Clone automated desktop pool

n

Delete desktop pool

You can either remove virtual machines from View Manager or delete virtual machines from the disk

Support for Remote Settings

Table 7‑1. Remote Settings

Remote Setting Options

Remote Machine Power Policy

Automatically logoff after disconnect

Allow users to reset/restart their machines

Allow user to initiate separate sessions
from different client devices

"Delete machine after logoff" for
Automated Desktop Pool with Full Clone
and Floating

n

Take no power action

n

Ensure machines are always powered on

n

Suspend

n

Power off

n

Immediately

n

Never

n

After n minutes

n

Yes

n

No

n

Yes

n

No

n

Yes

n

No

Support for View Administrator Operations

n

Disconnect Session

n

Logoff Session

n

Reset/Restart Desktop

n

Send Message

For dedicated desktop pool, you can add or remove user assignment for each virtual machine. For large
number of operations, you must use View PowerCLI Cmdlets.

n

Update-UserOwnership

VMware, Inc. 70

Setting Up Horizon 7 for Linux Desktops

n

Remove-UserOwnership

Note Do not change Remote Display Protocol settings. This setting must always be the same as

desktop pool creation.

Setting Option

Default display protocol VMware Blast

Allow user to choose protocol No

3D Renderer

n

Manage using vSphere Client for 2D or vSGA or vDGA

n

NVIDIA GRID vGPU

For more information, see View Administration guide.

Create an Automated Full-Clone Desktop Pool for Linux

You can create an automated full-clone desktop pool for Linux virtual machines. After you create the
automated full-clone desktop pool, you can use the Linux virtual machines as remote desktops in a
Horizon 7 deployment.

Prerequisites

n

Verify that Horizon Agent is installed on the Linux guest operating systems. See Install Horizon Agent

on a Linux Virtual Machine.

n

If you use the Winbind solution to join the Linux virtual machine to Active Directory, you must finish
configuring the Winbind solution in the virtual machine template.

n

If you use the Winbind solution, you must run the domain join command on the virtual machine.
Include the command in a shell script and specify the script path to the Horizon Agent option
RunOnceScript in /etc/vmware/viewagent-custom.conf. For more information, see Setting

Options in Configuration Files on a Linux Desktop.

n

Verify that vCenter Server is added to Horizon Connection Server.

Procedure

1 Create a guest customization specification.

See "Create a Customization Specification for Linux in the vSphere Web Client" in the vSphere Virtual
Machine Administration document. When you create the specification, make sure that you specify the

following settings correctly.

Setting Value

Target Virtual Machine OS Linux

Computer Name Use the virtual machine name.

Domain Specify the domain of the View environment.

VMware, Inc. 71

Setting Up Horizon 7 for Linux Desktops

Setting Value

Network Settings Use standard network settings.

Primary DNS Specify a valid address.

Note For more information on Guest OS Customization Support Matrix, see

http://partnerweb.vmware.com/programs/guestOS/guest-os-customization-matrix.pdf.

2 In Horizon Administrator, select Catalog > Desktop Pools > Add.

3 Select Automated Desktop Pool and click Next.

4 Select either dedicated or floating user assignments for the machines in the desktop pool and click

Next.

5 On the vCenter Server page, select Full virtual machines and select the appropriate vCenter server,

and click Next.

6 On the Desktop Pool Identification page, enter the desktop pool ID and click Next.

7 On the Desktop Pool Settings page, set the following options and click Next.

Option Description

Default display protocol VMware Blast

Allow users to choose protocol No

3D Renderer Manage using vSphere Client for 2D, vSGA, or vDGA desktop and NVIDIA GRID

vGPU for vGPU desktop

Note The pool settings are mandatory. Else, you might fail to connect to the desktop and get a

protocol error or a black screen.

8 On the Provisioning Settings page, set the Virtual Machine Naming options and click Next.

Option Description

Specify names manually Enter names manually.

Use a naming pattern For example, specify LinuxVM-{n}.

You must also specify the following desktop pool sizing options:

n

Maximum number of machines

n

Number of spare, powered-on machines

9 On the Storage Optimization page, select a storage management policy and click Next.

10 On the vCenter Settings page, you must click Browse and select the vCenter Server settings in

sequence and click Next.

You cannot skip a vCenter Server setting:

a Template

b VM folder location

c Host or cluster

VMware, Inc. 72

Setting Up Horizon 7 for Linux Desktops

d Resource pool

e Datastores

11 On the Advanced Storage Options page, select the appropriate storage options and click Next.

12 On the Guest Customization page, select your guest customization for Linux and click Next.

13 On the Ready to Complete page, review the details and select Entitle users after this wizard

finishes.

14 Click Finish.

15 To entitle users to the machines in the desktop pool, select the desktop pool and click Entitlements >

Add entitlements and add the users and groups.

16 Wait till all the Linux virtual machines in the desktop pool become available.

Create an Instant-Clone Floating Desktop Pool for Linux

You can create an instant-clone floating desktop pool for Linux virtual machines using the Add Desktop
Pool wizard. After creating an instant-clone floating desktop pool, you can use the Linux virtual machines

as remote desktops in a Horizon 7 deployment.

Prerequisites

n

Familiarize yourself with the steps for creating virtual machines in vCenter Server and installing Linux
operating systems. For more information, see Create a Virtual Machine and Install Linux.

n

Familiarize yourself with steps for AD integration using the PBISO authentication solution. For more
information, see the PowerBroker Identity Services Open (PBISO) Authentication section in

Integrating Linux with Active Directory.

n

Familiarize yourself with installation steps for Horizon 7 Agent for Linux. For more information, see

Install Horizon Agent on a Linux Virtual Machine.

n

Familiarize yourself with steps to take a snapshot of a powered off Linux VM using VMware vSphere
Web Client. See "Take a Snapshot in the VMware Host Client" in vSphere Single Host Management -
VMware Host Client.

n

Verify that vCenter Server is added to Horizon Connection Server.

Procedure

1 Create a Linux virtual machine (VM) with Ubuntu 14.04 or Ubuntu 16.04 installed.

Note This feature is supported only on Ubuntu 14.04 and 16.04 systems.

®

For more information, see Create a Virtual Machine and Install Linux.

VMware, Inc. 73

Setting Up Horizon 7 for Linux Desktops

2 Manually install Open VMware Tools (OVT) on your Ubuntu 14.04 or Ubuntu 16.04 machine using the

following command:

apt-get install open-vm-tools

See Prepare a Linux Machine for Remote Desktop Deployment for additional information.

3 Install any dependency packages that are required for the Linux distribution.

See Install Dependency Packages for Horizon Agent for more information.

4 Install Horizon Agent for Linux in the Linux VM.

sudo ./install_viewagent.sh -A yes

See Install Horizon Agent on a Linux Virtual Machine for details.

5 Integrate your Linux VM with Active Directory.

n

To use the PBISO authentication solution, perform the following steps:

a Download PBIS Open 8.5.6 or later from

https://www.beyondtrust.com/products/powerbroker-identity-services-open/

and install it on your Linux VM.

sudo ./pbis-open-8.5.6.2029.linux.x86_64.deb.sh

b Integrate your Linux VM with Active Directory using the information in PowerBroker Identity

Services Open (PBISO) Authentication section in Integrating Linux with Active Directory.

n

If you choose not to use PBISO to integrate your Linux VM with Active Directory, you must set the
OfflineJoinDomain option to none in the /etc/vmware/viewagent-custom.conf file.
Otherwise, the creation of the instant-clone floating desktop pool fails.

6 If your DHCP server does not broadcast to a DNS server, specify a DNS server for your Linux

system.

A new virtual network adapter is added when a new instant-cloned VM is created. Any setting in the
network adapter, such as the DNS server, in the VM template is lost when the new network adapter is
added to the instant-cloned VM. PBIS requires a valid DNS server and the FQDN mapping in
the /etc/hosts is not acceptable. To avoid losing the DNS Server setting when the new network
adapter is added to the cloned VM, you must specify a DNS server in your Linux system. For
example, in an Ubuntu 14.04 or 16.04 system, specify the DNS server by adding the following lines in
the /etc/resolvconf/resolv.conf.d/head file.

nameserver 10.10.10.10

search mydomain.org

VMware, Inc. 74

Setting Up Horizon 7 for Linux Desktops

7 (Optional) If you want to add an NFS mount in the /etc/fstab file of the master Linux VDI instant-

clone agent, use one of the following methods.

n

Add a 'soft' flag in /etc/fstab, such as:

10.111.222.333:/share /home/nfsmount nfs rsize=8192,wsize=8192,timeo=14,soft,intr,tcp

n

If you do not want to use the 'soft' flag in /etc/fstab, you cannot configure the /etc/fstab in
the master Linux VM image. You can write a power-off script to configure the /etc/fstab file,
then set this power-off script in the guest customization page of the instant-clone pool in Horizon
Administrator.

8 Shut down the Linux VM and create a master image by creating a snapshot of your powered off Linux

VM using VMware vSphere® Web Client.

See "Take a Snapshot in the VMware Host Client" in vSphere Single Host Management - VMware
Host Client for information.

9 In Horizon Administrator, select Catalog > Desktop Pools > Add.

10 Define the desktop pool.

a On the Type page, select the Automated Desktop Pool and click Next.

b On the User Assignment page, select Floating and click Next.

c On the vCenter Server page, select Instant clones.

11 Enter the desktop pool ID on the Desktop Pool Identification page and click Next.

12 On the Desktop Pool Settings page, accept the default settings and click Next.

13 On the Provisioning Settings page, set the following Virtual Machine Naming options and click

Next.

n

Naming Pattern - For example, specify LinuxVM-{n}

n

Max number of machines

n

Number of spare (powered on) machines

14 On the Storage Optimization page, select Use VMware Virtual SAN for the storage management

policy and click Next.

15 On the vCenter Settings page, click Browse for each vCenter Server setting, select the appropriate

value for each setting, and click Next.

16 On the Guest Customization page, specify the Domain setting, AD container, and any extra

customization scripts that must be run after the VM is cloned. Click Next.

17 On the Ready to Complete page, select the Entitle users after this wizard finishes and review the

details.

18 Click Finish.

VMware, Inc. 75

Setting Up Horizon 7 for Linux Desktops

In Horizon Administrator, you can view the desktop VMs as they are added to the pool by selecting
Catalog > Desktop Pools.

After you create the pool, do not delete the master image or remove it from the vCenter Server inventory
if the pool exists. If you remove the master image VM from the vCenter Server inventory by mistake, you
must add it back and then do a push image using the current image.

What to do next

Entitle users to access the pool. See "Add Entitlements to Desktop Pools" in Setting Up Virtual Desktops
in Horizon 7.

Broker PowerCLI Commands

The View PowerCLI cmdlets which are to perform various administration tasks on Connection Server and
Windows desktop, can also work for Linux desktop.

Create a Manual Desktop Pool

Add-ManualPool -DefaultProtocol Blast -AllowProtocolOverride $false -threedRender usevc|vgpu -Pool_id

<pool id> [more parameters]

For Linux Desktop the following options and values are mandatory.

n

DefaultProtocol Blast

n

AllowProtocolOverride $false

n

threedRender usevc|vgpu. For vGPU desktop, use -threedRender vgpu and for 2D/vSGA/vDGA
desktop -threedRender usevc .

Examples

n

Create a floating Linux Desktop pool named LinuxDesktop with a virtual machine, LinuxVM-01.

Add-ManualPool -DefaultProtocol Blast -AllowProtocolOverride $false -threedRender usevc -Pool_id

LinuxDesktop -Id (Get-DesktopVM -Name LinuxVM-01).id -Persistence NonPersistent -Vc_name

myvc.myorg.org

n

Create a dedicated Linux vGPU desktop pool named LinuxDesktop with all VMs that start with VM
name as LinuxVM-.

Get-DesktopVM | Where-Object {$_.Name.StartsWith("LinuxVM-")} | Add-ManualPool -DefaultProtocol

Blast -AllowProtocolOverride $false -Persistence Persistent -threedRender vgpu -Pool_id

LinuxDesktop

n

Create floating Linux desktop pool LinuxDesktop with the first RHEL 6 x64 VM.

Get-DesktopVM | Where-Object {$_.GuestID -eq "rhel6_64Guest"} | Select-Object -Index 0 | Add-

ManualPool -DefaultProtocol Blast -AllowProtocolOverride $false -Persistence NonPersistent -

threedRender usevc -Pool_id LinuxDesktop

VMware, Inc. 76

Setting Up Horizon 7 for Linux Desktops

Create a Full-Clone Automated Desktop Pool

Add-AutomaticPool -DefaultProtocol Blast -AllowProtocolOverride $false -threedRender usevc|vgpu `

-Pool_id <pool id> -Vc_id <vCenter id> `

-NamePrefix <VM Name Prefix>" `

-templatePath <Virtual Machine Template Path> `

-VmFolderPath <Virtual Machine Folder Path> `

-ResourcePoolPath <Resource Pool Path> `

-dataStorePaths <Datastore Path> `

-customizationSpecName <Customization Specification Name> `

[more parameters]

For Linux Desktop the following options and values are mandatory.

n

DefaultProtocol Blast

n

AllowProtocolOverride $false

n

threedRender usevc|vgpu. For vGPU desktop, use -threedRender vgpu and for 2D/vSGA desktop ­threedRender usevc.

Example

Add-AutomaticPool -DefaultProtocol Blast -AllowProtocolOverride $false -threedrender usevc`

-pool_id FullClone-Linux `

-Vc_id (Get-ViewVC -serverName myvc.myorg.org).vc_id `

-NamePrefix "FullClone-{n:fixed=3}" `

-Persistence NonPersistent –deletePolicy DeleteOnUse `

-VmFolderPath "/LinuxVDI/vm/FullClone" `

-ResourcePoolPath "/LinuxVDI/host/LinuxVDICluster/Resources" `

-templatePath "/LinuxVDI/vm/LinuxTemplate" `

-dataStorePaths "/LinuxVDI/host/LinuxVDICluster/datastore" `

-customizationSpecName "linux-spec" `

-maximumCount 100

Add or Remove Desktop Pool Entitlement

n

Entitle domain user group of domain mydomain.org to LinuxDesktop.

Add-PoolEntitlement -Pool_id LinuxDesktop -Sid (Get-User -Name "domain user" -Domain

"mydomain.org").sid

n

Remove entitlement of domain user group of mydomain.org domain from LinuxDesktop.

Remove-PoolEntitlement -Pool_id LinuxDesktop -Sid (Get-User -Name "domain user" -Domain

"mydomain.org").sid

VMware, Inc. 77

Setting Up Horizon 7 for Linux Desktops

Assign or Remove User To or From the VM in Dedicated Desktop
Pool

n

Assign myuser user to LinuxVM-01 VM which is in a dedicated desktop pool.

Update-UserOwnership -Machine_id (Get-DesktopVM -Name "LinuxVM-01").machine_id -Sid (Get-User -

Name "myuser" | Where-Object {$_.cn -eq "myuser"}).sid

n

Remove myuser user from LinuxVM-01 VM which is in a dedicated desktop pool.

Remove-UserOwnership -Machine_id (Get-DesktopVM -Name "LinuxVM-01").machine_id

Logo Desktop Connection

n

Logoff from the desktop session of myuser.

Get-RemoteSession -Username "mydomain.org\myuser" | Send-SessionLogoff

For more information on broker PowerCLI cmdlet, see Using View PowerCLI in View Integration.

VMware, Inc. 78

Bulk Deployment of Horizon 7

for Manual Desktop Pools 8

With View Administrator, you can create a pool of Windows, but not Linux, desktop machines
automatically. However, you can develop scripts that automate the deployment of a pool of Linux desktop
machines.

The sample scripts that are provided are for illustration purposes only. VMware does not accept any
responsibility for issues that might arise when you use the sample scripts.

This chapter includes the following topics:

n

Overview of Bulk Deployment of Linux Desktops

n

Overview of Bulk Upgrade of Linux Desktops

n

Create a Virtual Machine Template for Cloning Linux Desktop Machines

n

Input File for the Sample PowerCLI Scripts to Deploy Linux Desktops

n

Sample Script to Clone Linux Virtual Machines

n

Sample Script to Join Cloned Virtual Machines to AD Domain

n

Sample Script to Join Cloned Virtual Machines to AD Domain Using SSH

n

Sample Script to Upload Configuration Files to Linux Virtual Machines

n

Sample Script to Upload Configuration Files to Linux Virtual Machines Using SSH

n

Sample Script to Upgrade Horizon Agent on Linux Desktop Machines

n

Sample Script to Upgrade Horizon Agent on Linux Virtual Machines Using SSH

n

Sample Script to Perform Operations on Linux Virtual Machines

Overview of Bulk Deployment of Linux Desktops

Deploying manual desktops for Linux involve several steps. If you plan to deploy more than a few
desktops, you can automate some of the steps by using PowerCLI scripts.

For some operations, you can choose to have either PowerCLI or SSH execute the commands on the
Linux machine. The following table describes the differences between the two approaches.

VMware, Inc.

79

Setting Up Horizon 7 for Linux Desktops

PowerCLI SSH

No need to install additional tools.

Uploading files and command execution are
slower.

Need to supply the ESXi host's administrator
credentials.

Cannot handle special characters in the
administrator's password when running the
script to install Horizon Agent or the AD user's
password when running the script to join the
domain.

n

For Ubuntu, you need to install the SSH server with the command sudo apt­get install openssh-server. For RHEL and CentOS, openssh-server is

installed by default but you need to ensure that the firewall settings allow ssh.

n

Need to download the SSH client applications pscp.exe and plink.exe and
put them in the same folder as the PowerCLI scripts.

Uploading files and command execution are faster.

No need to supply the ESXi host's administrator credentials.

Can handle special characters in the administrator's password when running the
script to install Horizon Agent or the AD user's password when running the script
to join the domain.

Note Both PowerCLI-based and SSH-based scripts can handle special characters in the passwords for

the vCenter Server administrator and the Linux administrator. PowerCLI-based scripts can also handle
special characters in the ESXi host administrator's password. In all these cases, an escape character is
not necessary.

For more information about vSphere PowerCLI, see

https://www.vmware.com/support/developer/PowerCLI.

The process of bulk deploying a pool of Linux desktops involves the following steps:

1 Create a virtual machine template and install Horizon Agent on the virtual machine.

See Create a Virtual Machine Template for Cloning Linux Desktop Machines.

2 Create a guest customization specification.

See "Create a Customization Specification for Linux in the vSphere Web Client" in the vSphere Virtual
Machine Administration document. When you create the specification, make sure that you specify the
following settings correctly.

Setting Value

Target Virtual Machine OS Linux

Computer Name Use the virtual machine name.

Domain Specify the domain of the View environment.

Network Settings Use standard network settings.

Primary DNS Specify a valid address.

Note For more information on Guest OS Customization Support Matrix, see

http://partnerweb.vmware.com/programs/guestOS/guest-os-customization-matrix.pdf.

VMware, Inc. 80

Setting Up Horizon 7 for Linux Desktops

3 Clone virtual machines.

See Sample Script to Clone Linux Virtual Machines.

4 Join the cloned VMs to the Active Directory (AD) domain if you are using the winbind solution. You

can run the domain join command with example scripts below or use option RunOnceScript
in /etc/vmware/viewagent-custom.conf, configured in the template virtual machine.

See Sample Script to Join Cloned Virtual Machines to AD Domain or Sample Script to Join Cloned

Virtual Machines to AD Domain Using SSH.

5 Update configuration options in virtual machines.

See Sample Script to Upload Configuration Files to Linux Virtual Machines or Sample Script to

Upload Configuration Files to Linux Virtual Machines Using SSH.

6 Create a desktop pool.

See Create a Manual Desktop Pool for Linux.

For a sample script that performs operations such as powering on, shutting down, restarting, or deleting
virtual machines, see Sample Script to Perform Operations on Linux Virtual Machines. This script can
delete virtual machines from vCenter Server.

Overview of Bulk Upgrade of Linux Desktops

Bulk upgrade of manual desktops for Linux involve several steps. You can automate some of the steps by
using PowerCLI scripts.

Bulk Upgrade Unmanaged Desktop

To bulk upgrade the unmanaged virtual machine to managed or unmanaged virtual machine, you must
use the sample upgrade script to upload the new Horizon Agent to the existing virtual machines and run
upgrade command.

n

If you retain the unmanaged virtual machine, your existing desktop pool can be reused.

n

If you upgrade from unmanaged virtual machine to managed virtual machine, you must delete the
existing desktop pool and create a new desktop pool. For more information, see Upgrade Horizon

Agent on a Linux Virtual Machine.

Bulk Upgrade Managed Desktop

To bulk upgrade the managed virtual machine, select one of the following methods.

VMware, Inc. 81

Setting Up Horizon 7 for Linux Desktops

Method Description

In the template virtual machine, install
or upgrade the new Horizon Agent and
create a snapshot.

Use the sample script of upgrade to
upload the new Horizon Agent to
existing virtual machines and run the
upgrade command.

n

The user data and profile are lost since the existing virtual machines are deleted,
unless the user data and profile are located on the share server such as NFS server.

n

After the virtual machine replacement, the state of the virtual machine on View
Administrator might be missing. You must restart the broker service to fix it.

n

If you are using linked clone, this method avoids duplicate data on each virtual
machine.

n

User data and profile is retained.

n

If you are using linked clone, this method introduces duplicate data on each virtual
machine.

Create a Virtual Machine Template for Cloning Linux Desktop Machines

Before you perform virtual machine cloning, you must create a virtual machine template that the clones
are based on.

Prerequisites

n

Verify that your deployment meets the requirements for supporting Linux desktops. See System

Requirements for Horizon 7 for Linux.

n

Familiarize yourself with the steps for creating virtual machines in vCenter Server and installing guest
operating systems. See "Creating and Preparing Virtual Machines" in the Setting Up Virtual Desktops
in Horizon 7 document.

n

Familiarize yourself with the recommended video memory (vRAM) values for the monitors you will
use with the virtual machine. See System Requirements for Horizon 7 for Linux.

n

Familiarize yourself with the steps for AD integration. See Chapter 3 Setting Up Active Directory

Integration for Linux Desktops.

n

Familiarize yourself with the steps to install Horizon Agent on Linux. See Chapter 5 Installing Horizon

Agent.

n

If required, familiarize yourself with the steps to configure options using the View configuration files.
See Chapter 6 Configuration Options for Linux Desktops.

n

If you plan to set up graphics, familiarize yourself with the steps. See Chapter 4 Setting Up Graphics

for Linux Desktops.

Procedure

1 In vSphere Web Client or vSphere Client, create a new virtual machine.

VMware, Inc. 82

Setting Up Horizon 7 for Linux Desktops

2 Configure custom configuration options.

a Right-click the virtual machine and click Edit Settings.

b Specify the number of vCPUs and the vMemory size.

For recommended values, follow the guidelines in the installation guide for your Linux distribution.

For example, Ubuntu 12.04 recommends configuring 2048 MB for vMemory and 2 vCPUs.

c Select Video card and specify the number of displays and the total video memory (vRAM).

Set the vRAM size in vSphere Web Client for virtual machines that use 2D or vSGA, which use
the VMware driver. The vRAM size has no affect on vDGA or NVIDIA GRID vGPU machines,
which use NVIDIA drivers.

For recommended values, follow the guidelines in System Requirements for Horizon 7 for Linux.
Do not use the Video Memory Calculator.

3 Power on the virtual machine and install the Linux distribution.

4 Create a user with root privileges, for example, ViewUser. This user is used to install and uninstall

Horizon Agent only.

5 Edit /etc/sudoers and add the line ViewUser ALL=(ALL) NOPASSWD:ALL.

With this line in /etc/sudoers, no password is required to run sudo as ViewUser. When you run the
sample script to install Horizon Agent that is provided in this chapter, you specify ViewUser as an
input.

6 If the Linux distribution is RHEL, CentOS, or NeoKylin, edit /etc/sudoers and comment out the

following lines:

Defaults requiretty

Defaults !visiblepw

7 If the Linux distribution is not RHEL 7, CentOS 7, SLED 12, or SLES 12, install VMware Tools .

RHEL 7, CentOS 7, SLED 12, and SLES 12 have Open VM Tools installed by default.

8 If the Linux distribution is RHEL 7, CentOS 7, or SLES 12, install the deployPkg plug-in.

The instructions are at http://kb.vmware.com/kb/2075048.

9 For RHEL and CentOS, enable the Network Connection setting Connect automatically.

10 Perform the AD integration tasks.

11 Perform the steps to set up graphics.

12 Install Horizon agent.

sudo ./install_viewagent.sh -A yes

See Chapter 5 Installing Horizon Agent.

13 Perform additional configurations using the View configuration files.

VMware, Inc. 83

Setting Up Horizon 7 for Linux Desktops

14 Shut down the virtual machine and create a snapshot.

Input File for the Sample PowerCLI Scripts to Deploy Linux Desktops

The sample PowerCLI scripts to deploy Linux desktops read one input file that contains information about
the desktop machines.

The input file is of type csv and contains the following information:

n

Desktop virtual machine name

n

Parent virtual machine name

n

Guest customization specification

n

Datastore where the cloned desktop machine resides

n

ESXi server that hosts the desktop machine

n

Parent virtual machine's snapshot that is used for cloning

n

Flag that indicates whether to delete the desktop virtual machine if it exists

The following example shows what the input file may contain.

VMName,Parentvm,CustomSpec,Datastore,Host,FromSnapshot,DeleteIfPresent

linux-001,Ubuntu1204x64,linuxagent,datastore1,10.117.44.172,snapshot1,TRUE

linux-002,Ubuntu1204x64,linuxagent,datastore1,10.117.44.172,snapshot1,TRUE

linux-003,Ubuntu1204x64,linuxagent,datastore1,10.117.44.172,snapshot1,TRUE

linux-004,Ubuntu1204x64,linuxagent,datastore1,10.117.44.172,snapshot1,TRUE

linux-005,Ubuntu1204x64,linuxagent,datastore1,10.117.44.172,snapshot1,TRUE

The sample scripts assume that the name of this input file is CloneVMs.csv and that the file is located in
the same folder as the scripts.

Sample Script to Clone Linux Virtual Machines

You can customize and use the following sample script to clone any number of virtual machines (VMs).

To copy and paste the script content without page breaks, use the HTML version of this topic, available
from the Horizon 7 documentation page at https://www.vmware.com/support/pubs/view_pubs.html.

Script Input

This script reads one input file, which is described in Input File for the Sample PowerCLI Scripts to Deploy

Linux Desktops. This script also interactively asks for the following information:

n

IP address of the vCenter Server

n

Administrator login name for the vCenter Server

n

Administrator password for the vCenter Server

VMware, Inc. 84

Setting Up Horizon 7 for Linux Desktops

n

Clone type, which can be linked or full

n

Whether to disable vSphere VM console

Script Content

<#

Create Clones from a Master VM

The Tool supports creation of Full clone and linked clone from Master VM.

The parent VM is required for the linked-clone to work and the parent VMs file cannot be renamed or

moved.

#>

#------------------------- Functions -------------------------

function GetInput

{

Param($prompt, $IsPassword = $false)

$prompt = $prompt + ": "

Write-Host $prompt -NoNewLine

[Console]::ForegroundColor = "Blue"

if ($IsPassword)

{

$input = Read-Host -AsSecureString

$input =

[Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBST

R($input))

}

else

{

$input = Read-Host

}

[Console]::ResetColor()

return $input

}

function IsVMExists ()

{

Param($VMExists)

Write-Host "Checking if the VM $VMExists already Exists"

[bool]$Exists = $false

#Get all VMS and check if the VMs is already present in VC

$listvm = Get-vm

foreach ($lvm in $listvm)

{

if($VMExists -eq $lvm.Name )

{

$Exists = $true

}

}

return $Exists

}

function Disable_VM_Console()

VMware, Inc. 85

Setting Up Horizon 7 for Linux Desktops

{

Param($VMToDisableConsole)

$vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec

$extra = New-Object VMware.Vim.optionvalue

$extra.Key="RemoteDisplay.maxConnections"

$extra.Value="0"

$vmConfigSpec.extraconfig += $extra

$vm = Get-VM $VMToDisableConsole | Get-View

$vm.ReconfigVM($vmConfigSpec)

}

function Delete_VM()

{

Param($VMToDelete)

Write-Host "Deleting VM $VMToDelete"

Get-VM $VMToDelete | where { $_.PowerState –eq "PoweredOn" } | Stop-VM –confirm:$false

Get-VM $VMToDelete | Remove-VM –DeleteFromDisk –confirm:$false

}

#------------------------- Main Script -------------------------

$vcAddress = GetInput -prompt "Your vCenter address" -IsPassword $false

$vcAdmin = GetInput -prompt "Your vCenter admin user name" -IsPassword $false

$vcPassword = GetInput -prompt "Your vCenter admin user password" -IsPassword $true

$cloneType = GetInput -prompt 'Clone Type ("linked" or "full")' -IsPassword $false

$disableVMConsole = GetInput -prompt 'Disable vSphere VM Console ("yes" or "no", recommend "yes")' -

IsPassword $false

"-----------------------------------------------------"

$csvFile = '.\CloneVMs.csv'

# Check that user passed only linked or full clone

if (($CloneType.length >0) -and ($CloneType -ne "linked" -or $CloneType -ne "full"))

{

write-host -ForeGroundColor Red "Clone type supports only 'linked' or 'full' (case sensitive)"

exit

}

if (($disableVMConsole.length >0) -and ($disableVMConsole -ne "yes" -or $disableVMConsole -ne "no"))

{

write-host -ForeGroundColor Red "Disable vSphere VM Console supports only 'yes' or 'no' (case

sensitive)"

exit

}

#check if file exists

if (!(Test-Path $csvFile))

{

write-host -ForeGroundColor Red "CSV File $CSVFile not found"

exit

}

# Connect to the VC (Parameterize VC)

#Connect to vCenter

$VC_Conn_State = Connect-VIServer $vcAddress -user $vcAdmin -password $vcPassword

if([string]::IsNullOrEmpty($VC_Conn_State))

VMware, Inc. 86

Setting Up Horizon 7 for Linux Desktops

{

Write-Host 'Exit since failed to login vCenter'

exit

}

else

{

Write-Host 'vCenter is connected'

}

#Read input CSV file

$csvData = Import-CSV $csvFile

#$csvData = Import-CSV $csvFile -

header("VMName","Parentvm","CustomSpec","Datastore","Host","FromSnapshot","DeleteIfPresent")

foreach ($line in $csvData)

{

"`n-----------------------------------------------------"

$VMName = $line.VMName

write-host -ForeGroundColor Yellow "VM: $VMName`n"

$destVMName=$line.VMName

$srcVM = $line.Parentvm

$cSpec = $line.CustomSpec

$targetDSName = $line.Datastore

$destHost = $line.Host

$srcSnapshot = $line.FromSnapshot

$deleteExisting = $line.DeleteIfPresent

if (IsVMExists ($destVMName))

{

Write-Host "VM $destVMName Already Exists in VC $vcAddress"

if($deleteExisting -eq "TRUE")

{

Delete_VM ($destVMName)

}

else

{

Write-Host "Skip clone for $destVMName"

continue

}

}

$vm = get-vm $srcvm -ErrorAction Stop | get-view -ErrorAction Stop

$cloneSpec = new-object VMware.VIM.VirtualMachineCloneSpec

$cloneSpec.Location = new-object VMware.VIM.VirtualMachineRelocateSpec

if ($CloneType -eq "linked")

{

$cloneSpec.Location.DiskMoveType =

[VMware.VIM.VirtualMachineRelocateDiskMoveOptions]::createNewChildDiskBacking

}

Write-Host "Using Datastore $targetDSName"

$newDS = Get-Datastore $targetDSName | Get-View

$CloneSpec.Location.Datastore = $newDS.summary.Datastore

Set-VM -vm $srcVM -snapshot (Get-Snapshot -vm $srcVM -Name $srcSnapshot) -confirm:$false

$cloneSpec.Snapshot = $vm.Snapshot.CurrentSnapshot

$cloneSpec.Location.Host = (get-vmhost -Name $destHost).Extensiondata.MoRef

$CloneSpec.Location.Pool = (Get-ResourcePool -Name Resources -Location (Get-VMHost -Name

$destHost)).Extensiondata.MoRef

VMware, Inc. 87

Setting Up Horizon 7 for Linux Desktops

# Start the Clone task using the above parameters

$task = $vm.CloneVM_Task($vm.parent, $destVMName, $cloneSpec)

# Get the task object

$task = Get-Task | where { $_.id -eq $task }

#Wait for the taks to Complete

Wait-Task -Task $task

$newvm = Get-vm $destVMName

$customSpec = Get-OSCustomizationSpec $cSpec

Set-vm -OSCustomizationSpec $cSpec -vm $newvm -confirm:$false

if ($disableVMConsole -eq "yes")

{

Disable_VM_Console($destVMName)

}

# Start the VM

Start-VM $newvm

}

Disconnect-VIServer $vcAddress -Confirm:$false

exit

Script Execution

The following messages are from an execution of the script:

PowerCLI C:\scripts> .\CloneVMs.ps1

Your vCenter address: 10.117.44.17

Your vCenter admin user name: administrator

Your vCenter admin user password: *******

Clone Type<"linked" or "Full"> : linked

Disable vSphere VM Console ("yes" or "no", recommend "yes") : yes

The time that the cloning process takes depends on the number of desktop machines and can range from
several minutes to a number of hours. To verify that the process is complete, from vSphere client, make
sure that the last desktop virtual machine is powered on, has its own unique host name, and VMware
Tools is running.

Sample Script to Join Cloned Virtual Machines to AD Domain

You can customize and use the following sample script to join cloned virtual machines (VMs) to an Active
Directory (AD) domain.

You need to run this script if you use the Winbind solution for AD integration because the step to join the
domain will fail for the cloned VMs. This script runs a command to join the domain on each VM. You do
not need to run this script if you use the OpenLDAP solution.

To copy and paste the script content without page breaks, use the HTML version of this topic, available
from the Horizon 7 documentation page at https://www.vmware.com/support/pubs/view_pubs.html.

VMware, Inc. 88

Setting Up Horizon 7 for Linux Desktops

Script Input

This script reads one input file, which is described in Input File for the Sample PowerCLI Scripts to Deploy

Linux Desktops. This script also interactively asks for the following information:

n

IP address of the vCenter Server

n

Administrator login name for the vCenter Server

n

Administrator password for the vCenter Server

n

Administrator login name for the ESXi host

n

Administrator password for the ESXi host

n

User login name for the Linux VM

n

User password for the Linux VM

n

Login name of an AD user that is authorized to join machines to the domain

n

Password of the authorized AD user

Script Content

<#

.SYNOPSIS

run command "sudo /usr/bin/net ads join"

.DESCRIPTION

The tool is to run the command "sudo /usr/bin/net ads join" to join Linux to AD

.NOTES

#>

#------------------------- Functions -------------------------

function GetInput

{

Param($prompt, $IsPassword = $false)

$prompt = $prompt + ": "

Write-Host $prompt -NoNewLine

[Console]::ForegroundColor = "Blue"

if ($IsPassword)

{

$input = Read-Host -AsSecureString

$input =

[Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBST

R($input))

}

else

{

$input = Read-Host

}

[Console]::ResetColor()

VMware, Inc. 89

Setting Up Horizon 7 for Linux Desktops

return $input

}

#------------------------- Handle input -------------------------

"-----------------------------------------------------"

$vcAddress = GetInput -prompt "Your vCenter address" -IsPassword $false

$vcAdmin = GetInput -prompt "Your vCenter admin user name" -IsPassword $false

$vcPassword = GetInput -prompt "Your vCenter admin user password" -IsPassword $true

"-----------------------------------------------------"

$hostAdmin = GetInput -prompt 'Your ESXi host admin user name, such as root' -IsPassword $false

$hostPassword = GetInput -prompt "Your ESXi admin user password" -IsPassword $true

"-----------------------------------------------------"

$guestUser = GetInput -prompt 'Your VM guest OS user name' -IsPassword $false

$guestPassword = GetInput -prompt 'Your VM guest OS user password' -IsPassword $true

"-----------------------------------------------------"

$adUser = GetInput -prompt 'Type the AD user name to join the AD' -IsPassword $false

""

"`nPlease type the AD user password."

"Plase note that special character in password may not work with the script"

$adUserPassword = GetInput -prompt 'Your AD user password' -IsPassword $true

"-----------------------------------------------------"

#$csvFile = Read-Host 'Csv File '

$csvFile = '.\CloneVMs.csv'

#------------------------- Main Script -------------------------

#Connect to vCenter

#Connect to vCenter

$VC_Conn_State = Connect-VIServer $vcAddress -user $vcAdmin -password $vcPassword

if([string]::IsNullOrEmpty($VC_Conn_State))

{

Write-Host 'Exit since failed to login vCenter'

exit

}

else

{

Write-Host 'vCenter is connected'

}

#Read input CSV file

$csvData = Import-CSV $csvFile

$destFolder = "/home/$guestUser/"

#Handle VMs one by one

foreach ($line in $csvData)

{

"`n-----------------------------------------------------"

$VMName = $line.VMName

write-host -ForeGroundColor Yellow "VM: $VMName`n"

$cmd = "sudo /usr/bin/net ads join -U $adUser%$adUserPassword"

Write-Host "Run cmd 'sudo /usr/bin/net ads join' in VM '$VMName' with user '$guestUser'"

Invoke-VMScript -HostUser $hostAdmin -HostPassword $hostPassword -VM $VMName -GuestUser

$guestUser -GuestPassword $guestPassword -Confirm:$false -ScriptType Bash -ScriptText $cmd

VMware, Inc. 90

Setting Up Horizon 7 for Linux Desktops

}

Disconnect-VIServer $vcAddress -Confirm:$false

exit

Script Execution

The following messages are from an execution of the script:

PowerCLI C:\scripts> .\ClonedVMs_JoinDomain.ps1

--------------------------------------------------

Your vCenter address: 10.117.44.17

Your vCenter admin user name: administrator

Your vCenter admin user password: *******

--------------------------------------------------

Your ESXi host admin user name, such as root: root

Your ESXi host admin user password: *******

--------------------------------------------------

Your VM guest OS user name: ViewUser

Your VM guest OS user password: *******

--------------------------------------------------

Type the AD user name to join the AD: viewadmin

Please type the AD user password.

Please note that special character in password may not work with the script.

Your AD user password: *******

Sample Script to Join Cloned Virtual Machines to AD Domain Using SSH

You can customize and use the following sample script to join cloned virtual machines (VMs) to an Active
Directory (AD) domain. This script uses SSH to run commands on the Linux VMs.

You need to run this script if you use the Winbind solution for AD integration because the step to join the
domain will fail for the cloned VMs. This script runs a command to join the domain on each VM. You do
not need to run this script if you use the OpenLDAP solution.

To copy and paste the script content without page breaks, use the HTML version of this topic, available
from the Horizon 7 documentation page at https://www.vmware.com/support/pubs/view_pubs.html.

Script Input

This script reads one input file, which is described in Input File for the Sample PowerCLI Scripts to Deploy

Linux Desktops. This script also interactively asks for the following information:

n

IP address of the vCenter Server

n

Administrator login name for the vCenter Server

n

Administrator password for the vCenter Server

n

User login name for the Linux VM

VMware, Inc. 91

Setting Up Horizon 7 for Linux Desktops

n

User password for the Linux VM

n

Login name of an AD user that is authorized to join machines to the domain

n

Password of the authorized AD user

Script Content

<#

.SYNOPSIS

run command "sudo /usr/bin/net ads join" via SSH

.DESCRIPTION

The tool is to run the command "sudo /usr/bin/net ads join" to join Linux machine to AD via SSH

.NOTES

#>

#------------------------- Functions -------------------------

function GetInput

{

Param($prompt, $IsPassword = $false)

$prompt = $prompt + ": "

Write-Host $prompt -NoNewLine

[Console]::ForegroundColor = "Blue"

if ($IsPassword)

{

$input = Read-Host -AsSecureString

$input =

[Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBST

R($input))

}

else

{

$input = Read-Host

}

[Console]::ResetColor()

return $input

}

function Check_SSH_Client

{

Param($IsPlink, $IsPSCP)

if ($IsPlink)

{

if (Test-Path ".\plink.exe")

{

write-host -ForeGroundColor Yellow 'SSH client "plink.exe" found'

}

else

{

write-host -ForeGroundColor Red 'SSH client "plink.exe" not found, please download from its

official web site'

exit

VMware, Inc. 92

Setting Up Horizon 7 for Linux Desktops

}

}

if ($IsPSCP)

{

if (Test-Path ".\pscp.exe")

{

write-host -ForeGroundColor Yellow 'SSH client "pscp.exe" found'

}

else

{

write-host -ForeGroundColor Red 'SSH client "pscp.exe" not found, please download from its

official web site'

exit

}

}

}

function RunCmdViaSSH

{

Param($VM_Name, $User, $Password, $Cmd, $returnOutput = $false)

$VM= Get-VM $VM_Name

$IP = $VM.guest.IPAddress[0]

write-host "Run cmd on $VM_Name ($IP)"

if($returnOutput)

{

$command = "echo yes | .\plink.exe -ssh -l $user -pw $password $IP " + '"' + $cmd +'"'

$output = Invoke-Expression $command

return $output

}

else

{

echo yes | .\plink.exe -ssh -l $user -pw $password $IP "$cmd"

}

}

function UploadFileViaSSH

{

Param($VM_Name, $User, $Password, $LocalPath, $DestPath)

$VM= Get-VM $VM_Name

$IP = $VM.guest.IPAddress[0]

$command = "echo yes | .\pscp.exe -l $User -pw $Password $LocalPath $IP" + ":" + "$DestPath"

write-host "Upload file: $command"

Invoke-Expression $command

}

#------------------------- Handle input -------------------------

"-----------------------------------------------------"

Check_SSH_Client -IsPlink $true -IsPSCP $false

"-----------------------------------------------------"

$vcAddress = GetInput -prompt "Your vCenter address" -IsPassword $false

$vcAdmin = GetInput -prompt "Your vCenter admin user name" -IsPassword $false

$vcPassword = GetInput -prompt "Your vCenter admin user password" -IsPassword $true

VMware, Inc. 93

Setting Up Horizon 7 for Linux Desktops

"-----------------------------------------------------"

$guestUser = GetInput -prompt 'Your VM guest OS user name' -IsPassword $false

$guestPassword = GetInput -prompt 'Your VM guest OS user password' -IsPassword $true

"-----------------------------------------------------"

$adUser = GetInput -prompt 'Type the AD user name to join the AD' -IsPassword $false

""

"`nPlease type the AD user password."

[Console]::ForegroundColor = "Yellow"

"Plase note that special character should be escaped. For example, $ should be \$"

[Console]::ResetColor()

$adUserPassword = GetInput -prompt 'Your AD user password' -IsPassword $true

"-----------------------------------------------------"

#$csvFile = Read-Host 'Csv File '

$csvFile = '.\CloneVMs.csv'

#------------------------- Main Script -------------------------

#Connect to vCenter

$VC_Conn_State = Connect-VIServer $vcAddress -user $vcAdmin -password $vcPassword

if([string]::IsNullOrEmpty($VC_Conn_State))

{

Write-Host 'Exit since failed to login vCenter'

exit

}

else

{

Write-Host 'vCenter is connected'

}

#Read input CSV file

$csvData = Import-CSV $csvFile

$destFolder = "/home/$guestUser/"

#Handle VMs one by one

foreach ($line in $csvData)

{

"-----------------------------------------------------"

$VMName = $line.VMName

write-host -ForeGroundColor Yellow "VM: $VMName`n"

$cmd = "sudo /usr/bin/net ads join -U $adUser%$adUserPassword"

Write-Host "Run cmd 'sudo /usr/bin/net ads join' in VM '$VMName' with user '$guestUser'"

RunCmdViaSSH -VM_Name $VMName -User $guestUser -Password $guestPassword -Cmd $cmd

}

Disconnect-VIServer $vcAddress -Confirm:$false

exit

VMware, Inc. 94

Setting Up Horizon 7 for Linux Desktops

Script Execution

The following messages are from an execution of the script:

PowerCLI C:\scripts> .\ClonedVMs_JoinDomain_SSH.ps1

--------------------------------------------------

Your vCenter address: 10.117.44.17

Your vCenter admin user name: administrator

Your vCenter admin user password: *******

--------------------------------------------------

Your VM guest OS user name: ViewUser

Your VM guest OS user password: *******

--------------------------------------------------

Type the AD user name to join the AD: viewadmin

Please type the AD user password.

Please note that special character should be escaped. For example, $ should be \$

Your AD user password: *******

Sample Script to Upload Configuration Files to Linux
Virtual Machines

You can customize and use the following sample script to upload the configuration files config and
viewagent-custom.conf to multiple Linux virtual machines (VMs).

To copy and paste the script content without page breaks, use the HTML version of this topic, available
from the Horizon 7 documentation page at https://www.vmware.com/support/pubs/view_pubs.html.

Script Input

This script reads one input file, which is described in Input File for the Sample PowerCLI Scripts to Deploy

Linux Desktops. This script also interactively asks for the following information:

n

IP address of the vCenter Server

n

Administrator login name for the vCenter Server

n

Administrator password for the vCenter Server

n

Administrator login name for the ESXi host

n

Administrator password for the ESXi host

n

User login name for the Linux VM

n

User password for the Linux VM

VMware, Inc. 95

Setting Up Horizon 7 for Linux Desktops

Script Content

<#

Upload the configuration files config and viewagent-custom.conf to Linux VMs

#>

#------------------------- Functions -------------------------

function GetInput

{

Param($prompt, $IsPassword = $false)

$prompt = $prompt + ": "

Write-Host $prompt -NoNewLine

[Console]::ForegroundColor = "Blue"

if ($IsPassword)

{

$input = Read-Host -AsSecureString

$input =

[Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBST

R($input))

}

else

{

$input = Read-Host

}

[Console]::ResetColor()

return $input

}

#------------------------- Handle Input -------------------------

"-----------------------------------------------------"

write-host -ForeGroundColor Blue 'Please ensure your config file and viewagent-custom.conf file are

in current working directory'

$vcAddress = GetInput -prompt "Your vCenter address" -IsPassword $false

$vcAdmin = GetInput -prompt "Your vCenter admin user name" -IsPassword $false

$vcPassword = GetInput -prompt "Your vCenter admin user password" -IsPassword $true

"-----------------------------------------------------"

$hostAdmin = GetInput -prompt 'Your ESXi host admin user name, such as root' -IsPassword $false

$hostPassword = GetInput -prompt "Your ESXi admin user password" -IsPassword $true

"-----------------------------------------------------"

$guestUser = GetInput -prompt 'Your VM guest OS user name' -IsPassword $false

$guestPassword = GetInput -prompt 'Your VM guest OS user password' -IsPassword $true

"-----------------------------------------------------"

$csvFile = '.\CloneVMs.csv'

$setConfig = $false

$setCustomConf = $false

$config_File = "config"

$customConf_File = "viewagent-custom.conf"

#check if config file exists

if(Test-Path $config_File)

{

$setConfig = $true

VMware, Inc. 96

Setting Up Horizon 7 for Linux Desktops

write-host -ForeGroundColor Yellow '"config" file found'

}

else

{

write-host -ForeGroundColor Yellow '"config" file not found, skip it'

}

if(Test-Path $customConf_File)

{

$setCustomConf = $true

write-host -ForeGroundColor Yellow '"viewagent-custom.conf" file found'

}

else

{

write-host -ForeGroundColor Yellow '"viewagent-custom.conf" file not found, skip it'

}

if (($setConfig -eq $false)-AND ($setCustomConf -eq $false))

{

write-host -ForeGroundColor Red 'Both file not found, exit'

exit

}

#Connect to vCenter

$VC_Conn_State = Connect-VIServer $vcAddress -user $vcAdmin -password $vcPassword

if([string]::IsNullOrEmpty($VC_Conn_State))

{

Write-Host 'Exit since failed to login vCenter'

exit

}

else

{

Write-Host 'vCenter is connected'

}

#Read input CSV file

$csvData = Import-CSV $csvFile

$destFolder = "/home/$guestUser/"

#Handle VMs one by one

foreach ($line in $csvData)

{

"`n-----------------------------------------------------"

$VMName = $line.VMName

write-host -ForeGroundColor Yellow "VM: $VMName`n"

#Try to delete the configuration file from home folder on destination VM

$cmd = "rm -rf config viewagent-custom.conf"

Write-Host "Run cmd '$cmd' in VM '$VMName' with user '$guestUser'"

Invoke-VMScript -HostUser $hostAdmin -HostPassword $hostPassword -VM $VMName -GuestUser

$guestUser -GuestPassword $guestPassword -Confirm:$false -ScriptType Bash -ScriptText $cmd

if ($setConfig)

VMware, Inc. 97

Setting Up Horizon 7 for Linux Desktops

{

Write-Host "Upload File '$config_File' to '$destFolder' of VM '$VMName' with user '$guestUser'"

Copy-VMGuestFile -HostUser $hostAdmin -HostPassword $hostPassword -VM $VMName -GuestUser

$guestUser -GuestPassword $guestPassword -Confirm:$false -LocalToGuest -Destination $destFolder -

Source $config_File

$cmd = "sudo mv ./$config_File /etc/vmware/";

Write-Host "Move configuraton file: $cmd"

Invoke-VMScript -HostUser $hostAdmin -HostPassword $hostPassword -VM $VMName -GuestUser

$guestUser -GuestPassword $guestPassword -Confirm:$false -ScriptType Bash -ScriptText $cmd

}

if ($setCustomConf)

{

Write-Host "Upload File '$customConf_File' to '$destFolder' of VM '$VMName' with user '$guestUser'"

Copy-VMGuestFile -HostUser $hostAdmin -HostPassword $hostPassword -VM $VMName -GuestUser

$guestUser -GuestPassword $guestPassword -Confirm:$false -LocalToGuest -Destination $destFolder -

Source $customConf_File

$cmd = "sudo mv ./$customConf_File /etc/vmware/";

Write-Host "Move configuraton file: $cmd"

Invoke-VMScript -HostUser $hostAdmin -HostPassword $hostPassword -VM $VMName -GuestUser

$guestUser -GuestPassword $guestPassword -Confirm:$false -ScriptType Bash -ScriptText $cmd

}

}

Disconnect-VIServer $vcAddress -Confirm:$false

exit

Script Execution

The following messages are from an execution of the script:

PowerCLI C:\scripts> .\UpdateOptionFile.ps1

--------------------------------------------------

Please ensure your config file and view-agent.conf file are in current working directory.

Your vCenter address: 10.117.44.17

Your vCenter admin user name: administrator

Your vCenter admin user password: *******

--------------------------------------------------

Your ESXi host admin user name, such as root: root

Your ESXi host admin user password: *******

--------------------------------------------------

Your VM guest OS user name: ViewUser

Your VM guest OS user password: *******

Sample Script to Upload Configuration Files to Linux
Virtual Machines Using SSH

You can customize and use the following sample script to upload the configuration files config and
viewagent-custom.conf to multiple Linux virtual machines (VMs). This script uses SSH to run

commands on the Linux VMs.

VMware, Inc. 98

Setting Up Horizon 7 for Linux Desktops

To copy and paste the script content without page breaks, use the HTML version of this topic, available
from the Horizon 7 documentation page at https://www.vmware.com/support/pubs/view_pubs.html.

Script Input

This script reads one input file, which is described in Input File for the Sample PowerCLI Scripts to Deploy

Linux Desktops. This script also interactively asks for the following information:

n

IP address of the vCenter Server

n

Administrator login name for the vCenter Server

n

Administrator password for the vCenter Server

n

User login name for the Linux VM

n

User password for the Linux VM

Script Content

<#

Upload the configuration files config and viewagent-custom.conf to Linux VMs using SSH

#>

#------------------------- Functions -------------------------

function GetInput

{

Param($prompt, $IsPassword = $false)

$prompt = $prompt + ": "

Write-Host $prompt -NoNewLine

[Console]::ForegroundColor = "Blue"

if ($IsPassword)

{

$input = Read-Host -AsSecureString

$input =

[Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBST

R($input))

}

else

{

$input = Read-Host

}

[Console]::ResetColor()

return $input

}

function Check_SSH_Client

{

Param($IsPlink, $IsPSCP)

if ($IsPlink)

{

if (Test-Path ".\plink.exe")

{

write-host -ForeGroundColor Yellow 'SSH client "plink.exe" found'

}

VMware, Inc. 99

Setting Up Horizon 7 for Linux Desktops

else

{

write-host -ForeGroundColor Red 'SSH client "plink.exe" not found, please download from its

official web site'

exit

}

}

if ($IsPSCP)

{

if (Test-Path ".\pscp.exe")

{

write-host -ForeGroundColor Yellow 'SSH client "pscp.exe" found'

}

else

{

write-host -ForeGroundColor Red 'SSH client "pscp.exe" not found, please download from its

official web site'

exit

}

}

}

function RunCmdViaSSH

{

Param($VM_Name, $User, $Password, $Cmd, $returnOutput = $false)

$VM= Get-VM $VM_Name

$IP = $VM.guest.IPAddress[0]

write-host "Run cmd on $VM_Name ($IP)"

if($returnOutput)

{

$command = "echo yes | .\plink.exe -ssh -l $user -pw $password $IP " + '"' + $cmd +'"'

$output = Invoke-Expression $command

return $output

}

else

{

echo yes | .\plink.exe -ssh -l $user -pw $password $IP "$cmd"

}

}

function UploadFileViaSSH

{

Param($VM_Name, $User, $Password, $LocalPath, $DestPath)

$VM= Get-VM $VM_Name

$IP = $VM.guest.IPAddress[0]

$command = "echo yes | .\pscp.exe -l $User -pw $Password $LocalPath $IP" + ":" + "$DestPath"

write-host "Upload file: $command"

Invoke-Expression $command

}

#------------------------- Handle Input -------------------------

"-----------------------------------------------------"

VMware, Inc. 100