Vmware Using Horizon Client For Windows 4.3 User Guide 43 En

User Manual: vmware Horizon Client 4.3 for Windows - User Guide Free User Guide for VMware Horizon Software, Manual

Open the PDF directly: View PDF PDF.
Page Count: 104 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Using VMware Horizon Client for
Windows
Horizon Client 4.3
This document supports the version of each product listed and
supports all subsequent versions until the document is
replaced by a new edition. To check for more recent editions of
this document, see http://www.vmware.com/support/pubs.
EN-002308-00
Using VMware Horizon Client for Windows
2 VMware, Inc.
You can find the most up-to-date technical documentation on the VMware Web site at:
hp://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
docfeedback@vmware.com
Copyright © 2013–2016 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
Contents
Using VMware Horizon Client for Windows 7
1System Requirements and Setup for Windows-Based Clients 9
System Requirements for Windows Clients 10
System Requirements for Real-Time Audio-Video 11
Requirements for Scanner Redirection 12
Requirements for Serial Port Redirection 12
Requirements for Multimedia Redirection (MMR) 13
Requirements for Flash Redirection 14
Requirements for Using Flash URL Redirection 15
Requirements for URL Content Redirection 15
Requirements for Using Microsoft Lync with Horizon Client 16
Smart Card Authentication Requirements 17
Device Authentication Requirements 18
Supported Desktop Operating Systems 18
Preparing Connection Server for Horizon Client 19
Congure VMware Blast Options 19
Horizon Client Data Collected by VMware 20
2Installing Horizon Client for Windows 23
Enabling FIPS Mode in the Windows Client Operating System 23
Install Horizon Client for Windows 24
Installing Horizon Client Silently 25
Install Horizon Client Silently 25
Silent Installation Properties for Horizon Client 27
Microsoft Windows Installer Command-Line Options 28
Upgrade Horizon Client Online 30
3Conguring Horizon Client for End Users 33
Common Conguration Seings 33
Using URIs to Congure Horizon Client 34
Syntax for Creating vmware-view URIs 34
Examples of vmware-view URIs 37
Conguring Certicate Checking for End Users 39
Seing the Certicate Checking Mode for Horizon Client 40
Conguring Advanced TLS/SSL Options 41
Congure Application Reconnection Behavior 41
Using the Group Policy Template to Congure VMware Horizon Client for Windows 42
Scripting Denition Seings for Client GPOs 42
Security Seings for Client GPOs 44
RDP Seings for Client GPOs 47
VMware, Inc. 3
General Seings for Client GPOs 49
USB Seings for Client GPOs 51
View PCoIP Client Session Variables ADM Template Seings 54
Running Horizon Client from the Command Line 57
Horizon Client Command Usage 57
Horizon Client Conguration File 60
Using the Windows Registry to Congure Horizon Client 60
4Managing Remote Desktop and Application Connections 63
Connect to a Remote Desktop or Application 63
Tips for Using the Desktop and Application Selector 66
Share Access to Local Folders and Drives 66
Hide the VMware Horizon Client Window 68
Reconnecting to a Desktop or Application 69
Create a Desktop or Application Shortcut on Your Client Desktop or Start Menu 69
Switch Desktops or Applications 70
Log O or Disconnect 70
5Working in a Remote Desktop or Application 73
Feature Support Matrix for Windows Clients 73
Features Supported in Nested Mode 77
Internationalization 77
Use a Local IME with Remote Applications 77
Enabling Support for Onscreen Keyboards 78
Monitors and Screen Resolution 78
Supported Multiple Monitor Congurations 79
Select Specic Monitors in a Multiple-Monitor Setup 80
Use One Monitor in a Multiple-Monitor Setup 80
Use Display Scaling 81
Using DPI Synchronization 81
Change the Display Mode While a Desktop Window Is Open 82
Connect USB Devices 83
Congure Clients to Reconnect When USB Devices Restart 85
Using the Real-Time Audio-Video Feature for Webcams and Microphones 86
When You Can Use Your Webcam 87
Select a Preferred Webcam or Microphone on a Windows Client System 87
Copying and Pasting Text and Images 88
Conguring the Client Clipboard Memory Size 88
Using Remote Applications 89
Saving Documents in a Remote Application 89
Printing from a Remote Desktop or Application 89
Set Printing Preferences for the Virtual Printer Feature on a Remote Desktop 90
Using USB Printers 91
Control Adobe Flash Display 91
Clicking URL Links That Open Outside of Horizon Client 92
Using the Relative Mouse Feature for CAD and 3D Applications 92
Using Scanners 92
Using Serial Port Redirection 93
Using VMware Horizon Client for Windows
4 VMware, Inc.
Keyboard Shortcuts 95
6Troubleshooting Horizon Client 99
Problems with Keyboard Input 99
What to Do If Horizon Client Exits Unexpectedly 99
Reset a Remote Desktop or Application 100
Uninstalling Horizon Client 100
Index 101
Contents
VMware, Inc. 5
Using VMware Horizon Client for Windows
6 VMware, Inc.
Using VMware Horizon Client for Windows
This guide, Using VMware Horizon Client for Windows, provides information about installing and using
VMware Horizon® Client™ software on a Microsoft Windows client system to connect to a remote desktop
or application in the datacenter.
The information in this document includes system requirements and instructions for installing and using
Horizon Client for Windows.
This information is intended for administrators who need to set up a View deployment that includes
Microsoft Windows client systems, such as desktops and laptops. The information is wrien for experienced
system administrators who are familiar with virtual machine technology and datacenter operations.
VMware, Inc. 7
Using VMware Horizon Client for Windows
8 VMware, Inc.
System Requirements and Setup for
Windows-Based Clients 1
Systems running Horizon Client components must meet certain hardware and software requirements.
Horizon Client on Windows systems uses Microsoft Internet Explorer Internet seings, including proxy
seings, when connecting to View Connection Server. Ensure that your Internet Explorer seings are
accurate and that you can access the View Connection Server URL through Internet Explorer.
N
nStarting with version 7.0, View Agent is renamed Horizon Agent.
nVMware Blast, the display protocol that is available starting with Horizon Client 4.0 and Horizon Agent
7.0, is also known as VMware Blast Extreme.
This chapter includes the following topics:
n“System Requirements for Windows Clients,” on page 10
n“System Requirements for Real-Time Audio-Video,” on page 11
n“Requirements for Scanner Redirection,” on page 12
n“Requirements for Serial Port Redirection,” on page 12
n“Requirements for Multimedia Redirection (MMR),” on page 13
n“Requirements for Flash Redirection,” on page 14
n“Requirements for Using Flash URL Redirection,” on page 15
n“Requirements for URL Content Redirection,” on page 15
n“Requirements for Using Microsoft Lync with Horizon Client,” on page 16
n“Smart Card Authentication Requirements,” on page 17
n“Device Authentication Requirements,” on page 18
n“Supported Desktop Operating Systems,” on page 18
n“Preparing Connection Server for Horizon Client,” on page 19
n“Congure VMware Blast Options,” on page 19
n“Horizon Client Data Collected by VMware,” on page 20
VMware, Inc. 9
System Requirements for Windows Clients
You can install Horizon Client for Windows on PCs or laptops that use a supported Microsoft Windows
operating system.
The PC or laptop on which you install Horizon Client, and the peripherals it uses, must meet certain system
requirements.
Model All x86 or x86-64 Windows devices
Memory At least 1GB of RAM
Operating systems The following operating systems are supported:
OS Version
Service Pack or
Servicing Option Supported Editions
Windows 10 32- or 64-bit Current Branch (CB)
version 1607
Current Business Branch
(CBB) version 1607
Long-Term Servicing
Branch (LTSB) version
1607
Home, Pro,
Enterprise, and IoT
Core
Windows 8 or 8.1 32- or 64-bit None or Update 2 Pro, Enterprise, and
Industry Embedded
Windows 7 32- or 64-bit SP1 Home, Enterprise,
Professional, and
Ultimate
Windows Server
2008 R2
64-bit Latest Update Standard
Windows Server
2012 R2
64-bit Latest Update Standard
Windows Server 2008 R2 and Windows Server 2012 R2 are supported for the
purposes of running Horizon Client in nested mode. For more information,
see “Features Supported in Nested Mode,” on page 77.
Connection Server,
Security Server, and
View Agent or
Horizon Agent
Latest maintenance release of View 5.3.x and later releases
If client systems connect from outside the corporate rewall, VMware
recommends that you use a security server or Access Point appliance so that
client systems will not require a VPN connection.
Remote (hosted) applications are available only on Horizon 6.0 (or later)
View servers.
N Clients can also connect to the Access Point appliance, which is
available with Horizon 6, version 6.2, or a later release.
Display protocol for
View
VMware Blast, PCoIP, and RDP
Hardware Requirements
for PCoIP and VMware
Blast
nx86-based processor with SSE2 extensions, with a 800MHz or higher
processor speed.
Using VMware Horizon Client for Windows
10 VMware, Inc.
nAvailable RAM above system requirements to support various monitor
setups. Use the following formula as a general guide:
20MB + (24 * (# monitors) * (monitor width) * (monitor height))
As a rough guide, you can use the following calculations:
1 monitor: 1600 x 1200: 64MB
2 monitors: 1600 x 1200: 128MB
3 monitors: 1600 x 1200: 256MB
Hardware Requirements
for RDP
nx86-based processor with SSE2 extensions, with a 800MHz or higher
processor speed.
n128MB RAM.
Software Requirements
for RDP
nFor Windows 7, use RDP 7.1 or 8.0. Windows 7 includes RDP 7.
Windows 7 SP1 includes RDP 7.1.
nFor Windows 8, use RDP 8.0. For Windows 8.1, use RDP 8.1.
nFor Windows 10, use RDP 10.0.
n(Supported with View Agent 6.0.2 and earlier only) For Windows XP
desktop virtual machines, you must install the RDP patches listed in
Microsoft Knowledge Base (KB) articles 323497 and 884020. If you do not
install the RDP patches, a Windows Sockets failed error message might
appear on the client.
nThe agent installer congures the local rewall rule for inbound RDP
connections to match the current RDP port of the host operating system,
which is typically 3389. If you change the RDP port number, you must
change the associated rewall rules.
You can download Remote Desktop Client versions from the Microsoft
Download Center.
System Requirements for Real-Time Audio-Video
Real-Time Audio-Video works with standard webcam, USB audio, and analog audio devices, and with
standard conferencing applications like Skype, WebEx, and Google Hangouts. To support Real-Time Audio-
Video, your View deployment must meet certain software and hardware requirements.
View remote desktop The desktops must have View Agent 5.2 or later, or Horizon Agent 7.0 or
later, installed. For View Agent 5.2 desktops, the desktops must also have the
corresponding Remote Experience Agent installed. For example, if View
Agent 5.2 is installed, you must also install the Remote Experience Agent
from View 5.2 Feature Pack 2. See the View Feature Pack Installation and
Administration document for View. If you have View Agent 6.0 or later, or
Horizon Agent 7.0 or later, no feature pack is required. To use Real-Time
Audio-Video with RDS desktops and remote applications, you must have
Horizon Agent 7.0.2 or later.
Horizon Client computer
or client access device
nReal-Time Audio-Video is supported on all operating systems that run
Horizon Client for Windows. For details, see “System Requirements for
Windows Clients,” on page 10.
Chapter 1 System Requirements and Setup for Windows-Based Clients
VMware, Inc. 11
nThe webcam and audio device drivers must be installed, and the
webcam and audio device must be operable, on the client computer. To
support Real-Time Audio-Video, you do not have to install the device
drivers on the desktop operating system where the agent is installed.
Display protocol for
View
nPCoIP
nVMware Blast (requires Horizon Agent 7.0 or later)
Real-Time Audio-Video is not supported in RDP desktop sessions.
Requirements for Scanner Redirection
You can scan information into your remote desktops and applications with scanners that are connected to
your local client system.
To use this feature, your remote desktops, applications, and client computers must meet certain system
requirements
View remote desktop The remote desktops must have View Agent 6.0.2 or later, or Horizon Agent
7.0 or later, installed with the Scanner Redirection setup option, on the parent
or template virtual machines or RDS hosts. On Windows desktop and
Windows Server guest operating systems, the Horizon Agent Scanner
Redirection setup option is deselected by default.
For information about which guest operating systems are supported on
single-user virtual machines and on RDS hosts, and for information about
conguring scanner redirection in remote desktops and applications, see
"Congure Scanner Redirection," in Seing Up Desktop and Application Pools in
View.
Horizon Client computer
or client access device
nScanner redirection is supported on Windows 7, Windows 8/8.1, and
Windows 10.
nThe scanner device drivers must be installed, and the scanner must be
operable, on the client computer. You do not need to install the scanner
device drivers on the remote desktop operating system where the agent
is installed.
Scanning device
standard
TWAIN or WIA
Display protocol for
View
nPCoIP
nVMware Blast Extreme (requires Horizon Agent 7.0 or later)
Scanner redirection is not supported in RDP desktop sessions.
Requirements for Serial Port Redirection
With this feature, users can redirect locally connected, serial (COM) ports, such as built-in RS232 ports or
USB to Serial adapters, to their remote desktops. To support serial port redirection, your View deployment
must meet certain software and hardware requirements.
View remote desktop The remote desktops must have View Agent 6.1.1 or later, or Horizon Agent
7.0 or later, installed with the Serial Port Redirection setup option, on the
parent or template virtual machines. This setup option is deselected by
default.
Using VMware Horizon Client for Windows
12 VMware, Inc.
The following guest operating systems are supported on single-user virtual
machines:
n32-bit or 64-bit Windows 7
n32-bit or 64-bit Windows 8.x
n32-bit or 64-bit Windows 10
nWindows Server 2008 R2 congured as a desktop
nWindows Server 2012 R2 congured as a desktop
This feature is not currently supported for Windows Server RDS hosts.
Serial port device drivers do not have to be installed on the desktop
operating system where the agent is installed.
N For information about conguring serial port redirection in remote
desktops, see "Conguring Serial Port Redirection," in Seing Up Desktop and
Application Pools in View.
Horizon Client computer
or client access device
nSerial port redirection is supported on Windows 7, Windows 8.x client
systems, and Windows 10.
nAny required serial port device drivers must be installed, and the serial
port must be operable, on the client computer. You do not need to install
the device drivers on the remote desktop operating system where the
agent is installed.
Display protocol for
View
nPCoIP
nVMware Blast Extreme (requires Horizon Agent 7.0 or later)
VMware Horizon serial port redirection is not supported in RDP desktop
sessions.
Requirements for Multimedia Redirection (MMR)
With multimedia redirection (MMR), the multimedia stream is processed, that is, decoded, on the client
system. The client system plays the media content, thereby reducing the load on the ESXi host.
View remote desktop nSingle-user desktops must have View Agent 6.0.2 or later, or
Horizon Agent 7.0 or later, installed.
nSession-based desktops must have View Agent 6.1.1 or later, or
Horizon Agent 7.0 or later, installed on the RDS host.
Chapter 1 System Requirements and Setup for Windows-Based Clients
VMware, Inc. 13
nFor information about operating system requirements and other
software requirements and conguration seings for the remote desktop
or application, see the topics about Windows Media Multimedia
Redirection in Seing Up Desktop and Application Pools in View.
Horizon Client computer
or client access device
32-bit or 64-bit Windows 7, Windows 8.x, or Windows 10.
Supported media
formats
Media formats that are supported on Windows Media Player are supported.
For example: M4V; MOV; MP4; WMP; MPEG-4 Part 2; WMV 7, 8, and 9;
WMA; AVI; ACE; MP3; WAV.
N DRM-protected content is not redirected through Windows Media
MMR.
Requirements for Flash Redirection
With Flash Redirection, if you use Internet Explorer 9, 10, or 11, Flash content is sent to the client system.
The client system plays the media content, which reduces the load on the ESXi host.
Remote desktop nHorizon Agent 7.0 or later must be installed in a single-user (VDI)
remote desktop, with the Flash Redirection option. The Flash
Redirection option is not selected by default.
See the topics about installing Horizon Agent in the Seing Up Desktop
and Application Pools in View document.
nThe appropriate group policy seings must be congured. See the topics
about conguring Flash Redirection in the Seing Up Desktop and
Application Pools in View document.
nFlash Redirection is supported on Windows 7, Windows 8, Windows 8.1,
and Windows 10 single-user remote desktops.
nInternet Explorer 9, 10, or 11 must be installed with the corresponding
Flash ActiveX plug-in.
nAfter installation, the VMware View FlashMMR Server add-on must be
enabled in Internet Explorer.
Horizon Client computer
or client access device
nFlash Redirection is supported on Windows 7, Windows 8, Windows 8.1,
and Windows 10.
nThe Flash ActiveX plug-in must be installed and enabled
Display protocol for the
remote session
VMware Blast, PCoIP
Using VMware Horizon Client for Windows
14 VMware, Inc.
Requirements for Using Flash URL Redirection
Streaming Flash content directly from Adobe Media Server to client endpoints lowers the load on the
datacenter ESXi host, removes the extra routing through the datacenter, and reduces the bandwidth
required to simultaneously stream live video events to multiple client endpoints.
The Flash URL redirection feature uses a JavaScript that is embedded inside a Web page by the Web page
administrator. Whenever a virtual desktop user clicks on the designated URL link from within a Web page,
the JavaScript intercepts and redirects the ShockWave File (SWF) from the virtual desktop session to the
client endpoint. The endpoint then opens a local VMware Flash Projector outside of the virtual desktop
session and plays the media stream locally. Both multicast and unicast are supported.
This feature is available when used in conjunction with the correct version of the agent software. For View
5.3, this feature is included in the Remote Experience Agent, which is part of the View Feature Pack. For
View 6.0 and later releases, this feature is included in View Agent or Horizon Agent.
To use this feature, you must set up your Web page and your client devices. Client systems must meet
certain software requirements:
nClient systems must have IP connectivity to the Adobe Web server that hosts the ShockWave File (SWF)
that initiates the multicast or unicast streaming. If needed, congure your rewall to open the
appropriate ports to allow client devices to access this server.
nClient systems must have Adobe Flash Player 10.1 or later for Internet Explorer (which uses ActiveX).
For a list of the remote desktop requirements for Flash URL redirection, and for instructions about how to
congure a Web page to provide a multicast or unicast stream, see the View documentation.
Requirements for URL Content Redirection
With URL Content Redirection, you can have URL content redirected from a client to a remote desktop or
application, or vice versa. For example, you can enter an URL or click a link in Internet Explorer on the client
and have the remote application Chrome display the content, or click an HTTP link in the remote
application Word and have a browser on the client display the content.
You can congure any number of protocols, such as HTTP, mailto, and callto, for redirection. This feature
supports redirection in both directions:
nFrom a client to a remote desktop or application (client to agent)
Based on the rules that you set up, Horizon Client launches either a remote desktop or a remote
application to handle the URL. If a desktop is launched, the default application for the URL's protocol
processes the URL.
nFrom a remote desktop or application to a client (agent to client)
Horizon Agent sends the URL to Horizon Client, which launches the default application for the
protocol that is specied in the URL.
This feature requires that the Horizon administrator congures GPO seings that apply to remote desktops,
RDS hosts, and Horizon Clients. The GPO seings specify how Horizon Client and Horizon Agent redirect
URL content. For more information about this feature, including limitations and GPO seings, see
"Conguring URL Content Redirection" in the Seing Up Desktop and Application Pools in View document.
This feature has the following requirements:
Remote desktop or RDS
host that provides
remote applications
nHorizon Agent 7.0 or later. This feature must be installed if you want to
congure agent-to-client redirection.
Chapter 1 System Requirements and Setup for Windows-Based Clients
VMware, Inc. 15
nThe supported browsers in which you can type or click a URL and have
that URL redirected are Internet Explorer 9,10, and 11.
Horizon Client computer
or client access device
nThis feature must be installed if you want to congure client-to-agent
redirection.
nThe supported browsers in which you can type or click a URL and have
that URL redirected are Internet Explorer 9, 10, and 11.
Display Protocol for the
Remote Session
VMware Blast or PCoIP
Requirements for Using Microsoft Lync with Horizon Client
You can use a Microsoft Lync 2013 client on remote desktops to participate in Unied Communications (UC)
VoIP (voice over IP) and video chat calls with Lync certied USB audio and video devices. A dedicated IP
phone is no longer required.
This architecture requires the installation of a Microsoft Lync 2013 client on the remote desktop and a
Microsoft Lync VDI plug-in on the client endpoint. Customers can use the Microsoft Lync 2013 client for
presence, instant messaging, Web conferencing, and Microsoft Oce functionality.
Whenever a Lync VoIP or video chat call occurs, the Lync VDI plug-in ooads all the media processing
from the datacenter server to the client endpoint, and encodes all media into Lync-optimized audio and
video codecs. This optimized architecture is highly scalable, results in lower network bandwidth used, and
provides point-to-point media delivery with support for high-quality real-time VoIP and video. For more
information, see the white paper about Horizon 6 and Microsoft Lync 2013, at
hp://www.vmware.com/les/pdf/techpaper/vmware-horizon-view-microsoft-lync-install-congure.pdf.
N Recording audio is not yet supported. This integration is supported only with the PCoIP display
protocol.
This feature has the following requirements.
Operating system nClient operating system: Windows 7 SP1, Windows 8.x, or Windows 10.
nVirtual machine (agent) operating system depends on the agent version.
Version Guest Operating System
View Agent 6.2 or later,
or Horizon Agent 7.0 or
later
32- or 64-bit Windows 7 SP1, Windows 8.x, Windows
10, or 64-bit Windows Server 2008 R2 SP1
For Microsoft RDS hosts: Windows Server 2008 R2,
Windows Server 2012, or Windows Server 2012 R2
View Agent 6.0 or 6.1 32- or 64-bit Windows 7 SP1, Windows 8.x, or 64-bit
Windows Server 2008 R2 SP1
View Agent 5.3 32- or 64-bit Windows 7 SP1
Client system software n32-bit version of Microsoft Lync VDI Plug-in
I The 64-bit version of Microsoft Oce must not be installed
on the client machine. The 32-bit Microsoft Lync VDI plugin that is
required is not compatible with 64-bit Microsoft Oce 2013.
nSecurity certicate generated during Microsoft Lync Server 2013
deployment must be imported into the Trusted Root Certicate
Authorities directory.
Using VMware Horizon Client for Windows
16 VMware, Inc.
Remote desktop (agent)
software
nView Agent 5.3 or later, or Horizon Agent 7.0 or later
nMicrosoft Lync 2013 Client
With the View 5.3 or later agent, the Lync 2013 client bit-level is not
required to match the bit-level of the virtual machine operating system.
nSecurity certicate generated during Microsoft Lync Server 2013
deployment must be imported into the Trusted Root Certicate
Authorities directory
Required servers nA server running View Connection Server 5.3 or later
nA server running Microsoft Lync Server 2013
nA vSphere infrastructure to host the virtual machines
The vCenter Server and ESXi hosts must be running vSphere 5.0 or later.
Hardware nHardware that supports each of the required software components
previously listed
nClient endpoint: 1.5GHz or faster CPU and a minimum of 2GB of RAM
for the Microsoft Lync 2013 Plug-in
N For troubleshooting information, see VMware KB 2063769 and VMware KB 2053732.
Smart Card Authentication Requirements
Client systems that use a smart card for user authentication must meet certain requirements.
Each client system that uses a smart card for user authentication must have the following software and
hardware:
nHorizon Client
nA compatible smart card reader
nProduct-specic application drivers
You must also install product-specic application drivers on the remote desktops or Microsoft RDS host.
View supports smart cards and smart card readers that use a PKCS#11 or Microsoft CryptoAPI provider.
You can optionally install the ActivIdentity ActivClient software suite, which provides tools for interacting
with smart cards.
Users that authenticate with smart cards must have a smart card or USB smart card token, and each smart
card must contain a user certicate.
To install certicates on a smart card, you must set up a computer to act as an enrollment station. This
computer must have the authority to issue smart card certicates for users, and it must be a member of the
domain you are issuing certicates for.
I When you enroll a smart card, you can choose the key size of the resulting certicate. To use
smart cards with local desktops, you must select a 1024-bit or 2048-bit key size during smart card
enrollment. Certicates with 512-bit keys are not supported.
The Microsoft TechNet Web site includes detailed information on planning and implementing smart card
authentication for Windows systems.
Chapter 1 System Requirements and Setup for Windows-Based Clients
VMware, Inc. 17
In addition to meeting these requirements for Horizon Client systems, other View components must meet
certain conguration requirements to support smart cards:
nFor information about conguring Connection Server to support smart card use, see "Seing Up Smart
Card Authentication" in the View Administration document.
You must add all applicable Certicate Authority (CA) certicates for all trusted user certicates to a
server truststore le on the Connection Server host or security server host. These certicates include
root certicates and must include intermediate certicates if the user's smart card certicate was issued
by an intermediate certicate authority.
nFor information about tasks you might need to perform in Active Directory to implement smart card
authentication, see "Seing Up Smart Card Authentication" in the View Administration document.
Enabling the Username Hint Field in Horizon Client
In some environments, smart card users can use a single smart card certicate to authenticate to multiple
user accounts. Users enter their user name in the Username hint eld during smart card sign-in.
To make the Username hint eld appear on the Horizon Client login dialog box, you must enable the smart
card user name hints feature for the Connection Server instance in View Administrator. The smart card user
name hints feature is supported only with Horizon 7 version 7.0.2 and later servers and agents. For
information about enabling the smart card user name hints feature, see "Seing Up Smart Card
Authentication" in the View Administration document.
If your environment uses an Access Point appliance rather than a security server for secure external access,
you must congure the Access Point appliance to support the smart card user name hints feature. The smart
card user name hints feature is supported only with Access Point 2.7.2 and later. For information about
enabling the smart card user name hints feature in Access Point, see the Deploying and Conguring Access
Point document.
N Horizon Client still supports single-account smart card certicates when the smart card user name
hints feature is enabled.
Device Authentication Requirements
You can set up certicate authentication for client devices.
This feature has the following requirements:
nAccess Point 2.6 or later.
nHorizon 7 version 7.0 or later.
nA certicate installed on the client device that Access Point will accept.
Supported Desktop Operating Systems
Administrators create virtual machines with a guest operating system and install agent software in the guest
operating system. End users can log in to these virtual machines from a client device.
For a list of the supported Windows guest operating systems, see the "Supported Operating Systems for
View Agent" topic in the View 5.x or 6.x installation documentation. See the "Supported Operating Systems
for Horizon Agent" topic in the Horizon 7 installation documentation.
Some Linux guest operating systems are also supported if you have View Agent 6.1.1 or later, or
Horizon Agent 7.0 or later. For information about system requirements, conguring Linux virtual machines
for use in Horizon 6 or Horizon 7, and a list of supported features, see Seing Up Horizon 6 for Linux
Desktops, which is part of the Horizon 6, version 6.1 documentation, or see Seing Up Horizon 7 for Linux
Desktops.
Using VMware Horizon Client for Windows
18 VMware, Inc.
Preparing Connection Server for Horizon Client
Administrators must perform specic tasks to enable end users to connect to remote desktops and
applications.
Before end users can connect to Connection Server or a security server and access a remote desktop or
application, you must congure certain pool seings and security seings:
nIf you plan to use Access Point, congure Connection Server to work with Access Point. See Deploying
and Conguring Access Point. Access Point appliances fulll the same role that was previously played by
only security servers.
nIf you are using a security server, verify that you are using the latest maintenance releases of
Connection Server 5.3.x and Security Server 5.3.x or later releases. For more information, see the View
Installation document.
nIf you plan to use a secure tunnel connection for client devices and if the secure connection is
congured with a DNS host name for Connection Server or a security server, verify that the client
device can resolve this DNS name.
To enable or disable the secure tunnel, in View Administrator, go to the Edit View Connection Server
Seings dialog box and use the check box called Use secure tunnel connection to desktop.
nVerify that a desktop or application pool has been created and that the user account that you plan to use
is entitled to access the pool.
For Connection Server 5.3.x, see the topics about creating desktop pools in the View Administration
document. For Connection Server 6.0 and later, see the topics about creating desktop and application
pools in the Seing Up Desktop and Application Pools in View document.
I If end users have a high-resolution display and will use the High Resolution Mode client
seing while viewing their remote desktops in full screen mode, you must allocate sucient VRAM for
each Windows 7 or later remote desktop. The amount of vRAM depends on the number of monitors
congured for end users and on the display resolution. To estimate the amount of vRAM you need, see
the section "RAM Sizing for Specic Monitor Congurations" of the topic "Estimating Memory
Requirements for Virtual Desktops," in the View Architecture Planning document.
nTo use two-factor authentication with Horizon Client, such as RSA SecurID or RADIUS authentication,
you must enable this feature on Connection Server. For more information, see the topics about two-
factor authentication in the View Administration document.
Configure VMware Blast Options
You can congure H.264 decoding and network protocol options for remote desktop and application
sessions that use the VMware Blast display protocol.
The maximum resolution that is supported depends on the capability of the graphical processing unit (GPU)
on the client. A GPU that can support 4K resolution for JPEG/PNG might not support 4K resolution for H.
264. If a resolution for H.264 is not supported, Horizon Client uses JPEG/PNG instead.
Prerequisites
This feature requires Horizon Agent 7.0 or later.
Procedure
1 In the desktop and application selector window of Horizon Client, click the Seings icon in the upper-
right portion of the window, and select VMware Blast in the left pane of the Seings window.
Chapter 1 System Requirements and Setup for Windows-Based Clients
VMware, Inc. 19
2Congure the decoding and network protocol options.
Option Description
H.264 Select this option to allow H.264 decoding in Horizon Client. When this
option is selected (the default seing), Horizon Client uses H.264 decoding
if the agent supports H.264 software encoding. If the agent does not
support H.264 software encoding, Horizon Client uses JPG/PNG decoding.
Deselect this option to use JPG/PNG decoding.
UDP Select this option to allow UDP networking in Horizon Client. When this
option is selected (the default seing), Horizon Client uses UDP
networking if UDP connectivity is available. If UDP networking is blocked,
Horizon Client uses TCP networking.
Deselect this option to use TCP networking.
N UDP is disabled by default on a Horizon remote desktop. For UDP
to work, it must be enabled on the desktop, the client, and the Blast Secure
Gateway (BSG).
Your changes take eect the next time a user connects to a remote desktop or application and selects the
VMware Blast display protocol. Your changes do not aect existing VMware Blast sessions.
Horizon Client Data Collected by VMware
If your company participates in the customer experience improvement program, VMware collects data from
certain Horizon Client elds. Fields containing sensitive information are made anonymous.
VMware collects data on the clients to prioritize hardware and software compatibility. If your company's
administrator has opted to participate in the customer experience improvement program, VMware collects
anonymous data about your deployment in order to improve VMware's response to customer requirements.
No data that identies your organization is collected. Horizon Client information is sent rst to Connection
Server and then on to VMware, along with data from Connection Server instances, desktop pools, and
remote desktops.
Although the information is encrypted while in transit to Connection Server, the information on the client
system is logged unencrypted in a user-specic directory. The logs do not contain any personally identiable
information.
The administrator who installs Connection Server can select whether to participate in the VMware customer
experience improvement program while running the Connection Server installation wizard, or an
administrator can set an option in View Administrator after the installation.
Table 1‑1. Data Collected from Horizon Clients for the Customer Experience Improvement Program
Description
Is This Field
Made
Anonymous
? Example Value
Company that produced the
Horizon Client application
No VMware
Product name No VMware Horizon Client
Client product version No (The format is x.x.x-yyyyyy, where x.x.x is the client version
number and yyyyyy is the build number.)
Client binary architecture No Examples include the following:
ni386
nx86_64
narm
Using VMware Horizon Client for Windows
20 VMware, Inc.
Table 1‑1. Data Collected from Horizon Clients for the Customer Experience Improvement Program
(Continued)
Description
Is This Field
Made
Anonymous
? Example Value
Client build name No Examples include the following:
nVMware-Horizon-Client-Win32-Windows
nVMware-Horizon-Client-Linux
nVMware-Horizon-Client-iOS
nVMware-Horizon-Client-Mac
nVMware-Horizon-Client-Android
nVMware-Horizon-Client-WinStore
Host operating system No Examples include the following:
nWindows 8.1
nWindows 7, 64-bit Service Pack 1 (Build 7601 )
niPhone OS 5.1.1 (9B206)
nUbuntu 12.04.4 LTS
nMac OS X 10.8.5 (12F45)
Host operating system kernel No Examples include the following:
nWindows 6.1.7601 SP1
nDarwin Kernel Version 11.0.0: Sun Apr 8 21:52:26 PDT
2012; root:xnu-1878.11.10~1/RELEASE_ARM_S5L8945X
nDarwin 11.4.2
nLinux 2.6.32-44-generic #98-Ubuntu SMP Mon Sep 24
17:27:10 UTC 2012
nunknown (for Windows Store)
Host operating system architecture No Examples include the following:
nx86_64
ni386
narmv71
nARM
Host system model No Examples include the following:
nDell Inc. OptiPlex 960
niPad3,3
nMacBookPro8,2
nDell Inc. Precision WorkStation T3400 (A04 03/21/2008)
Host system CPU No Examples include the following:
nIntel(R) Core(TM)2 Duo CPU E8400 @ 3.00GH
nIntel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GH
nunknown (for iPad)
Number of cores in the host system's
processor
No For example: 4
MB of memory on the host system No Examples include the following:
n4096
nunknown (for Windows Store)
Number of USB devices connected No 2 (USB device redirection is supported only for Linux,
Windows, and Mac clients.)
Maximum concurrent USB device
connections
No 2
Chapter 1 System Requirements and Setup for Windows-Based Clients
VMware, Inc. 21
Table 1‑1. Data Collected from Horizon Clients for the Customer Experience Improvement Program
(Continued)
Description
Is This Field
Made
Anonymous
? Example Value
USB device vendor ID No Examples include the following:
nKingston
nNEC
nNokia
nWacom
USB device product ID No Examples include the following:
nDataTraveler
nGamepad
nStorage Drive
nWireless Mouse
USB device family No Examples include the following:
nSecurity
nHuman Interface Device
nImaging
USB device usage count No (Number of times the device was shared)
Using VMware Horizon Client for Windows
22 VMware, Inc.
Installing Horizon Client for Windows 2
You can obtain the Windows-based Horizon Client installer either from the VMware Web site or from a Web
access page provided by View Connection Server. You can set various startup options for end users after
Horizon Client is installed.
This chapter includes the following topics:
n“Enabling FIPS Mode in the Windows Client Operating System,” on page 23
n“Install Horizon Client for Windows,” on page 24
n“Installing Horizon Client Silently,” on page 25
n“Upgrade Horizon Client Online,” on page 30
Enabling FIPS Mode in the Windows Client Operating System
If you plan to install Horizon Client with Federal Information Processing Standard (FIPS) compliant
cryptography, you must enable FIPS mode in the client operating system before you run the Horizon Client
installer.
When FIPS mode is enabled in the client operating system, applications use only cryptographic algorithms
that are FIPS-140 compliant and in compliance with FIPS-approved modes of operation. You can enable FIPS
mode by enabling a specic security seing, either in the Local Security Policy or as part of Group Policy, or
by editing a Windows Registry key.
I Installing Horizon Client with FIPS-compliant cryptography is supported only for client
systems that have Windows 7 SP1 operating systems.
For more information about FIPS support, which is available with Horizon 6 version 6.2 or later, see the View
Installation document.
Setting the FIPS Configuration Property
To enable FIPS mode in the client operating system, you can use a Windows group policy seing or a
Windows Registry seing for the client computer.
nTo use the group policy seing, open the Group Policy Editor, navigate to Computer
Configuration\Windows Settings\Security Settings\Local Policies\Security Options, and enable
the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing
seing.
nTo use the Windows Registry, go to
HKLM\System\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy\Enabled and set Enabled to 1.
VMware, Inc. 23
For more information about FIPS mode, go to hps://support.microsoft.com/en-us/kb/811833.
I If you do not enable FIPS mode before running the Horizon Client installer, the installer option
to use FIPS-compliant cryptography does not appear during a custom installation. FIPS-compliant
cryptography is not enabled during a typical installation. If you install Horizon Client without the FIPS-
compliant cryptography option and you later decide to use the option, you must uninstall the client, enable
FIPS mode in the client operating system, and run the Horizon Client installer again.
Install Horizon Client for Windows
End users open Horizon Client to connect to their remote desktops and remote applications from a client
system. You can run a Windows-based installer le to install all Horizon Client components.
The installer determines whether the client system has a 64-bit or 32-bit operating and installs the correct
version of Horizon Client for the client system. The installer does not run on Windows XP or Windows
Vista.
This procedure describes how to install Horizon Client by using an interactive installation wizard. To install
the URL Content Redirection feature, you must run the installer from the command line and specify the
URL_FILTERING_ENABLED parameter, for example, VMware-Horizon-Client-y.y.y-xxxxxx.exe /v
URL_FILTERING_ENABLED=1. To use the command-line, silent installation feature of the Microsoft Windows
Installer (MSI), see “Install Horizon Client Silently,” on page 25.
N You can install Horizon Client in a remote desktop virtual machine if that desktop is running View
Agent 6.0 or later, or Horizon Agent 7.0 or later. Companies might use this installation strategy if their end
users access remote applications from Windows thin-client devices.
Prerequisites
nVerify that the client system uses a supported operating system. See “System Requirements for
Windows Clients,” on page 10.
nVerify that you have the URL for a download page that contains the Horizon Client installer. This URL
might be the VMware Downloads page at hp://www.vmware.com/go/viewclients, or it might be the
URL for a Connection Server instance.
nVerify that you can log in as an administrator on the client system.
nVerify that the domain controllers have the latest patches, enough free disk space, and can communicate
with each other. Otherwise, when you run the installer on a Windows 8.1 system, the installer can take
an unusual amount of time to nish. This problem occurs if the machine's domain controller, or another
domain controller in its hierarchy, is unresponsive or unreachable.
nIf you plan to install Horizon Client with FIPS-compliant cryptography, enable FIPS mode in the client
operating system before you run the Horizon Client installer. See “Enabling FIPS Mode in the Windows
Client Operating System,” on page 23.
nIf you plan to install the USB Redirection component, do the following:
nDetermine whether the person who uses the client device is allowed to access locally connected
USB devices from a remote desktop. If access is not permied, either do not install the USB
Redirection component, or install the component and disable it by using a group policy seing. If
you use group policy to disable USB redirection, you do not need to reinstall Horizon Client if you
later decide to enable USB redirection for a client. For more information, see “Scripting Denition
Seings for Client GPOs,” on page 42.
nVerify that the Windows Automatic Update feature is not turned o on the client computer.
Using VMware Horizon Client for Windows
24 VMware, Inc.
nDecide whether to use the feature that allows end users to log in to Horizon Client and their remote
desktop as the currently logged in user. Credential information that the user entered when logging in to
the client system is passed to the Connection Server instance and ultimately to the remote desktop.
Some client operating systems do not support this feature.
nIf you do not want to require end users to supply the fully qualied domain name (FQDN) of the
Connection Server instance, determine the FQDN so that you can supply it during installation.
Procedure
1 Log in to the client system as an administrator.
2 Navigate to the VMware product page at hp://www.vmware.com/go/viewclients.
3 Download the installer le, for example, VMware-Horizon-Client-y.y.y-xxxxxx.exe.
xxxxxx is the build number and y.y.y is the version number.
4 Double-click the installer le to begin the installation.
5 Select the installation type and follow the prompts.
Option Description
Typical Installs the IPv4 Internet protocol and the USB Redirection and Log in as
current user features. If FIPS mode is enabled on the client operating
system, FIPS-compliant cryptography is disabled.
Custom Allows you to select the components to install. Follow these guidelines
when selecting components:
nDo not select the IPv6 Internet protocol unless all the components in
your Horizon environment use IPv6. If you select IPv6, several
features are unavailable. For more information, see the View Installation
document.
nYou can enable FIPS-compliant cryptography only if you have already
enabled FIPS mode on the client operating system.
The installer installs certain Windows services, including VMware Horizon Client
(horizon_client_service), VMware USB Arbitration Service (VMUSBArbService), and VMware View USB
(vmware-view-usbd).
What to do next
Start Horizon Client and verify that you can log in to the correct remote desktop or application. See
“Connect to a Remote Desktop or Application,” on page 63.
Installing Horizon Client Silently
You can install Horizon Client silently by typing the installer lename and installation options at the
command line. With silent installation, you can eciently deploy View components in a large enterprise.
Install Horizon Client Silently
You can use the silent installation feature of the Microsoft Windows Installer (MSI) to install Horizon Client
on several Windows computers. In a silent installation, you use the command line and do not have to
respond to wizard prompts.
The installer determines whether the client system has a 64-bit or 32-bit operating and installs the correct
version of Horizon Client for the client system.
Chapter 2 Installing Horizon Client for Windows
VMware, Inc. 25
Prerequisites
nVerify that the client system uses a supported operating system. See “System Requirements for
Windows Clients,” on page 10.
nVerify that you can log in as an administrator on the client system.
nVerify that the domain controllers have the latest patches, enough free disk space, and can communicate
with each other. Otherwise, when you run the installer on a Windows 8.1 system, the installer can take
an unusual amount of time to nish. This problem occurs if the machine's domain controller, or another
domain controller in its hierarchy, is unresponsive or unreachable.
nIf you plan to install Horizon Client with FIPS-compliant cryptography, enable FIPS mode in the client
operating system before you run the Horizon Client installer. See “Enabling FIPS Mode in the Windows
Client Operating System,” on page 23.
nDecide whether to use the feature that allows end users to log in to Horizon Client and their remote
desktop as the currently logged in user. Credential information that the user entered when logging in to
the client system is passed to the Connection Server instance and ultimately to the remote desktop.
Some client operating systems do not support this feature.
nBecome familiar with the MSI installer command-line options. See “Microsoft Windows Installer
Command-Line Options,” on page 28.
nBecome familiar with the silent installation (MSI) properties available with Horizon Client. See “Silent
Installation Properties for Horizon Client,” on page 27.
nDetermine whether to allow end users to access locally connected USB devices from their virtual
desktops. If not, set the MSI property, ADDLOCAL, to the list of features of interest and omit the USB
feature. For details, see “Silent Installation Properties for Horizon Client,” on page 27.
nIf you do not want to require end users to supply the fully qualied domain name (FQDN) of the
Connection Server instance, determine the FQDN so that you can supply it during installation.
Procedure
1 Log in to the client system as an administrator.
2 Navigate to the VMware product page at hp://www.vmware.com/go/viewclients.
3 Download the Horizon Client installer le, for example, VMware-Horizon-Client-y.y.y-xxxxxx.exe.
xxxxxx is the build number and y.y.y is the version number.
4 Open a command prompt on the Windows client computer.
5 Type the installation command on one line.
This example installs Horizon Client silently:
VMware-Horizon-Client-y.y.y-xxxxxx.exe /s /v"/qn ADDLOCAL=Core,USB,TSSO"
Alternatively, you can use ADDLOCAL=ALL instead of ADDLOCAL=Core,USB,TSSO.
N The Core feature is mandatory.
The installer installs certain Windows services, including VMware Horizon Client
(horizon_client_service), VMware USB Arbitration Service (VMUSBArbService), and VMware View USB
(vmware-view-usbd).
Using VMware Horizon Client for Windows
26 VMware, Inc.
What to do next
(Optional) If you installed Horizon Client with the URL Content Redirection feature, verify that the feature
is installed by checking that the vmware-url-protocol-launch-helper.exe and the vmware-url-filtering-
plugin.dll les are installed in the %PROGRAMFILES%\VMware\VMware Horizon View Client\ directory. Also
ensure that the Internet Explorer add-on VMware Horizon View URL Filtering Plugin is installed and
enabled.
Start Horizon Client and verify that you can log in to the correct remote desktop or application. See
“Connect to a Remote Desktop or Application,” on page 63.
Silent Installation Properties for Horizon Client
You can include specic properties when you silently install Horizon Client from the command line. You
must use a PROPERTY=value format so that Microsoft Windows Installer (MSI) can interpret the properties
and values.
Table 2-1 shows the Horizon Client silent installation properties that you can use at the command-line.
Table 2‑1. MSI Properties for Silently Installing Horizon Client
MSI Property Description Default Value
INSTALLDIR The path and folder in which the Horizon Client software is
installed.
For example: INSTALLDIR=""D:\abc\my folder""
The sets of two double quotes that enclose the path permit the
MSI installer to interpret the space as a valid part of the path.
%ProgramFiles
%\VMware\VMware Horizon
View Client
VDM_IP_PROTOCOL_USAGE Species the IP (network protocol) version that View
components use for communication. The possible values are
IPv4 and IPv6.
IPv4
VDM_SERVER The fully qualied domain name (FQDN) of the View
Connection Server instance to which Horizon Client users
connect by default. When you congure this property,
Horizon Client users do not have to supply this FQDN.
For example: VDM_SERVER=cs1.companydomain.com
This MSI property is optional.
None
DESKTOP_SHORTCUT Congures a desktop shortcut icon for Horizon Client.
A value of 1 installs the shortcut. A value of 0 does not install
the shortcut.
1
STARTMENU_SHORTCUT Congures a shortcut for Horizon Client in the Start menu.
A value of 1 installs the shortcut. A value of 0 does not install
the shortcut.
1
URL_FILTERING_ENABLED Species whether to install the URL Content Redirection
feature. A value of 1 installs the feature.
N The option ADDLOCAL=ALL does not include this
feature.
0
VDM_FIPS_ENABLED Species whether to install Horizon Client with FIPS-
compliant cryptography.
A value of 1 installs the client with FIPS-compliant
cryptography. A value of 0 does not.
N Before you set this option to 1, you must enable FIPS
mode in the Windows client operating system. See “Enabling
FIPS Mode in the Windows Client Operating System,” on
page 23.
0
In a silent installation command, you can use the MSI property, ADDLOCAL=, to specify features that the
Horizon Client installer congures. Each silent-installation feature corresponds to a setup option that you
can select during an interactive installation.
Chapter 2 Installing Horizon Client for Windows
VMware, Inc. 27
Table 2-2 shows the Horizon Client features you can type at the command line and the corresponding
interactive-installation options.
Table 2‑2. Horizon Client Silent Installation Features and Interactive Custom Setup Options
Silent Installation Feature Custom Setup Option in an Interactive Installation
Core
If you specify individual features with the MSI property,
ADDLOCAL=, you must include Core.
None.
During an interactive installation, the core Horizon Client
functions are installed by default.
TSSO Log in as the currently logged-in Windows domain user
USB USB Redirection
Microsoft Windows Installer Command-Line Options
To install Horizon Client silently, you must use Microsoft Windows Installer (MSI) command-line options
and properties. The Horizon Client installers are MSI programs and use standard MSI features. You can also
use MSI command-line options to uninstall Horizon Client silently.
For details about MSI, see the Microsoft Web site. For MSI command-line options, see the Microsoft
Developer Network (MSDN) Library Web site and search for MSI command-line options. To see MSI
command-line use, you can open a command prompt on the client computer and type msiexec /?.
To run the Horizon Client installer silently, you begin by silencing the bootstrap program that extracts the
installer into a temporary directory and starts an interactive installation.
The following table shows the command-line options that control the installer bootstrap program.
Table 2‑3. Command-Line Options for the Bootstrap Program
Option Description
/s Disables the bootstrap splash screen and extraction dialog box, which prevents the display
of interactive dialog boxes.
For example: VMware-Horizon-Client-y.y.y-xxxxxx.exe /s
The /s option is required to run a silent installation. In the examples, xxxxxx is the build
number and y.y.y is the version number.
/v" MSI_command_line_options"Instructs the installer to pass the double-quote-enclosed string that you enter at the
command line as a set of options for MSI to interpret. You must enclose your command-line
entries between double quotes. Place a double quote after the /v and at the end of the
command line.
For example: VMware-Horizon-Client-y.y.y-
xxxxxx.exe /s /v"command_line_options"
To instruct the MSI installer to interpret a string that contains spaces, enclose the string in
two sets of double quotes. For example, you might want to install the client in an
installation path name that contains spaces.
For example: VMware-Horizon-View-Client-y.y.y-
xxxxxx.exe /s /v"command_line_options INSTALLDIR=""d:\abc\my folder"""
In this example, the MSI installer passes on the installation-directory path and does not
aempt to interpret the string as two command-line options. Note the nal double quote
that encloses the entire command line.
The /v"command_line_options" option is required to run a silent installation.
You control the remainder of a silent installation by passing command-line options and MSI property values
to the MSI installer, msiexec.exe. The MSI installer includes Horizon Client installation code. The installer
uses the values and options that you enter in the command line to interpret installation choices and setup
options that are specic to Horizon Client.
The following table shows the command-line options and MSI property values that are passed to the MSI
installer.
Using VMware Horizon Client for Windows
28 VMware, Inc.
Table 2‑4. MSI Command-Line Options and MSI Properties
MSI Option or Property Description
/qn Instructs the MSI installer not to display the installer wizard pages.
For example, you might want to install the agent silently and use only default setup
options and features:
VMware-Horizon-Client-y.y.y-xxxxxx.exe /s /v"/qn"
In the examples, xxxxxx is the build number and y.y.y is the version number.
Alternatively, you can use the /qr or /qb option to perform a noninteractive,
automated installation. With the /qr option, as the installation proceeds, the
wizard pages appear, but you cannot respond to them. With the /qb option, a
simple progress bar appears.
The /qn, /qb, or /qr option is required to run a noninteractive installation.
INSTALLDIR (Optional) Species an alternative installation path for installation directory.
Use the format INSTALLDIR=path to specify an installation path. You can ignore
this MSI property if you want to install the client in the default path.
ADDLOCAL (Optional) Determines the component-specic features to install. In an interactive
installation, the installer displays custom setup options to select. With the MSI
property ADDLOCAL, you can specify these setup options on the command line.
To install all available custom setup options, enter ADDLOCAL=ALL.
For example: VMware-Horizon-Client-y.y.y-xxxxxx.exe /s /v"/qn
ADDLOCAL=ALL"
If you do not use the MSI property, ADDLOCAL, the default setup options are
installed.
To specify individual setup options, enter a comma-separated list of setup option
names. Do not use spaces between names. Use the format
ADDLOCAL=value,value,value....
For example, you might want to install the client with the USB Redirection feature
but without the Log in as Current User feature:
VMware-Horizon-Client-y.y.y-xxxxxx.exe /s /v"/qn
ADDLOCAL=Core,USB"
LOGINASCURRENTUSER_DISPLAY (Optional) Determines whether the Log in as current user check box is visible on
the Horizon Client connection dialog box.
Valid values are 1 (enabled) and 0 (disabled). The default is 1, which means that
the check box is visible, and users can select or deselect it and override its default
value. When the check box is hidden, users cannot override its default value from
the Horizon Client connection dialog box.
LOGINASCURRENTUSER_DEFAULT (Optional) Species the default value of the Log in as current user check box on the
Horizon Client connection dialog box. Valid values are 1 (enabled) and 0
(disabled). No default is set, which means that the check box is deselected, and
users must provide identity and credential information multiple times before they
can access a remote desktop.
When the Log in as current user check box is selected, the identity and credential
information that the user provided when logging in to the client system is passed
to the View Connection Server instance and ultimately to the remote desktop.
Use this option with the LOGINASCURRENTUSER_DISPLAY option. For example:
LOGINASCURRENTUSER_DISPLAY=1 LOGINASCURRENTUSER_DEFAULT=1
If a user runs Horizon Client from the command line and species the
logInAsCurrentUser option, that value overrides this seing.
Chapter 2 Installing Horizon Client for Windows
VMware, Inc. 29
Table 2‑4. MSI Command-Line Options and MSI Properties (Continued)
MSI Option or Property Description
REBOOT (Optional) You can use the REBOOT=ReallySuppress option to suppress all
restarts and restart prompts.
/l*v log_file (Optional) Writes logging information in to the specied log le.
For example: /l*v ""%TEMP%\vmmsi.log""
This example generates a detailed log le that is similar to the log generated during
an interactive installation.
You can use this option to record custom features that might apply uniquely to
your installation. You can use the recorded information to specify installation
features in future silent installations.
Example: Installation Examples
In the following examples, xxxxxx is the build number, y.y.y is the version number, install_folder is the
path to the installation folder, and view.mycompany.com is the name of a ctitious View Connection Server
instance.
Default installation example:
VMware-Horizon-Client-y.y.y-xxxxxx.exe /s /v"/qn REBOOT=ReallySuppress INSTALLDIR=install_folder
ADDLOCAL=ALL DESKTOP_SHORTCUT=1 STARTMENU_SHORTCUT=1 VDM_SERVER=view.mycompany.com /l*v "%TEMP
%\log.txt""
Installation and conguration example for the Log In as Current User feature:
VMware-Horizon-Client-y.y.y-xxxxxx.exe /s /v"/qn INSTALLDIR=install_folder ADDLOCAL=Core,TSSO
LOGINASCURRENTUSER_DISPLAY=1 LOGINASCURRENTUSER_DEFAULT=1 DESKTOP_SHORTCUT=1
STARTMENU_SHORTCUT=1 VDM_SERVER=view.mycompany.com /l*v "%TEMP%\log.txt""
In this example, REBOOT=ReallySuppress is omied because the TSSO (log in as the currently logged-in
Windows domain user) option requires a reboot.
Upgrade Horizon Client Online
You can upgrade Horizon Client online if the online upgrade feature is enabled. This feature is disabled by
default.
You can enable this feature by modifying the group policy seings
Enable Horizon Client online update and URL for Horizon Client online update. For more
information, see “General Seings for Client GPOs,” on page 49.
Prerequisites
nSave your work before you update Horizon Client. The update might initiate a system reboot.
nVerify that you can log in as an administrator on the client system.
Procedure
1 Log in as an administrator.
2 In Horizon Client, click Software Updates from one of two screens.
Horizon Client Screen Action
Before you connect to a Connection
Server
Click Options > Software Updates.
After you connect to a Connection
Server
Click Help > Software Updates
Using VMware Horizon Client for Windows
30 VMware, Inc.
3 Click Check for Updates.
4 Click Download and Install.
Chapter 2 Installing Horizon Client for Windows
VMware, Inc. 31
Using VMware Horizon Client for Windows
32 VMware, Inc.
Configuring Horizon Client for End
Users 3
Conguring Horizon Client for end users can involve conguring URIs to start Horizon Client, conguring
the certicate verication mode, seing advanced TLS/SSL options, and using Group Policy Administrative
(ADM) template les to congure custom seings.
This chapter includes the following topics:
n“Common Conguration Seings,” on page 33
n“Using URIs to Congure Horizon Client,” on page 34
n“Conguring Certicate Checking for End Users,” on page 39
n“Conguring Advanced TLS/SSL Options,” on page 41
n“Congure Application Reconnection Behavior,” on page 41
n“Using the Group Policy Template to Congure VMware Horizon Client for Windows,” on page 42
n“Running Horizon Client from the Command Line,” on page 57
n“Using the Windows Registry to Congure Horizon Client,” on page 60
Common Configuration Settings
Horizon Client provides several conguration mechanisms to simplify the login and desktop selection
experience for end users, and enforce security policies.
The following table shows only some of the conguration seings that you can set in one or more ways.
Table 3‑1. Common Configuration Settings
Setting Mechanisms for Configuring
View Connection Server address URI, Group Policy, Command Line, Windows Registry
Active Directory user name URI, Group Policy, Command Line, Windows Registry
Domain name URI, Group Policy, Command Line, Windows Registry
Desktop display name URI, Group Policy, Command Line
Window size URI, Group Policy, Command Line
Display protocol URI, Command Line
Conguring certicate checking Group Policy, Windows Registry
Conguring SSL protocols and
cryptographic algorithms
Group Policy, Windows Registry
VMware, Inc. 33
Using URIs to Configure Horizon Client
Using uniform resource identiers (URIs), you can create a Web page or an email with links that end users
click to start Horizon Client, connect to a server, and open a specic desktop or application with specic
conguration options.
You can simplify the process of connecting to a remote desktop or application by creating Web or email links
for end users. You create these links by constructing URIs that provide some or all the following
information, so that your end users do not need to supply it:
nConnection Server address
nPort number for Connection Server
nActive Directory user name
nRADIUS or RSA SecurID user name, if dierent from the Active Directory user name
nDomain name
nDesktop or application display name
nWindow size
nActions including reset, log out, and start session
nDisplay protocol
nOptions for redirecting USB devices
To construct a URI, you use the vmware-view URI scheme with Horizon Client specic path and query parts.
N You can use URIs to start Horizon Client only if the client software is already installed on client
computers.
Syntax for Creating vmware-view URIs
Syntax includes the vmware-view URI scheme, a path part to specify the desktop or application, and,
optionally, a query to specify desktop or application actions or conguration options.
URI Specification
Use the following syntax to create URIs to start Horizon Client:
vmware-view://[authority-part][/path-part][?query-part]
The only required element is the URI scheme, vmware-view. For some versions of some client operating
systems, the scheme name is case-sensitive. Therefore, use vmware-view.
I In all parts, non-ASCII characters must rst be encoded according to UTF-8 [STD63], and then
each octet of the corresponding UTF-8 sequence must be percent-encoded to be represented as URI
characters.
For information about encoding for ASCII characters, see the URL encoding reference at
hp://www.utf8-chartable.de/.
authority-part Species the server address and, optionally, a user name, a non-default port
number, or both. Underscores (_) are not supported in server names. Server
names must conform to DNS syntax.
To specify a user name, use the following syntax:
user1@server-address
Using VMware Horizon Client for Windows
34 VMware, Inc.
You cannot specify a UPN address, which includes the domain. To specify
the domain, you can use the domainName query part in the URI.
To specify a port number, use the following syntax:
server-address:port-number
path-part Species the desktop or application. Use the desktop display name or
application display name. This name is the one specied in View
Administrator when the desktop or application pool was created. If the
display name has a space in it, use the %20 encoding mechanism to represent
the space.
query-part Species the conguration options to use or the desktop or application
actions to perform. Queries are not case-sensitive. To use multiple queries,
use an ampersand (&) between the queries. If queries conict with each
other, the last query in the list is used. Use the following syntax:
query1=value1[&query2=value2...]
Supported Queries
This topic lists the queries that are supported for this type of Horizon Client. If you are creating URIs for
multiple types of clients, such as desktop clients and mobile clients, see the Using VMware Horizon Client
guide for each type of client system.
action Table 3‑2. Values That Can Be Used With the action Query
Value Description
browse Displays a list of available desktops and applications hosted on the
specied server. You are not required to specify a desktop or
application when using this action.
start-session Opens the specied desktop or application. If no action query is
provided and the desktop or application name is provided,
start-session is the default action.
reset Shuts down and restarts the specied desktop or remote
application. Unsaved data is lost. Reseing a remote desktop is the
equivalent of pressing the Reset buon on a physical PC.
logoff Logs the user out of the guest operating system in the remote
desktop. If you specify an application, the action is ignored or the
end user sees the warning message "Invalid URI action."
args Species command-line arguments to add to remote application launch. Use
the syntax args=value, where value is a string. Use percent encoding for the
following characters:
nFor a colon (:), use %3A
nFor a back slash (\), use %5C
nFor a space ( ), use %20
nFor a double quotation mark ("), use %22
For example, to specify the lename "My new file.txt" for the Notepad++
application, use %22My%20new%20file.txt%22.
appProtocol For remote applications, valid values are PCOIP and BLAST. For example, to
specify PCoIP, use the syntax appProtocol=PCOIP.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 35
connectUSBOnInsert Connects a USB device to the foreground desktop when you plug in the
device. This query is implicitly set if you specify the unattended query. To use
this query, you must set the action query to start-session or else not have
an action query. Valid values are yes and no. An example of the syntax is
connectUSBOnInsert=yes.
connectUSBOnStartup Redirects all USB devices to the desktop that are currently connected to the
client system. This query is implicitly set if you specify the unattended query.
To use this query, you must set the action query to start-session or else not
have an action query. Valid values are yes and no. An example of the syntax
is connectUSBOnStartup=yes.
desktopLayout Sets the size of the window that displays a remote desktop. To use this query,
you must set the action query to start-session or else not have an action
query.
Table 3‑3. Valid Values for the desktopLayout Query
Value Description
fullscreen Full screen on one monitor. This value is the default.
multimonitor Full screen on all monitors.
windowLarge Large window.
windowSmall Small window.
WxHCustom resolution, where you specify the width by height,
in pixels. An example of the syntax is
desktopLayout=1280x800.
desktopProtocol For remote desktops, valid values are RDP, PCOIP, and BLAST. For example, to
specify PCoIP, use the syntax desktopProtocol=PCOIP.
domainName The NETBIOS domain name associated with the user who is connecting to
the remote desktop or application. For example, you might use mycompany
rather than mycompany.com.
filePath Species the path to the le on the local system that you want to open with
the remote application. You must use the full path, including the drive leer.
Use percent encoding for the following characters:
nFor a colon (:), use %3A
nFor a back slash (\), use %5C
nFor a space ( ), use %20
For example, to represent le path C:\test file.txt, use
C%3A%5Ctest%20file.txt.
tokenUserName Species the RSA or RADIUS user name. Use this query only if the RSA or
RADIUS user name is dierent from the Active Directory user name. If you
do not specify this query and RSA or RADIUS authentication is required, the
Windows user name is used. The syntax is tokenUserName=name.
Using VMware Horizon Client for Windows
36 VMware, Inc.
unattended Creates a server connection to a remote desktop in kiosk mode. If you use
this query, do not specify user information if you generated the account
name from the MAC address of the client device. If you created custom
account names in ADAM, however, such as names that begin with "custom-"
you must specify the account information.
useExisting If this option is set to true, only one Horizon Client instance can run. If users
try to connect to a second server, they must log out of the rst server, causing
desktop and application sessions to be disconnected. If this option is set to
false, multiple Horizon Client instances can run and users can connect to
multiple servers at the same time. The default is true. An example of the
syntax is useExisting=false.
Examples of vmware-view URIs
You can create hypertext links or buons with the vmware-view URI scheme and include these links in email
or on a Web page. Your end users can click these links to, for example, open a particular remote desktop
with the startup options you specify.
URI Syntax Examples
Each URI example is followed by a description of what the end user sees after clicking the URI link.
1vmware-view://view.mycompany.com/Primary%20Desktop?action=start-session
Horizon Client starts and connects to the view.mycompany.com server. The login box prompts the user for
a user name, domain name, and password. After a successful login, the client connects to the desktop
whose display name is displayed as Primary Desktop, and the user is logged in to the guest operating
system.
N The default display protocol and window size are used. The default display protocol is PCoIP.
The default window size is full screen.
2vmware-view://view.mycompany.com:7555/Primary%20Desktop
This URI has the same eect as the previous example, except that it uses the nondefault port of 7555 for
Connection Server. (The default port is 443.) Because a desktop identier is provided, the desktop opens
even though the start-session action is not included in the URI.
3vmware-view://fred@view.mycompany.com/Finance%20Desktop?desktopProtocol=PCOIP
Horizon Client starts and connects to the view.mycompany.com server. In the login box, the User name
text box is populated with the name fred. The user must supply the domain name and password. After
a successful login, the client connects to the desktop whose display name is displayed as Finance
Desktop, and the user is logged in to the guest operating system. The connection uses the PCoIP
display protocol.
4vmware-view://view.mycompany.com/Calculator?action=start-session&appProtocol=BLAST
Horizon Client starts and connects to the view.mycompany.com server. In the login box, the user must
supply the user name, domain name, and password. After a successful login, the client connects to the
application whose display name is displayed as Calculator. The connection uses the VMware Blast
display protocol.
5vmware-view://fred@view.mycompany.com/Finance%20Desktop?domainName=mycompany
Horizon Client starts and connects to the view.mycompany.com server. In the login box, the User name
text box is populated with the name fred, and the Domain text box is populated with mycompany. The
user must supply only a password. After a successful login, the client connects to the desktop whose
display name is displayed as Finance Desktop, and the user is logged in to the guest operating system.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 37
6vmware-view://view.mycompany.com/
Horizon Client starts and the user is taken to the login prompt for connecting to the
view.mycompany.com server.
7vmware-view://view.mycompany.com/Primary%20Desktop?action=reset
Horizon Client starts and connects to the view.mycompany.com server. The login box prompts the user for
a user name, domain name, and password. After a successful login, Horizon Client displays a dialog
box that prompts the user to conrm the reset operation for Primary Desktop. After the reset occurs,
depending on the type of client, the user might see a message that indicates whether the reset was
successful.
N This action is available only if a View administrator has enabled this feature for end users.
8vmware-view://view.mycompany.com/Primary%20Desktop?action=start-
session&connectUSBOnStartup=true
This URI has the same eect as the rst example, and all USB devices connected to the client system are
redirected to the remote desktop.
9vmware-view://
This URI starts Horizon Client if it is not running, or brings Horizon Client to the foreground if it is
running.
10 vmware-view://10.10.10.10/My%20Notepad++?args=%22My%20new%20file.txt%22
Launches My Notepad++ on server 10.10.10.10 and passes the argument My new file.txt in the
application launch command. Spaces and double quotes use percent escaping. The lename is enclosed
in double quotes because it contains spaces.
You can also type this command at the Windows command line prompt by using the following syntax:
vmware-view.exe --serverURL 10.10.10.10 --appName "My Notepad++" --args "\"my new.txt\""
In this example, double quotes are escaped by using the characters \".
11 vmware-view://10.10.10.10/Notepad++%2012?args=a.txt%20b.txt
Launches Notepad++ 12 on server 10.10.10.10 and passes the argument a.text b.txt in the application
launch command. Because the argument is not enclosed in quotes, a space separates the lenames and
the two les are opened separately in Notepad++.
N Applications can dier in the way they use command line arguments. For example, if you pass
the argument a.txt b.txt to Wordpad, Wordpad will open only one le, a.txt.
HTML Code Examples
You can use URIs to make hypertext links and buons to include in emails or on Web pages. The following
examples show how to use the URI from the rst URI example to code a hypertext link that says, Test Link,
and a buon that says, .
<html>
<body>
<a href="vmware-view://view.mycompany.com/Primary%20Desktop?action=start-session">Test
Link</a><br>
<form><input type="button" value="TestButton" onClick="window.location.href=
Using VMware Horizon Client for Windows
38 VMware, Inc.
'vmware-view://view.mycompany.com/Primary%20Desktop?action=start-session'"></form> <br>
</body>
</html>
Configuring Certificate Checking for End Users
Administrators can congure the certicate verication mode so that, for example, full verication is always
performed.
Certicate checking occurs for SSL connections between Connection Server and Horizon Client.
Administrators can congure the verication mode to use one of the following strategies:
nEnd users are allowed to choose the verication mode. The rest of this list describes the three
verication modes.
n(No verication) No certicate checks are performed.
n(Warn) End users are warned if a self-signed certicate is being presented by the server. Users can
choose whether or not to allow this type of connection.
n(Full security) Full verication is performed and connections that do not pass full verication are
rejected.
For details about the types of verication checks performed, see “Seing the Certicate Checking Mode for
Horizon Client,” on page 40.
Use the Client Conguration ADM template le (vdm_client.adm) to set the verication mode. All ADM and
ADMX les that provide group policy seings are available in a .zip le named VMware-Horizon-Extras-
Bundle-x.x.x-yyyyyyy.zip, where x.x.x is the version and yyyyyyy is the build number. You can download
this GPO bundle from the VMware Horizon download site at hp://www.vmware.com/go/downloadview.
For information about using this template to control GPO seings, see “Using the Group Policy Template to
Congure VMware Horizon Client for Windows,” on page 42.
N You can also use the Client Conguration ADM template le to restrict the use of certain
cryptographic algorithms and protocols before establishing an encrypted SSL connection. For more
information about this seing, see“Security Seings for Client GPOs,” on page 44.
If you do not want to congure the certicate verication seing as a group policy, you can also enable
certicate verication by adding the CertCheckMode value name to one of the following registry keys on the
client computer:
nFor 32-bit Windows: HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware VDM\Client\Security
nFor 64-bit Windows: HKLM\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VDM\Client\Security
Use the following values in the registry key:
n0 implements Do not verify server identity certificates.
n1 implements Warn before connecting to untrusted servers.
n2 implements Never connect to untrusted servers.
If you congure both the group policy seing and the CertCheckMode seing in the registry key, the group
policy seing takes precedence over the registry key value.
N In a future release, conguring this seing using the Windows registry might not be supported. A
GPO seing must be used.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 39
Setting the Certificate Checking Mode for Horizon Client
Administrators and sometimes end users can congure whether client connections are rejected if any or
some server certicate checks fail.
Certicate checking occurs for SSL connections between Connection Server and Horizon Client. Certicate
verication includes the following checks:
nHas the certicate been revoked?
nIs the certicate intended for a purpose other than verifying the identity of the sender and encrypting
server communications? That is, is it the correct type of certicate?
nHas the certicate expired, or is it valid only in the future? That is, is the certicate valid according to
the computer clock?
nDoes the common name on the certicate match the host name of the server that sends it? A mismatch
can occur if a load balancer redirects Horizon Client to a server that has a certicate that does not match
the host name entered in Horizon Client. Another reason a mismatch can occur is if you enter an IP
address rather than a host name in the client.
nIs the certicate signed by an unknown or untrusted certicate authority (CA)? Self-signed certicates
are one type of untrusted CA.
To pass this check, the certicate's chain of trust must be rooted in the device's local certicate store.
N For information about distributing a self-signed root certicate to all Windows client systems in a
domain, see "Add the Root Certicate to Trusted Root Certication Authorities" in the View Installation
document.
When you use Horizon Client to log in to a desktop, if your administrator has allowed it, you can click
 SSL to set the certicate checking mode. You have three choices:
nNever connect to untrusted servers. If any of the certicate checks fails, the client cannot connect to the
server. An error message lists the checks that failed.
nWarn before connecting to untrusted servers. If a certicate check fails because the server uses a self-
signed certicate, you can click Continue to ignore the warning. For self-signed certicates, the
certicate name is not required to match the server name you entered in Horizon Client.
You can also receive a warning if the certicate has expired.
nDo not verify server identity . This seing means that no certicate checking occurs.
If the certicate checking mode is set to Warn, you can still connect to a Connection Server instance that uses
a self-signed certicate.
If an administrator later installs a security certicate from a trusted certicate authority, so that all certicate
checks pass when you connect, this trusted connection is remembered for that specic server. In the future,
if that server ever presents a self-signed certicate again, the connection fails. After a particular server
presents a fully veriable certicate, it must always do so.
I If you previously congured your company's client systems to use a specic cipher via GPO,
such as by conguring SSL Cipher Suite Order group policy seings, you must now use a Horizon Client
group policy security seing included in the View ADM template le. See “Security Seings for Client
GPOs,” on page 44. You can alternatively use the SSLCipherList registry seing on the client. See “Using
the Windows Registry to Congure Horizon Client,” on page 60.
Using VMware Horizon Client for Windows
40 VMware, Inc.
Configuring Advanced TLS/SSL Options
You can select the security protocols and cryptographic algorithms that are used to encrypt communications
between Horizon Client and Horizon servers or between Horizon Client and the agent in the remote
desktop.
These security options are also used to encrypt the USB channel (communication between the USB service
daemon and the agent).
With the default seing, cipher suites use 128- or 256-bit AES, remove anonymous DH algorithms, and then
sort the current cipher list in order of encryption algorithm key length.
By default, TLS v1.0, TLS v1.1, and TLS v1.2 are enabled. SSL v2.0 and v3.0 are not supported.
N If TLS v1.0 and RC4 are disabled, USB redirection does not work when users are connected to
Windows XP desktops. Be aware of the security risk if you choose to make this feature work by enabling
TLS v1.0 and RC4.
If you congure a security protocol for Horizon Client that is not enabled on the View server to which the
client connects, a TLS/SSL error occurs and the connection fails.
I At least one of the protocols that you enable in Horizon Client must also be enabled on the
remote desktop. Otherwise, USB devices cannot be redirected to the remote desktop.
On the client system, you can use either a group policy seing or a Windows Registry seing to change the
default ciphers and protocols. For information about using a GPO, see the seing called "Congures SSL
protocols and cryptographic algorithms," in “Security Seings for Client GPOs,” on page 44. For
information about using the SSLCipherList seing in the Windows Registry, see “Using the Windows
Registry to Congure Horizon Client,” on page 60.
Configure Application Reconnection Behavior
When you disconnect from a server, running applications might remain open. You can congure how
running applications behave when you reconnect to the server.
A View administrator can disable the application reconnection behavior seings in Horizon Client from the
command line or by seing a group policy seing. The group policy seing takes precedence over the
command-line seing. For more information, see the -appSessionReconnectionBehavior option in
“Horizon Client Command Usage,” on page 57, or the Disconnected application session resumption
behavior group policy seing in “Scripting Denition Seings for Client GPOs,” on page 42.
Procedure
1 In the desktop and application selector window of Horizon Client, right-click a remote application and
select .
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 41
2 In the Remote Applications pane that appears, select an application reconnection behavior seing.
Option Description
Ask to reconnect to open
applications
Horizon Client noties you that you have one or more remote applications
running when you reconnect to the server. You can click Reconnect to
applications to reopen the application windows, or Not Now to not
reopen the application windows.
Reconnect automatically to open
applications
Application windows for running applications automatically reopen when
you reconnect to the server.
Do not ask to reconnect and do not
automatically reconnect
Horizon Client does not prompt you to reopen running applications and
running application windows do not reopen when you reconnect to the
server.
3 Click OK to save your changes.
The seing takes eect the next time you connect to the server.
Using the Group Policy Template to Configure VMware Horizon Client
for Windows
VMware Horizon Client includes a Group Policy Administrative (ADM) template le for conguring
VMware Horizon Client. You can optimize and secure remote desktop connections by adding the policy
seings in this ADM template le to a new or existing GPO in Active Directory.
The View ADM template le contains both Computer Conguration and User Conguration group policies.
nThe Computer Conguration policies set policies that apply to Horizon Client, regardless of who is
running the client on the host.
nThe User Conguration policies set Horizon Client policies that apply to all users who are running
Horizon Client, as well as RDP connection seings. User Conguration policies override equivalent
Computer Conguration policies.
View applies policies at desktop startup and when users log in.
The Horizon Client Conguration ADM template le (vdm_client.adm) and all ADM and ADMX les that
provide group policy seings are available in a .zip le named VMware-Horizon-Extras-Bundle-x.x.x-
yyyyyyy.zip, where x.x.x is the version and yyyyyyy is the build number. You can download the le from the
VMware Horizon download site at hp://www.vmware.com/go/downloadview. You must copy this le to
your Active Directory server and use the Group Policy Management Editor to add this administrative
template. For instructions, see the topic "Add View ADM Templates to a GPO" in the Seing Up Desktop and
Application Pools in View document.
Scripting Definition Settings for Client GPOs
You can set policies for many of the same seings used when you run VMware Horizon Client from the
command line, including desktop size, name, and domain name, among others.
The following table describes the scripting denition seings in the VMware Horizon Client Conguration
ADM template le. The template provides a Computer Conguration and a User Conguration version of
each scripting denition seing. The User Conguration seing overrides the equivalent Computer
Conguration seing.
Using VMware Horizon Client for Windows
42 VMware, Inc.
Table 3‑4. VMware Horizon Client Configuration Template: Scripting Definitions
Setting Description
Automatically connect if only one
launch item is entitled
(Automatically connects to the desktop if it is the only one entitled for
the usr. This seing spares the user from having to select the desktop
from a list that contains only one desktop.
Connect all USB devices to the
desktop on launch
Determines whether all of the available USB devices on the client system
are connected to the desktop when the desktop is launched.
Connect all USB devices to the
desktop when they are plugged in
Determines whether USB devices are connected to the desktop when
they are plugged in to the client system.
DesktopLayout Species the layout of the VMware Horizon Client window that a user
sees when logging into a remote desktop. The layout choices are as
follows:
nFull Screen
nMultimonitor
nWindow - Large
nWindow - Small
This seing is available only when the DesktopName to select
setting is also set.
DesktopName to select Species the default desktop that VMware Horizon Client uses during
login.
Disable 3rd-party Terminal Services
plugins
Determines whether VMware Horizon Client checks third-party
Terminal Services plugins that are installed as normal RDP plugins. If
you do not congure this seing,VMware Horizon Client checks third-
party plugins by default. This seing does not aect View-specic
plugins, such as USB redirection.
Locked Guest Size Species the screen resolution of the remote desktop if the display is
used on one monitor. That is, this seing does not work if you set the
remote desktop display to All Monitors.
After you enable the seing, remote desktop autot functionality is
disabled. The minimum screen size is 640x480. The maximum screen
size is 4096x4096. This seing applies only to PCoIP connections and
does not apply to RDP connections.
I As a best practice, do not set the resolution higher than the
maximum resolution supported for the remote desktop, which is set in
View Administrator:
nIf 3D is enabled, up to 2 monitors are supported at a resolution of up
to 1920x1200.
nIf 3D is not enabled, up to 4 monitors are supported at a resolution
of up to 2560x1600.
In practice, this client-side seing will be ignored if it is set to a higher
resolution than is possible, given operating system version, amount of
vRAM, and color depth of the remote desktop. For example, if the
resolution for the desktop is set to 1920x1200 in View Administrator, the
resolution shown on the client might not be higher than 1920x1200,
depending on the capabilities of the remote desktop.
Logon DomainName Species the NetBIOS domain that Horizon Client uses during login.
Logon Password Species the password that Horizon Client uses during login. The
password is stored in plain text by Active Directory. For improved
security, it is recommended that you do not specify this seing. Users
can enter the password interactively.
Logon UserName Species the password that Horizon Client uses during login. The
password is stored in plain text by Active Directory.
Server URL Species the URL that Horizon Client uses during login, for example,
https://view1.example.com.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 43
Table 3‑4. VMware Horizon Client Configuration Template: Scripting Definitions (Continued)
Setting Description
Suppress error messages (when fully
scripted only)
Determines whether Horizon Client error messages are hidden during
login.
This seing applies only when the login process is fully scripted, for
example, when all the required login information is prepopulated
through policy.
If the login fails because of incorrect login information, the user is not
notied and the Horizon Client process is terminated.
Disconnected application session
resumption behavior
Determines how running applications behave when users reconnect to a
server. The choices are as follows:
nAsk to reconnect to open applications
nReconnect automatically to open applications
nDo not ask and do not automatically reconnect
When this seing is enabled, end users cannot congure application
reconnection behavior on the Seings page in Horizon Client.
When this seing is disabled, end users can congure application
reconnection behavior in Horizon Client. This seing is disabled by
default.
Security Settings for Client GPOs
Security seings include options regarding security certicate, login credentials, and the single sign-on
feature.
The following table describes the security seings in the Horizon Client Conguration ADM template le.
This table shows whether the seings include both Computer Conguration and User Conguration
seings or Computer Conguration seings only. For the security seings that include both types, the User
Conguration seing overrides the equivalent Computer Conguration seing.
Table 3‑5. Horizon Client Configuration Template: Security Settings
Setting Description
Allow command line credentials
(Computer Conguration seing)
Determines whether user credentials can be provided with Horizon Client
command line options. If this seing is disabled, the smartCardPIN and
password options are not available when users run Horizon Client from the
command line.
This seing is enabled by default.
The equivalent Windows Registry value is AllowCmdLineCredentials.
Servers Trusted For Delegation
(Computer Conguration seing)
Species the View Connection Server instances that accept the user identity and
credential information that is passed when a user selects the Log in as current
user check box. If you do not specify any View Connection Server instances, all
View Connection Server instances accept this information.
To add a View Connection Server instance, use one of the following formats:
ndomain\system$
nsystem$@domain.com
nThe Service Principal Name (SPN) of the View Connection Server service.
The equivalent Windows Registry value is BrokersTrustedForDelegation.
Using VMware Horizon Client for Windows
44 VMware, Inc.
Table 3‑5. Horizon Client Configuration Template: Security Settings (Continued)
Setting Description
Certificate verification mode
(Computer Conguration seing)
Congures the level of certicate checking that is performed by Horizon Client.
You can select one of these modes:
nNo Security. View does not perform certicate checking.
nWarn But Allow. A self-signed certicate is provided by View. In this case,
it is acceptable if the certicate name does not match the View Connection
Server name provided by the user in Horizon Client.
If any other certicate error condition occurs, View displays an error dialog
and prevents the user from connecting to View Connection Server.
Warn But Allow is the default value.
nFull Security. If any type of certicate error occurs, the user cannot
connect to View Connection Server. View displays certicate errors to the
user.
When this group policy seing is congured, users can view the selected
certicate verication mode in Horizon Client but cannot congure the seing.
The SSL conguration dialog box informs users that the administrator has
locked the seing.
When this seing is not congured or disabled, Horizon Client users can select a
certicate verication mode.
To allow a View server to perform checking of certicates provided by
Horizon Client, the client must make HTTPS connections to the View
Connection Server or security server host. Certicate checking is not supported
if you o-load SSL to an intermediate device that makes HTTP connections to
the View Connection Server or security server host.
If you do not want to congure this seing as a group policy, you can also
enable certicate verication by adding the CertCheckMode value name to one
of the following registry keys on the client computer:
nFor 32-bit Windows: HKEY_LOCAL_MACHINE\Software\VMware,
Inc.\VMware VDM\Client\Security
nFor 64-bit Windows: HKLM\SOFTWARE\Wow6432Node\VMware,
Inc.\VMware VDM\Client\Security
Use the following values in the registry key:
n0 implements No Security.
n1 implements Warn But Allow.
n2 implements Full Security.
If you congure both the group policy seing and the CertCheckMode seing in
the Windows Registry key, the group policy seing takes precedence over the
registry key value.
N In a future release, conguring this seing using the Windows registry
might not be supported. A GPO seing must be used.
Default value of the 'Log in
as current user' checkbox
(Computer and User Conguration
seing)
Species the default value of the Log in as current user check box on
theHorizon Client connection dialog box.
This seing overrides the default value specied during Horizon Client
installation.
If a user runs Horizon Client from the command line and species the
logInAsCurrentUser option, that value overrides this seing.
When the Log in as current user check box is selected, the identity and
credential information that the user provided when logging in to the client
system is passed to the View Connection Server instance and ultimately to the
remote desktop. When the check box is deselected, users must provide identity
and credential information multiple times before they can access a remote
desktop.
This seing is disabled by default.
The equivalent Windows Registry value is LogInAsCurrentUser.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 45
Table 3‑5. Horizon Client Configuration Template: Security Settings (Continued)
Setting Description
Display option to Log in as
current user
(Computer and User Conguration
seing)
Determines whether the Log in as current user check box is visible on the
Horizon Client connection dialog box.
When the check box is visible, users can select or deselect it and override its
default value. When the check box is hidden, users cannot override its default
value from the Horizon Client connection dialog box.
You can specify the default value for the Log in as current user check box by
using the policy seing Default value of the 'Log in as current user'
checkbox.
This seing is enabled by default.
The equivalent Windows Registry value is LogInAsCurrentUser_Display.
Enable jump list integration
(Computer Conguration seing)
Determines whether a jump list appears in the Horizon Client icon on the
taskbar of Windows 7 and later systems. The jump list lets users connect to
recent View Connection Server instances and remote desktops.
If Horizon Client is shared, you might not want users to see the names of recent
desktops. You can disable the jump list by disabling this seing.
This seing is enabled by default.
The equivalent Windows Registry value is EnableJumplist.
Enable SSL encrypted framework
channel
(Computer and User Conguration
seing)
Determines whether SSL is enabled for View 5.0 and earlier desktops. Before
View 5.0, the data sent over port TCP 32111 to the desktop was not encrypted.
nEnable: Enables SSL, but allows fallback to the previous unencrypted
connection if the remote desktop does not have SSL support. For example,
View 5.0 and earlier desktops do not have SSL support. Enable is the
default seing.
nDisable: Disables SSL. This seing is not recommended but might be useful
for debugging or if the channel is not being tunneled and could potentially
then be optimized by a WAN accelerator product.
nEnforce: Enables SSL, and refuses to connect to desktops with no SSL
support .
The equivalent Windows Registry value is EnableTicketSSLAuth.
Configures SSL protocols and
cryptographic algorithms
(Computer and User Conguration
seing)
Congures the cipher list to restrict the use of certain cryptographic algorithms
and protocols before establishing an encrypted SSL connection. The cipher list
consists of one or more cipher strings separated by colons.
N The cipher string is case-sensitive.
The default value is TLSv1:TLSv1.1:TLSv1.2:!aNULL:kECDH
+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA
+AES.
That means that TLS v1, TLS v1.1 and TLS v1.2 are enabled. (SSL v2.0 and v3.0
are removed.)
Cipher suites use 128- or 256-bit AES, remove anonymous DH algorithms, and
then sort the current cipher list in order of encryption algorithm key length.
Reference link for the conguration:
hp://www.openssl.org/docs/apps/ciphers.html
The equivalent Windows Registry value is SSLCipherList.
Enable Single Sign-On for
smart card authentication
(Computer Conguration seing)
Determines whether single sign-on is enabled for smart card authentication.
When single sign-on is enabled, Horizon Client stores the encrypted smart card
PIN in temporary memory before submiing it to View Connection Server.
When single sign-on is disabled, Horizon Client does not display a custom PIN
dialog.
The equivalent Windows Registry value is EnableSmartCardSSO.
Ignore bad SSL certificate
date received from the server
(Computer Conguration seing)
(View 4.6 and earlier releases only) Determines whether errors that are
associated with invalid server certicate dates are ignored. These errors occur
when a server sends a certicate with a date that has passed.
The equivalent Windows Registry value is IgnoreCertDateInvalid.
Using VMware Horizon Client for Windows
46 VMware, Inc.
Table 3‑5. Horizon Client Configuration Template: Security Settings (Continued)
Setting Description
Ignore certificate revocation
problems
(Computer Conguration seing)
(View 4.6 and earlier releases only) Determines whether errors that are
associated with a revoked server certicate are ignored. These errors occur
when the server sends a certicate that has been revoked and when the client
cannot verify a certicate's revocation status.
This seing is disabled by default.
The equivalent Windows Registry value is IgnoreRevocation.
Ignore incorrect SSL
certificate common name (host
name field)
(Computer Conguration seing)
(View 4.6 and earlier releases only) Determines whether errors that are
associated with incorrect server certicate common names are ignored. These
errors occur when the common name on the certicate does not match the
hostname of the server that sends it.
The equivalent Windows Registry value is IgnoreCertCnInvalid.
Ignore incorrect usage
problems
(Computer Conguration seing)
(View 4.6 and earlier releases only) Determines whether errors that are
associated with incorrect usage of a server certicate are ignored. These errors
occur when the server sends a certicate that is intended for a purpose other
than verifying the identity of the sender and encrypting server communications.
The equivalent Windows Registry value is IgnoreWrongUsage.
Ignore unknown certificate
authority problems
(Computer Conguration seing)
(View 4.6 and earlier releases only) Determines whether errors that are
associated with an unknown Certicate Authority (CA) on the server certicate
are ignored. These errors occur when the server sends a certicate that is signed
by an untrusted third-party CA.
The equivalent Windows Registry value is IgnoreUnknownCa.
RDP Settings for Client GPOs
You can set group policies for options such as redirection of such things as audio, printers, ports, and other
devices when you use the Microsoft RDP display protocol.
The following table describes the Remote Desktop Protocol (RDP) seings in the Horizon Client
Conguration ADM template le. All RDP seings are User Conguration seings.
Table 3‑6. Horizon Client Configuration Administrative Template: RDP Settings
Setting Description
Audio redirection Determines whether audio information played on the remote desktop is redirected.
Select one of the following seings:
nDisable Audio: Audio is disabled.
nPlay in VM (needed for VoIP USB Support): Audio plays within the remote
desktop. This seing requires a shared USB audio device to provide sound on
the client.
nRedirect to client: Audio is redirected to the client. This is the default mode.
This seing applies only to RDP audio. Audio that is redirected through MMR
plays in the client.
Enable audio capture
redirection
Determines whether the default audio input device is redirected from the client to
the remote session. When this seing is enabled, the audio recording device on the
client appears in the remote desktop and can record audio input.
The default seing is disabled.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 47
Table 3‑6. Horizon Client Configuration Administrative Template: RDP Settings (Continued)
Setting Description
Bitmap cache file size in
unit for number bpp bitmaps
Species the size of the bitmap cache, in kilobytes or megabytes, to use for specic
bits per pixel (bpp) bitmap color seings.
Separate versions of this seing are provided for the following unit and bpp
combinations:
nKB/8bpp
nMB/8bpp
nMB/16bpp
nMB/24bpp
nMB/32bpp
Bitmap caching/cache
persistence active
Determines whether persistent bitmap caching is used (active). Persistent bitmap
caching can improve performance, but it requires additional disk space.
Color depth Species the color depth of the remote desktop. Select one of the available seings:
n8 bit
n15 bit
n16 bit
n24 bit
n32 bit
For 24-bit Windows XP systems, you must enable the Limit Maximum Color Depth
policy in Computer  > Administrative Templates > Windows
Components > Terminal Services and set it to 24 bits.
Cursor shadow Determines whether a shadow appears under the cursor on the remote desktop.
Desktop background Determines whether the desktop background appears when clients connect to a
remote desktop.
Desktop composition (Windows Vista or later) Determines whether desktop composition is enabled on
the remote desktop.
When desktop composition is enabled, individual windows no longer draw
directly to the screen or primary display device as they did in previous versions of
Microsoft Windows. Instead, drawing is redirected to o-screen surfaces in video
memory, which are then rendered into a desktop image and presented on the
display.
Enable compression Determines whether RDP data is compressed. This seing is enabled by default.
Enable RDP Auto-Reconnect Determines whether the RDP client component aempts to reconnect to a remote
desktop after an RDP protocol connection failure. This seing has no eect if the
Use secure tunnel connection to desktop option is enabled in View Administrator.
This seing is disabled by default.
Font smoothing (Windows Vista or later) Determines whether anti-aliasing is applied to the fonts
on the remote desktop.
Menu and window animation Determines whether animation for menus and windows is enabled when clients
connect to a remote desktop.
Redirect clipboard Determines whether the local clipboard information is redirected when clients
connect to the remote desktop.
Redirect drives Determines whether local disk drives are redirected when clients connect to the
remote desktop. By default, local drives are redirected.
Enabling this seing, or leaving it uncongured, allows data on the redirected
drive on the remote desktop to be copied to the drive on the client computer.
Disable this seing if allowing data to pass from the remote desktop to users' client
computers represents a potential security risk in your deployment. Another
approach is to disable folder redirection in the remote desktop virtual machine by
enabling the Microsoft Windows group policy seing, Do not allow drive
redirection.
The Redirect drives seing applies to RDP only.
Using VMware Horizon Client for Windows
48 VMware, Inc.
Table 3‑6. Horizon Client Configuration Administrative Template: RDP Settings (Continued)
Setting Description
Redirect printers Determines whether local printers are redirected when clients connect to the
remote desktop.
Redirect serial ports Determines whether local COM ports are redirected when clients connect to the
remote desktop.
Redirect smart cards Determines whether local smart cards are redirected when clients connect to the
remote desktop.
N This seing applies to both RDP and PCoIP connections.
Redirect supported plug-and-
play devices
Determines whether local plug-and-play and point-of-sale devices are redirected
when clients connect to the remote desktop. This behavior is dierent from the
redirection that is managed by the USB Redirection component of the agent.
Shadow bitmaps Determines whether bitmaps are shadowed. This seing has no eect in full-screen
mode.
Show contents of window
while dragging
Determines whether the folder contents appear when users drag a folder to a new
location.
Themes Determines whether themes appear when clients connect to a remote desktop.
Windows key combination
redirection
Determines where Windows key combinations are applied.
This seing lets you send key combinations to the remote virtual machine or apply
key combinations locally.
If this seing is not congured, key combinations are applied locally.
General Settings for Client GPOs
Seings include proxy options, time zone forwarding, multimedia acceleration, and other display seings.
General Settings
The following table describes the general seings in the Horizon Client Conguration ADM template le.
General seings include both Computer Conguration and User Conguration seings. The User
Conguration seing overrides the equivalent Computer Conguration seing.
Table 3‑7. Horizon Client Configuration Template: General Settings
Setting Description
Always on top
(User Conguration seing)
Determines whether the Horizon Client window is always the topmost window.
Enabling this seing prevents the Windows taskbar from obscuring a full-screen
Horizon Client window. This seing is disabled by default.
Default value of the "Hide
the selector after launching
an item" check box
(Computer and User Conguration
seing)
Sets whether the Hide the selector after launching an item check box is selected
by default.
This seing is disabled by default.
Determines if the VMware View
Client should use proxy.pac
file
(Computer Conguration seing)
(View 4.6 and earlier releases only) Determines whether Horizon Client uses a
Proxy Auto Cong (PAC) le. Enabling this seing causes Horizon Client to use a
PAC le.
A PAC le (commonly called proxy.pac) helps Web browsers and other user
agents nd the appropriate proxy server for a particular URL or Web site request.
If you enable this seing on a multi-core machine, the WinINet application that
Horizon Client uses to nd the proxy server information might crash. Disable this
seing if this problem occurs on your machine.
This seing is disabled by default.
N This seing applies to direct connections only. It does not aect tunnel
connections.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 49
Table 3‑7. Horizon Client Configuration Template: General Settings (Continued)
Setting Description
Disable time zone forwarding
(Computer Conguration seing)
Determines whether time zone synchronization between the remote desktop and
the connected client is disabled.
Disable toast notifications
(Computer and User Conguration
seing)
Determines whether to disable toast notications from Horizon Client.
Enable this seing if you do not want the user to see toast notications in the
corner of the screen.
N If you enable this seing, the user does not see a 5-minute warning when
the Session Timeout function is active.
Disallow passing through
client information in a
nested session
(Computer Conguration seing)
Species whether Horizon Client should be prevented from passing through
client information in a nested session. When enabled, if Horizon Client is running
inside of a Horizon session, it will send the actual physical client information
instead of the VM device information. This seing applies to the following pieces
of client information: device name and domain, client type, IP address, and MAC
address. This seing is disabled by default, which means passing through client
information in a nested session is allowed.
Don't check monitor alignment
on spanning
(User Conguration seing)
By default, the client desktop does not span multiple monitors if the screens do
not form an exact rectangle when they are combined. Enable this seing to
override the default. This seing is disabled by default.
Enable multi-media
acceleration
(User Conguration seing)
Determines whether multimedia redirection (MMR) is enabled on the client.
MMR does not work correctly if the Horizon Client video display hardware does
not have overlay support.
Enable relative mouse
(Computer and User Conguration
seing)
(View 5.2 and later releases only) Enables the relative mouse when using the
PCoIP display protocol. Relative mouse mode improves mouse behavior for
certain graphics applications and games. If the remote desktop does not support
relative mouse then this seing will not be used. This seing is disabled by
default.
Enable the shade
(User Conguration seing)
Determines whether the shade menu bar at the top of the Horizon Client window
is visible. This seing is enabled by default.
N The shade menu bar is disabled by default for kiosk mode.
Enable Horizon Client online
update
(Computer Conguration seing)
Enables the online upgrade feature. This seing is disabled by default.
Tunnel proxy bypass address
list
(Computer Conguration seing)
Species a list of tunnel addresses. The proxy server is not used for these
addresses. Use a semicolon (;) to separate multiple entries.
URL for View Client online
help
(Computer Conguration seing)
Species an alternate URL from which Horizon Client can retrieve help pages.
This seing is intended for use in environments that cannot retrieve the remotely-
hosted help system because they do not have internet access.
URL for Horizon Client online
update
(Computer Conguration seing)
Species an alternate URL from which Horizon Client can retrieve updates. This
seing is intended for use in an environment that denes its own private/personal
update center. If it is not enabled, the VMware ocial update server will be used.
Pin the shade
(User Conguration seing)
Determines whether the pin on the shade at the top of the Horizon Client window
is enabled and auto-hiding of the menu bar does not occur. This seing has no
eect if the shade is disabled. This seing is enabled by default.
Using VMware Horizon Client for Windows
50 VMware, Inc.
Table 3‑7. Horizon Client Configuration Template: General Settings (Continued)
Setting Description
Disable desktop disconnect
messages
(Computer and User Conguration
seing)
Species whether messages that are normally shown upon desktop disconnection
should be disabled. These messages are shown by default.
Disable sharing files and
folders
(User Conguration seing)
Species whether client drive redirection functionality is available in
Horizon Client.
When this seing is set to Enabled, all client drive redirection functionality is
disabled in Horizon Client, including the ability to open local les with remote
applications. In addition, the following elements are hidden in the Horizon Client
user interface:
nSharing panel in the Seings dialog box
nShare Folders item in the Option menu in a remote desktop
nSharing item for Horizon Client in the system tray
nSharing dialog box that appears the rst time you connect to a remote
desktop or application after you connect to a server
When this seing is set to Disabled, the client drive redirection feature is fully
functional. If this seing is not congured, the default value is Disabled. This
seing is not congured by default.
USB Settings for Client GPOs
You can dene USB policy seings for both the agent and Horizon Client for Windows. On connection,
Horizon Client downloads the USB policy seings from the agent and uses them in conjunction with the
Horizon Client USB policy seings to decide which devices it will allow to be available for redirection from
the host machine.
The following table describes each policy seing for spliing composite USB in the Horizon Client
Conguration ADM template le. The seings apply at computer level. Horizon Client preferentially reads
the seings from the GPO at computer level, and otherwise from the registry at
HKLM\Software\Policies\VMware, Inc.\VMware VDM\Client\USB. For a description of how View applies the
policies for spliing composite USB devices, see the topics about using policies to control USB redirection, in
the Seing Up Desktop and Application Pools in View document.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 51
Table 3‑8. Horizon Client Configuration Template: USB Splitting Settings
Setting Properties
Allow Auto Device
Splitting
Allow the automatic spliing of composite USB devices.
The default value is undened, which equates to false.
Exclude Vid/Pid Device
From Split
Excludes a composite USB device specied by vendor and product IDs from spliing. The
format of the seing is vid-xxx1_pid-yyy2[;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.
For example: vid-0781_pid-55**
The default value is undened.
Split Vid/Pid Device Treats the components of a composite USB device specied by vendor and product IDs as
separate devices. The format of the seing 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.
For example: vid-0781_pid-554c(exintf:01;exintf:02)
N View does not automatically include the components that you have not explicitly
excluded. You must specify a lter policy such as Include Vid/Pid Device to include
those components.
The default value is undened.
The following table describes each policy seing for ltering USB devices in the Horizon Client
Conguration ADM template le. The seings apply at computer level. Horizon Client preferentially reads
the seings from the GPO at computer level, and otherwise from the registry at
HKLM\Software\Policies\VMware, Inc.\VMware VDM\Client\USB. For a description of how View applies the
policies for ltering USB devices, see the topics about conguring lter policy seings for USB redirection,
in the Seing Up Desktop and Application Pools in View document.
Table 3‑9. Horizon Client Configuration Template: USB Filtering Settings
Setting Properties
Allow Audio Input
Devices
Allows audio input devices to be redirected.
The default value is undened, which equates to true.
Allow Audio Output
Devices
Allows audio output devices to be redirected.
The default value is undened, which equates to false.
Allow HIDBootable Allows input devices other than keyboards or mice that are available at boot time (also
known as hid-bootable devices) to be redirected.
The default value is undened, which equates to true.
Allow Device
Descriptor Failsafe
Behavior
Allows devices to be redirected even if the Horizon Client fails to get the cong/device
descriptors.
To allow a device even if it fails the cong/desc, include it in the Include lters, such
IncludeVidPid or IncludePath.
The default value is undened, which equates to false.
Allow Other Input
Devices
Allows input devices other than hid-bootable devices or keyboards with integrated
pointing devices to be redirected.
The default value is undened, which equates to true.
Allow Keyboard and
Mouse Devices
Allows keyboards with integrated pointing devices (such as a mouse, trackball, or touch
pad) to be redirected.
The default value is undened, which equates to false.
Allow Smart Cards Allows smart-card devices to be redirected.
The default value is undened, which equates to false.
Using VMware Horizon Client for Windows
52 VMware, Inc.
Table 3‑9. Horizon Client Configuration Template: USB Filtering Settings (Continued)
Setting Properties
Allow Video Devices Allows video devices to be redirected.
The default value is undened, which equates to true.
Disable Remote
Configuration
Disables the use of agent seings when performing USB device ltering.
The default value is undened, which equates to false.
Exclude All Devices Excludes all USB devices from being redirected. If set to true, you can use other policy
seings to allow specic devices or families of devices to be redirected. If set to false, you
can use other policy seings to prevent specic devices or families of devices from being
redirected.
If you set the value of Exclude All Devices to true on the agent, and this seing is
passed to Horizon Client, the agent seing overrides the Horizon Client seing.
The default value is undened, which equates to false.
Exclude Device Family Excludes families of devices from being redirected. The format of the seing is
family_name_1[;family_name_2]...
For example: bluetooth;smart-card
If you have enabled automatic device spliing, View 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 spliing, View examines the device family of the whole
composite USB device.
The default value is undened.
Exclude Vid/Pid Device Excludes devices with specied vendor and product IDs from being redirected. The format
of the seing is vid-xxx1_pid-yyy2[;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.
For example: vid-0781_pid-****;vid-0561_pid-554c
The default value is undened.
Exclude Path Exclude devices at specied hub or port paths from being redirected. The format of the
seing is bus-x1[/y1].../port-z1[;bus-x2[/y2].../port-z2]...
You must specify bus and port numbers in hexadecimal. You cannot use the wildcard
character in paths.
For example: bus-1/2/3_port-02;bus-1/1/1/4_port-ff
The default value is undened.
Include Device Family Includes families of devices that can be redirected. The format of the seing is
family_name_1[;family_name_2]...
For example: storage
The default value is undened.
Include Path Include devices at a specied hub or port paths that can be redirected. The format of the
seing is bus-x1[/y1].../port-z1[;bus-x2[/y2].../port-z2]...
You must specify bus and port numbers in hexadecimal. You cannot use the wildcard
character in paths.
For example: bus-1/2_port-02;bus-1/7/1/4_port-0f
The default value is undened.
Include Vid/Pid Device Includes devices with specied vendor and product IDs that can be redirected. The format
of the seing is vid-xxx1_pid-yyy2[;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.
For example: vid-0561_pid-554c
The default value is undened.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 53
View PCoIP Client Session Variables ADM Template Settings
The View PCoIP Client Session Variables ADM template le (pcoip.client.adm) contains policy seings
related to the PCoIP display protocol. You can congure seings to default values that can be overridden by
an administrator, or you can congure seings to values that cannot be overridden.
This ADM le is available in a bundled .zip le named VMware-Horizon-Extras-Bundle-x.x.x-yyyyyyy.zip,
which you can download from the VMware download site at
hps://my.vmware.com/web/vmware/downloads. Under Desktop & End-User Computing, select the
VMware Horizon 7 download, which includes the bundled .zip le.
Table 3‑10. View PCoIP Client Session Variables
Setting Description
Configure PCoIP
client image cache
size policy
Controls the size of the PCoIP client image cache. The client uses image caching to store
portions of the display that were previously transmied. Image caching reduces the amount
of data that is retransmied.
When this seing is not congured or when it is disabled, PCoIP uses a default client image
cache size of 250MB.
When you enable this seing, you can congure a client image cache size from a minimum
of 50 MB to a maximum of 300 MB. The default value is 250MB.
Configure PCoIP event
log verbosity
Sets the PCoIP event log verbosity. The values range from 0 (least verbose) to 3 (most
verbose).
When this seing is enabled, you can set the verbosity level from 0 to 3. When the seing is
not congured or disabled, the default event log verbosity level is 2.
When this seing is modied during an active PCoIP session, the new seing takes eect
immediately.
Configure PCoIP
session encryption
algorithms
Controls the encryption algorithms advertised by the PCoIP endpoint during session
negotiation.
Checking one of the check boxes disables the associated encryption algorithm. You must
enable at least one algorithm.
This seing applies to both agent and client. The endpoints negotiate the actual session
encryption algorithm that is used. If FIPS140-2 approved mode is enabled, the Disable
AES-128-GCM encryption value will be overridden if both AES-128-GCM encryption and
AES-256-GCM encryption are disabled.
If the Configure SSL Connections seing is disabled or not congured, both the
Salsa20-256round12 and AES-128-GCM algorithms are available for negotiation by this
endpoint.
Supported encryption algorithms, in order of preference, are SALSA20/12-256, AES-
GCM-128, and AES-GCM-256. By default, all supported encryption algorithms are available
for negotiation by this endpoint.
Using VMware Horizon Client for Windows
54 VMware, Inc.
Table 3‑10. View PCoIP Client Session Variables (Continued)
Setting Description
Configure PCoIP
virtual channels
Species the virtual channels that can and cannot operate over PCoIP sessions. This seing
also determines whether to disable clipboard processing on the PCoIP host.
Virtual channels that are used in PCoIP sessions must appear on the virtual channel
authorization list. Virtual channels that appear in the unauthorized virtual channel list
cannot be used in PCoIP sessions.
You can specify a maximum of 15 virtual channels for use in PCoIP sessions.
Separate multiple channel names with the vertical bar (|) character. For example, the virtual
channel authorization string to allow the mksvchan and vdp_rdpvcbridge virtual channels
is mksvchan|vdp_rdpvcbridge.
If a channel name contains the vertical bar or backslash (\) character, insert a backslash
character before it. For example, type the channel name awk|ward\channel as
awk\|ward\\channel.
When the authorized virtual channel list is empty, all virtual channels are disallowed. When
the unauthorized virtual channel list is empty, all virtual channels are allowed.
The virtual channels seing applies to both agent and client. Virtual channels must be
enabled on both agent and client for virtual channels to be used.
The virtual channels seing provides a separate check box that allows you to disable remote
clipboard processing on the PCoIP host. This value applies to the agent only.
By default, all virtual channels are enabled, including clipboard processing.
Configure the Client
PCoIP UDP port
Species the UDP client port that is used by software PCoIP clients. The UDP port value
species the base UDP port to use. The UDP port range value determines how many
additional ports to try if the base port is not available.
The range spans from the base port to the sum of the base port and port range. For example,
if the base port is 50002 and the port range is 64, the range spans from 50002 to 50066.
This seing applies to the client only.
By default, the base port is 50002 and the port range is 64.
Configure the maximum
PCoIP session
bandwidth
Species the maximum bandwidth, in kilobits per second, in a PCoIP session. The
bandwidth includes all imaging, audio, virtual channel, USB, and control PCoIP trac.
Set this value to the overall capacity of the link to which your endpoint is connected, taking
into consideration the number of expected concurrent PCoIP sessions. For example, with a
single-user VDI conguration (a single PCoIP session) that connects through a 4Mbit/s
Internet connection, set this value to 4Mbit, or 10% less than this value to leave some
allowance for other network trac. When you expect multiple concurrent PCoIP sessions to
share a link, comprising either multiple VDI users or an RDS conguration, you might want
to adjust the seing accordingly. However, lowering this value will restrict the maximum
bandwidth for each active session.
Seing this value prevents the agent from aempting to transmit at a higher rate than the
link capacity, which would cause excessive packet loss and a poorer user experience. This
value is symmetric. It forces the client and agent to use the lower of the two values that are
set on the client and agent side. For example, seing a 4Mbit/s maximum bandwidth forces
the agent to transmit at a lower rate, even though the seing is congured on the client.
When this seing is disabled or not congured on an endpoint, the endpoint imposes no
bandwidth constraints. When this seing is congured, the seing is used as the endpoint's
maximum bandwidth constraint in kilobits per second.
The default value when this seing is not congured is 900000 kilobits per second.
This seing applies to the agent and the client. If the two endpoints have dierent seings,
the lower value is used.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 55
Table 3‑10. View PCoIP Client Session Variables (Continued)
Setting Description
Configure the PCoIP
transport header
Congures the PCoIP transport header and sets the transport session priority.
The PCoIP transport header is a 32-bit header that is added to all PCoIP UDP packets (only
if the transport header is enabled and supported by both sides). The PCoIP transport header
allows network devices to make beer prioritization/QoS decisions when dealing with
network congestion. The transport header is enabled by default.
The transport session priority determines the PCoIP session priority reported in the PCoIP
transport header. Network devices make beer prioritization/QoS decisions based on the
specied transport session priority.
When the Configure the PCoIP transport header seing is enabled, the following
transport session priorities are available:
nHigh
nMedium (default value)
nLow
n
The transport session priority value is negotiated by the PCoIP agent and client. If the PCoIP
agent species a transport session priority value, the session uses the agent-specied session
priority. If only the client has specied a transport session priority, the session uses the
client-specied session priority. If neither agent nor client has specied a transport session
priority, or  Priority is specied, the session uses the default value, Medium
priority.
Enable/disable audio
in the PCoIP session
Determines whether audio is enabled in PCoIP sessions. Both endpoints must have audio
enabled. When this seing is enabled, PCoIP audio is allowed. When it is disabled, PCoIP
audio is disabled. When this seing is not congured, audio is enabled by default.
Configure the PCoIP
session bandwidth
floor
Species a lower limit, in kilobits per second, for the bandwidth that is reserved by the
PCoIP session.
This seing congures the minimum expected bandwidth transmission rate for the
endpoint. When you use this seing to reserve bandwidth for an endpoint, the user does not
have to wait for bandwidth to become available, which improves session responsiveness.
Make sure that you do not over-subscribe the total reserved bandwidth for all endpoints.
Make sure that the sum of bandwidth oors for all connections in your conguration does
not exceed the network capability.
The default value is 0, which means that no minimum bandwidth is reserved. When this
seing is disabled or not congured, no minimum bandwidth is reserved.
This seing applies to the agent and the client, but the seing only aects the endpoint on
which it is congured.
When this seing is modied during an active PCoIP session, the change takes eect
immediately.
Configure the PCoIP
session MTU
Species the Maximum Transmission Unit (MTU) size for UDP packets for a PCoIP session.
The MTU size includes IP and UDP packet headers. TCP uses the standard MTU discovery
mechanism to set MTU and is not aected by this seing.
The maximum MTU size is 1500 bytes. The minimum MTU size is 500 bytes. The default
value is 1300 bytes.
Typically, you do not have to change the MTU size. Change this value if you have an
unusual network setup that causes PCoIP packet fragmentation.
This seing applies to the agent and the client. If the two endpoints have dierent MTU size
seings, the lowest size is used.
If this seing is disabled or not congured, the client uses the default value in the
negotiation with the agent.
Using VMware Horizon Client for Windows
56 VMware, Inc.
Running Horizon Client from the Command Line
You can run Horizon Client for Windows from the command line or from scripts. You might want to do this
if you are implementing a kiosk-based application that grants end users access to desktop applications.
You use the vmware-view.exe command to run the Horizon Client for Windows from the command line. The
command includes options that you can specify to change the behavior of Horizon Client.
Horizon Client Command Usage
The syntax of the vmware-view command controls the operation of Horizon Client.
Use the following form of the vmware-view command from a Windows command prompt.
vmware-view [command_line_option [argument]] ...
The default path to the vmware-view command executable le depends on your system.
nOn 32-bit systems, the path is C:\Program Files\VMware\VMware Horizon View Client\.
nOn 64-bit systems, the path is C:\Program Files (x86)\VMware\VMware Horizon View Client\.
For your convenience, add this path to your PATH environment variable.
The following table shows the command-line options that you can use with the vmware-view command.
Table 3‑11. Horizon Client Command-Line Options
Option Description
/? Displays the list of command options.
-appName application_name Species the name of the application as it would appear in the desktop and
application selection window. This is the display name that was specied for
the application pool in the pool creation wizard.
-appSessionReconnectionBehavior
argument
Species the application reconnection behavior seing.
nalways implements Reconnect automatically to open applications
nnever implements Do not ask to reconnect and do not automatically
reconnect
nask implements Ask to reconnect to open applications
When you use this option, the application reconnection seings are disabled
on the Seings page in Horizon Client.
-args argument Species command-line arguments to add to remote application launch. For
example: vmware-view.exe --serverURL 10.10.10.10 --appName "My
Notepad++" --args "\"my new.txt\""
-connectUSBOnStartup When set to true, redirects all USB devices to the desktop that are currently
connected to the host. This option is implicitly set if you specify the
-unattended option. The default is false.
-connectUSBOnInsert When set to true, connects a USB device to the foreground desktop when
you plug in the device. This option is implicitly set if you specify the
-unattended option. The default is false.
-desktopLayout window_size Species how to display the window for the desktop:
fullscreen Full-screen display.
multimonitor Multiple-monitor display.
windowLarge Large window.
windowSmall Small window.
length X width Custom size. For example: 800 X 600
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 57
Table 3‑11. Horizon Client Command-Line Options (Continued)
Option Description
-desktopName desktop_name Species the name of the desktop as it would appear in the desktop and
application selection window. This is the display name that was specied for
the pool in the pool creation wizard.
I Do not specify this option for clients in kiosk mode. This option
has no eect when in the desktop is run in kiosk mode. For kiosk mode, the
connection is made to the rst desktop in the list of entitled desktops.
-desktopProtocol protocol Species the display protocol to use as it would appear in the desktop and
application selection window. The display protocol can be Blast, PCoIP, or
RDP.
-domainName domain_name Species the NETBIOS domain that the end user uses to log in to
Horizon Client. For example, you would use mycompany rather than
mycompany.com.
-file le_path Species the path of a conguration le that contains additional command
options and arguments. See “Horizon Client Conguration File,” on page 60.
-h Shows help options.
-hideClientAfterLaunchSession When set to true, hides the remote desktop and application selector window
and the Show VMware Horizon Client menu after launching a remote
session. When set to false, shows the remote desktop and application
selector window and the Show VMware Horizon Client menu after
launching a remote session. The default is true.
-languageId Locale_ID Provides localization support for dierent languages in Horizon Client. If a
resource library is available, specify the Locale ID (LCID) to use. For US
English, enter the value 0x409.
-listMonitors Lists index values and display layout information for the connected monitors.
For example:
1: (0, 0, 1920, 1200)
2: (1920, 0, 3840, 1200)
3: (-900, -410, 0, 1190)
You can use the index values in the -monitors option.
-logInAsCurrentUser When set to true, uses the credential information that the end user provides
when logging in to the client system to log in to the View Connection Server
instance and ultimately to the View desktop. The default is false.
-monitors "n[,n,n,n]" Species monitors to use in a multiple-monitor setup, where n is the index
value of a monitor. You can use the -listMonitors option to determine the
index values of the connected monitors. You can specify up to four index
values, separated by commas. For example: -monitors "1,2"
This option has no eect unless -desktopLayout is set to multimonitor.
-nonInteractive Suppresses error message boxes when starting Horizon Client from a script.
This option is implicitly set if you specify the -unattended option.
-noVMwareAddins Prevents loading of VMware-specic virtual channels such virtual printing.
-password password Species the password that the end user uses to log in to Horizon Client. The
password is processed in plain text by the command console or any scripting
tool. You do not need to specify this option for clients in kiosk mode if you
generate the password automatically. For improved security, it is
recommended that you do not specify this option. Users can enter the
password interactively.
-printEnvironmentInfo Displays the IP address, MAC address, and machine name of the client
device.
-serverURL connection_server Species the URL, IP address, or FQDN of the View Connection Server
instance.
-shutdown Shuts down all desktops and applications and relevant UI components.
Using VMware Horizon Client for Windows
58 VMware, Inc.
Table 3‑11. Horizon Client Command-Line Options (Continued)
Option Description
-singleAutoConnect Species that if the user is entitled to only one remote desktop or application,
after the user authenticates to the server, the desktop or application is
automatically connected and the user is logged in. This seing spares the user
from having to select the desktop or application from a list that contains only
one item.
-smartCardPIN PIN Species the PIN when an end user inserts a smart card to login.
-usernameHint user_name Species the account name to use as the username hint.
-standalone Supported for backwards compatibility purposes. This is the default behavior
for this client. Specifying -standalone is not necessary. Launches a second
instance of the Horizon Client that can connect to the same or a dierent
View Connection Server.
For multiple desktop connections to the same server or to a dierent server,
using the secure tunnel is supported.
N The second desktop connection might not have access to local
hardware, such as USB devices, smart, cards, printers, and multiple monitors.
-supportText le_name Species the full path of a text le. The content of the le is displayed in the
Support Information dialog.
-unattended Runs Horizon Client in a noninteractive mode that is suitable for clients in
kiosk mode. You must also specify:
nThe account name of the client, if you did not generate the account name
from the MAC address of the client device. The name must begin with
the string “custom-” or an alternate prex that you have congured in
ADAM.
nThe password of the client, if you did not generate a password
automatically when you set up the account for the client.
The -unattended option implicitly sets the -nonInteractive,
-connectUSBOnStartup, -connectUSBOnInsert , and
-desktopLayout multimonitoroptions.
-useExisting Enables you to launch multiple remote desktops and applications from a
single Horizon Client session.
When you specify this option, Horizon Client determines whether a session
with the same username, domain, and server URL already exists and, if it
does, reuses that session instead of creating a new session.
For example, in the following command, user-1 launches the Calculator
application and a new session is created.
vmware-view.exe -userName user-1 -password secret
-domainName domain -appName Calculator
-serverURL view.mycompany.com -useExisting
In the next command, user1 launches the Paint application with the same
username, domain, and server URL, and the same session is used.
vmware-view.exe -userName user-1 -password secret
-domainName domain -appName Paint
-serverURL view.mycompany.com -useExisting
-userName user_name Species the account name that the end user uses to log in to Horizon Client.
You do not need to specify this option for clients in kiosk mode if you
generate the account name from the MAC address of the client device.
You can specify all options by Active Directory group policies except for -file, -languageId,
-printEnvironmentInfo, -smartCardPIN, and -unattended.
N Group policy seings take precedence over seings that you specify in the command line.
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 59
Horizon Client Configuration File
You can read command-line options for Horizon Client from a conguration le.
You can specify the path of the conguration le as an argument to the -file le_path option of the vmware-
view command. The le must be a Unicode (UTF-16) or ASCII text le.
Example: Example of a Configuration File for a Noninteractive Application
The following example shows the contents of a conguration le for a noninteractive application.
-serverURL https://view.yourcompany.com
-userName autouser
-password auto123
-domainName companydomain
-desktopName autodesktop
-nonInteractive
Example: Example of a Configuration File for a Client in Kiosk Mode
The following example shows a client in kiosk mode whose account name is based on its MAC address. The
client has an automatically generated password.
-serverURL 145.124.24.100
-unattended
Using the Windows Registry to Configure Horizon Client
You can dene default seings for the Horizon Client in the Windows Registry instead of specifying these
seings on the command line. Group policy seings take precedence over Windows Registry seings, and
Windows Registry seings take precedence over the command line..
N In a future release, the Windows registry seings described in this section might not be supported.
GPO seings must be used.
Table 3-12 shows the registry seings for logging in to Horizon Client. These seings are located under
HKEY_CURRENT_USER\Software\VMware, Inc.\VMware VDM\Client\ in the registry. This location is specic to a
particular user, whereas the HKEY_LOCAL_MACHINE seings, described in the next table, are computer-wide
seings and pertain to all local users and all domain users in a Windows domain environment who have
permission to log in to the computer.
Table 3‑12. Horizon Client Registry Settings for Credentials
Registry Setting Description
Password Species the default password.
UserName Species the default user name.
Table 3-13 shows the registry seings for Horizon Client that do not include login credentials. The location
of these seings depends on the type of system:
nFor 32-bit Windows: HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware VDM\Client\
nFor 64-bit Windows: HKLM\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VDM\Client\
Using VMware Horizon Client for Windows
60 VMware, Inc.
Table 3‑13. Horizon Client Registry Settings
Registry Setting Description
DomainName Species the default NETBIOS domain name. For example, you would use mycompany rather
than mycompany.com.
EnableShade Species whether the menu bar (shade) at the top of the Horizon Client window is enabled. The
menu bar is enabled by default except for clients in kiosk mode. A value of false disables the
menu bar.
N This seing is applicable only when you have the display layout set to All Monitors or
Fullscreen.
ServerURL Species the default View Connection Server instance by its URL, IP address, or FQDN.
EnableSoftKeypad If set to true and a Horizon Client window has focus, then physical keyboard, onscreen
keyboard, mouse, and handwriting pad events are sent to the remote desktop or remote
application, even if the mouse or onscreen keyboard is outside of the Horizon Client window.
The default is false.
The following table shows security seings that you can add. The location of these seings depends on the
type of system:
nFor 32-bit Windows: HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware VDM\Client\Security
nFor 64-bit Windows: HKLM\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VDM\Client\Security
Table 3‑14. Security Settings
Registry Setting Description and Valid Values
CertCheckMode Species the certicate checking mode.
n0 implements Do not verify server identity certificates.
n1 implements Warn before connecting to untrusted servers.
n2 implements Never connect to untrusted servers.
SSLCipherList Congures the cipher list to restrict the use of certain cryptographic algorithms and protocols
before establishing an encrypted SSL connection. The cipher list consists of one or more
cipher strings separated by colons.
N All cipher strings are case-sensitive.
The default value is TLSv1:TLSv1.1:TLSv1.2:!aNULL:kECDH+AESGCM:ECDH
+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES.
This means that TLSv.1, TLSv1.1, and TLSv1.2 are enabled. (SSL v2.0 and v3.0 are removed.)
Cipher suites use 128- or 256-bit AES, remove anonymous DH algorithms, and then sort the
current cipher list in order of encryption algorithm key length.
Reference link for the conguration: hp://www.openssl.org/docs/apps/ciphers.html
Chapter 3 Configuring Horizon Client for End Users
VMware, Inc. 61
Using VMware Horizon Client for Windows
62 VMware, Inc.
Managing Remote Desktop and
Application Connections 4
Use Horizon Client to connect to Connection Server or a security server and log in to or o of a remote
desktop, and use remote applications. For troubleshooting purposes, you can also reset remote desktops and
applications.
Depending on how the administrator congures policies for remote desktops, end users might be able to
perform many operations on their desktops.
This chapter includes the following topics:
n“Connect to a Remote Desktop or Application,” on page 63
n“Tips for Using the Desktop and Application Selector,” on page 66
n“Share Access to Local Folders and Drives,” on page 66
n“Hide the VMware Horizon Client Window,” on page 68
n“Reconnecting to a Desktop or Application,” on page 69
n“Create a Desktop or Application Shortcut on Your Client Desktop or Start Menu,” on page 69
n“Switch Desktops or Applications,” on page 70
n“Log O or Disconnect,” on page 70
Connect to a Remote Desktop or Application
After logging in to a server, you can connect to the remote desktops and applications that you are
authorized to use.
Before you have end users access their remote desktops and applications, test that you can connect to a
remote desktop or application from a client device. You must specify a server and supply credentials for
your user account.
To use remote applications, you must connect to View Connection Server 6.0 or later.
The Log in as current user feature is available even if Horizon Client is installed on a remote desktop.
Prerequisites
nObtain credentials to log in, such as a user name and password, RSA SecurID user name and passcode,
RADIUS authentication user name and passcode, or smart card personal identication number (PIN).
nObtain the NETBIOS domain name for logging in. For example, you might use mycompany rather than
mycompany.com.
nPerform the administrative tasks described in “Preparing Connection Server for Horizon Client,” on
page 19.
VMware, Inc. 63
nIf you are outside the corporate network and are not using a security server to access the remote
desktop, verify that your client device is set up to use a VPN connection and turn on that connection.
I VMware recommends using a security server rather than a VPN.
nVerify that you have the fully qualied domain name (FQDN) of the server that provides access to the
remote desktop or application. Underscores (_) are not supported in server names. You also need the
port number if the port is not 443.
nIf you plan to use the RDP display protocol to connect to a remote desktop, verify that the
AllowDirectRDP agent group policy seing is enabled.
nIf your administrator has allowed it, you can congure the certicate checking mode for the SSL
certicate presented by View Connection Server. To determine which mode to use, see “Seing the
Certicate Checking Mode for Horizon Client,” on page 40.
Procedure
1 Double-click the VMware Horizon Client desktop shortcut or click Start > Programs > VMware
Horizon Client.
2 (Optional) To set the certicate checking mode, click the Options buon in the menu bar and select
 SSL.
You can congure this option only if your administrator has allowed it.
3 (Optional) To log in as the currently logged-in Windows domain user, click the Options buon in the
menu bar and select Log in as current user.
This option is available if the Log in as current user module is installed on your client system, and if
your administrator has enabled the global seing for this feature. Some companies choose not to enable
this feature.
4 Double-click the + Add Server buon if no servers have yet been added, or click the + New Server
buon in the menu bar, and enter the name of View Connection Server or a security server, and click
Connect.
Connections between Horizon Client and View Connection Server always use SSL. The default port for
SSL connections is 443. If View Connection Server is not congured to use the default port, use the
format shown in this example: view.company.com:1443.
You might see a message that you must conrm before the login dialog box appears.
N After a successful connection is made, an icon for this server is saved to the Horizon Client home
screen. The next time you open Horizon Client to connect to this server, you can double-click the icon,
or, if you use only this one server, you can right-click the icon for the server and select Autoconnect to
this Server from the context menu.
5 If you are prompted for RSA SecurID credentials or RADIUS authentication credentials, enter the user
name and passcode and click Continue.
6 Enter the credentials of a user who is entitled to use at least one desktop or application pool, select the
domain, and click Login.
If you type the user name using the format user@domain, the name is treated as a user principal name
(UPN) because of the @ sign, and the domain drop-down menu is disabled.
For information about creating desktop pools and entitling users to pools, see Seing Up Desktop and
Application Pools in View document.
Using VMware Horizon Client for Windows
64 VMware, Inc.
7 (Optional) To congure display seings for remote desktops, either right-click a desktop icon or select a
desktop icon and click the  (gear-shaped) icon next to the server name in the upper portion of
the screen.
Option Description
Display protocol If your administrator has allowed it, you can use the Connect Via list to
select the display protocol. VMware Blast requires Horizon Agent 7.0 or
later.
Display layout Use the Display list to select a window size or to use multiple monitors.
8 (Optional) To mark the remote desktop or application as a favorite, right-click the desktop or
application icon and select Mark as Favorite from the context menu that appears.
A star icon appears in the upper-right corner of the desktop or application name. The next time you log
in, you can click the Show Favorites buon to nd this application or desktop quickly.
9 To connect to a remote desktop or application, either double-click its icon or right-click the icon and
select Launch from the context menu.
If you are connecting to a session-based remote desktop, which is hosted on a Microsoft RDS host, and
if the desktop is already set to use a dierent display protocol, you will not be able to connect
immediately. You will be prompted to either use the protocol that is currently set or have the system log
you o of the remote operating system so that a connection can be made with the protocol you selected.
After you are connected, the remote desktop or application window appears. If you are entitled to more
than one desktop or application, the desktop and application selector window also remains open, so that
you can connect to multiple items at the same time.
From the Sharing dialog box, you can allow or deny access to les on your local system. For more
information, see “Share Access to Local Folders and Drives,” on page 66.
If authentication to View Connection Server fails or if the client cannot connect to the remote desktop or
application, perform the following tasks:
nDetermine whether View Connection Server is congured not to use SSL. The client software requires
SSL connections. Check whether the global seing in View Administrator for the Use SSL for client
connections check box is deselected. If so, you must either select the check box, so that SSL is used, or
set up your environment so that clients can connect to an HTTPS enabled load balancer or other
intermediate device that is congured to make an HTTP connection to View Connection Server.
nVerify that the security certicate for View Connection Server is working properly. If it is not, in View
Administrator, you might also see that the agent on desktops is unreachable. These are symptoms of
additional connection problems caused by certicate problems.
nVerify that the tags set on the View Connection Server instance allow connections from this user. See the
View Administration document.
nVerify that the user is entitled to access this desktop or application. See the Seing Up Desktop and
Application Pools in View document.
nIf you are using the RDP display protocol to connect to a remote desktop, verify that the remote
operating system allows remote desktop connections.
What to do next
Congure startup options. If you do not want to require end users to provide the host name of View
Connection Server, or if you want to congure other startup options, use a command-line option to create a
desktop shortcut. See “Running Horizon Client from the Command Line,” on page 57.
Chapter 4 Managing Remote Desktop and Application Connections
VMware, Inc. 65
Tips for Using the Desktop and Application Selector
For your convenience, you can reorganize or reduce the number of icons on the Horizon Client desktop and
application selector screen.
After you authenticate and connect to a particular server, a window appears that includes icons for all the
remote desktops and applications you are entitled to use. Try the following suggestions to quickly launch
your most frequently used remote desktops and applications:
nQuickly type in the rst few leers of the name. For example, if you have icons for Paint, PowerPoint,
and Publisher, you can quickly type pa to select the Paint application.
If more than one item matches the leers you typed, you can press F4 to go to the next item that
matches. When you get to the last item, you can press F4 to go back to the rst item that matches.
nMark an icon as a favorite by right-clicking the icon and selecting Mark as Favorite from the context
menu. After you select favorites, click the Show Favorites View buon (star icon) to remove all the
icons that are not favorites.
nWhile in the Favorites view, select an icon and drag it to change the ordering of the icons. When you are
not in the Favorites view, by default desktop icons are listed rst, in alphabetical order, followed by
application icons, also listed in alphabetical order. But you can drag and drop icons to reposition them
while in the Favorites view.
The ordering of icons is saved on the server you are using, either when you disconnect from the server
or when you launch an application or desktop. If you do not manually disconnect from the server or
launch an item, your changes will not be saved.
nCreate a shortcut so that you can access the remote desktop or application from your own local desktop
and avoid the selector window altogether. Right click the icon and select Create Shortcut from the
context menu.
nRight click the remote desktop or application icon and select Add to Start Menu from the context menu
so that you can access the remote desktop or application from your own local Start menu and avoid the
selector window altogether.
N If you are using a Windows 7 or later client system, after you have connected to a server, desktop, or
application, you can open Horizon Client and right-click the Horizon Client icon in the Windows taskbar to
select that recently used server, desktop, or application. Up to 10 items appear in the list. To remove an item,
right-click it and select Remove from this list.
If you right-click the Horizon Client icon in the taskbar and do not see a jump list, right-click the taskbar,
select Properties, and click the Start Menu tab. In the Privacy section, select the Store and display recently
opened items in the Start menu and the taskbar check box, and click OK.
Share Access to Local Folders and Drives
You can congure Horizon Client to share folders and drives on your local system with remote desktops
and applications. Drives can include mapped drives and USB storage devices. This feature is called client
drive redirection.
In a Windows remote desktop, shared folders and drives appear in the Devices and drives section in the
This PC folder, or in the Other section in the Computer folder, depending on the Windows operating
system version. In a remote application, such as Notepad, you can browse to and open a le in a shared
folder or drive. The folders and drives you select for sharing appear in the le system as network drives that
use the naming format name on MACHINE-NAME.
Using VMware Horizon Client for Windows
66 VMware, Inc.
You do not need to be connected to a remote desktop or application to congure client drive redirection
seings. The seings apply to all your remote desktops and applications. That is, you cannot congure the
seings so that local client folders are shared with one remote desktop or application but not with other
remote desktops or applications.
You can also turn on the ability to open local les with remote applications directly from the local le
system. When you right-click a local le, the Open with menu also lists the available remote applications.
You can also set les to be opened automatically with remote applications when you double-click the le.
When you enable this feature, all les on your local le system that have certain le extensions are
registered with the View server that you are logged in to. For example, if Microsoft Word is one of the
remote applications available from the View server, you can right-click a .docx le on your local le system
and open the le with the remote MS Word application. This feature requires Horizon 6.2 servers and
agents.
An administrator can hide the client drive redirection feature in Horizon Client by enabling a group policy
seing. For more information, see Disable sharing  and folders in Table 3-7.
Conguring the browser on the client system to use a proxy server can cause poor client drive redirection
performance if the secure tunnel is enabled on the Connection Server instance. For the best client drive
redirection performance, congure the browser not to use a proxy server or automatically detect LAN
seings.
Prerequisites
To share folders and drives with a remote desktop or application, you must enable the client drive
redirection feature. This task includes installing View Agent 6.1.1 or later, or Horizon Agent 7.0 or later, and
enabling the agent Client Drive Redirection option. It can also include seing policies to control client drive
redirection behavior. For more information, see the Seing Up Desktop and Application Pools in View
document.
Procedure
1 Open the Seings dialog box with the Sharing panel displayed.
Option Description
From the desktop and application
selection window
Right-click a desktop or application icon, select , and select
Sharing in the left panel of the window that appears.
From the Sharing dialog box that
appears when you connect to a
desktop or application
Click the  > Sharing link in the dialog box.
From within a desktop OS Select Options > Share Folders from the menu bar.
2Congure the client drive redirection seings.
Option Action
Share a specific folder or drive with
remote desktops and applications
Click the Add buon, browse to and select the folder or drive to share, and
click OK.
N You cannot share a folder on a USB device if the device is already
connected to a remote desktop or application with the USB redirection
feature.
Also, do not turn on the USB redirection feature that automatically
connects USB devices at startup or when the device is inserted. If you do
so, the next time you start Horizon Client or plug in the USB device, the
device will be connected using the USB redirection feature rather than the
client drive redirection feature.
Stop sharing a specific folder or
drive
Select the folder or drive in the Folder list and click the Remove buon.
Chapter 4 Managing Remote Desktop and Application Connections
VMware, Inc. 67
Option Action
Permit remote desktops and
applications access to files in your
local user directory
Select the Share your local  user-name check box.
Share USB storage devices with
remote desktops and applications
Select the Allow access to removable storage check box. The client drive
redirection feature automatically shares all USB storage devices inserted in
your client system and all FireWire and Thunderbolt-connected external
drives. You do not need to select a specic device to share.
N USB storage devices already connected to a remote desktop or
application with the USB redirection feature are not shared.
If this check box is deselected, you can use the USB redirection feature to
connect USB storage devices to remote desktops and applications.
Turn on the ability to open a local
file with a remote application from
the local file system
Select the Open local  in hosted applications check box. With this
option, you can right-click a le in your local le system and select to open
the le with a remote application.
You can also change the properties of the le so that all les with that le
extension are opened with the remote application by default, such as when
you double-click the le. For example, you can right-click a le, select
Properties, and click Change to select the remote application to open les
of that type.
Your administrator can disable this feature.
Do not show the Sharing dialog box
when you connect to a remote
desktop or application
Select the Do not show dialog when connecting to a desktop or
application check box.
If this check box is deselected, the Sharing dialog box appears the rst time
you connect to a desktop or application after you connect to a server. For
example, if you log in to a server and connect to a desktop, you see the
Sharing dialog box. If you then connect to another desktop or application,
you do not see the dialog box again. To see the dialog box again, you must
disconnect from the server and then log in again.
What to do next
Verify that you can see the shared folders from within the remote desktop or application:
nFrom within a Windows remote desktop, open File Explorer and look in the Devices and drives section
in the This PC folder, or open Windows Explorer and look in the Other section in the Computer folder.
nFrom within a remote application, if applicable, select File > Open or File > Save As and navigate to the
folder or drive, which appears in the le system as a network drive that uses the naming format folder-
name on MACHINE-NAME.
Hide the VMware Horizon Client Window
You can hide the VMware Horizon Client window after you open a remote desktop or application.
You can also set a preference that always hides the VMware Horizon Client window after a remote desktop
or application opens.
N Administrators can use a group policy seing to congure whether the window is always hidden
after a remote desktop or application opens.
For more information, see “General Seings for Client GPOs,” on page 49.
Procedure
nTo hide the VMware Horizon Client window after you open a remote desktop or application, click the
Close buon in the corner of the VMware Horizon Client window.
Using VMware Horizon Client for Windows
68 VMware, Inc.
nTo set a preference that always hides the VMware Horizon Client window after a remote desktop or
application opens, before you connect to a View server, click the Options buon in the menu bar and
select Hide the selector after launching an item.
nTo show the VMware Horizon Client window after it has been hidden, right-click the
VMware Horizon Client icon in the system tray and select Show VMware Horizon Client, or, if you are
logged in to a remote desktop, click the Options buon in the menu bar and select Switch to Other
Desktop.
Reconnecting to a Desktop or Application
For security purposes, administrators set timeouts that log you o of a server after a certain number of
hours and that lock a remote application after a certain number of minutes of inactivity.
With the View 6.0 remote applications feature, if you have not used a remote application for a certain
amount of time, then 30 seconds before the application is automatically locked, you receive a warning
prompt. If you do not respond, the application is locked. By default the timeout occurs after 15 minutes of
inactivity, but your administrator can change the time period.
For example, if you have one or more applications open and you walk away from your computer, when you
return an hour later, the application windows might no longer be open. Instead you might see a dialog box
prompting you to click the OK buon so that the application windows appear again.
The server timeout period is typically set for a certain number of hours of inactivity. By default, if you have
Horizon Client open and connected to a particular server for more than 10 hours, you will be required to log
in again. This timeout applies regardless of whether you are connected to a remote application or a remote
desktop.
To congure these timeout seings, in View Administrator, go to Global  and edit the general
seings.
Create a Desktop or Application Shortcut on Your Client Desktop or
Start Menu
You can create a shortcut for a remote desktop or application. The shortcut appears on your client desktop,
just like shortcuts for locally installed applications. You can also create a Start menu item that appears in the
Programs list.
Procedure
1 Start Horizon Client and log in to the server.
2 In the desktop and application selection window, right-click an application or desktop and select Create
Shortcut or Add to Start Menu from the context menu that appears.
Depending on the command you selected, a shortcut item is created on your client desktop or in the Start
menu of your client system.
What to do next
You can rename, delete, or perform any action on this shortcut that you can perform on shortcuts for locally
installed applications. When you use the shortcut, if you are not already logged in to the server, you are
prompted to log in before the remote desktop or application window opens.
Chapter 4 Managing Remote Desktop and Application Connections
VMware, Inc. 69
Switch Desktops or Applications
If you are connected to a remote desktop, you can switch to another desktop. You can also connect to remote
applications while you are connected to a remote desktop.
Procedure
uSelect a remote desktop or application from the same server or a dierent server.
Option Action
Choose a different desktop or
application on the same server
Perform one of the following actions:
nIf you are currently logged in to a remote desktop select Options >
Switch to Other Desktop from the Horizon Client menu bar, and
select a desktop or application to launch.
nIf you are currently logged in to a remote application, right-click the
VMware Horizon Client icon in the system tray and select Show
VMware Horizon Client to display the desktop and application
selector window, and double-click the icon for the other dierent
desktop or application.
nFrom the desktop and application selector window, double-click the
icon for th other desktop or application. That desktop or application
opens in a new window so that you have multiple windows open, and
you can switch between them.
Choose a different desktop or
application on a different server
Perform either of the following actions:
nIf you want to keep the current desktop or application open and also
connect to a remote desktop or application on another server, start a
new instance of Horizon Client and connect to the other desktop or
application.
nIf you want to close the current desktop and connect to a desktop on
another server, go to the desktop selector window, click the
Disconnect icon in the upper-left corner of the window, and conrm
that you want to log o of the server. You will be disconnected from
the current server and any open desktop sessions. You can then
connect to a dierent server.
Log Off or Disconnect
With some congurations, if you disconnect from a remote desktop without logging o, applications in the
desktop can remain open. You can also disconnect from a server and leave remote applications running.
Even if you do not have a remote desktop open, you can log o of the remote desktop operating system.
Using this feature has the same result as sending Ctrl+Alt+Del to the desktop and then clicking Log .
N The Windows key combination Ctrl+Alt+Del is not supported in remote desktops. To use the
equivalent of pressing Ctrl+Alt+Del, click the Send Ctrl+Alt+Delete buon in the menu bar. Alternatively, in
most cases, you can press Ctrl+Alt+Insert.
Using VMware Horizon Client for Windows
70 VMware, Inc.
Procedure
nDisconnect from a remote desktop without logging o.
Option Action
From the remote desktop window Perform one of the following actions:
nClick the Close buon in the corner of the desktop window.
nSelect Options > Disconnect from the menu bar in the desktop
window.
From the desktop and application
selector window
The desktop and application selector window is open if you are entitled to
multiple desktops or applications on the server. In the upper-left corner of
the desktop selector window, click the Disconnect from this server icon
and click Yes in the warning box.
N Your View administrator can congure your desktop to automatically log o when
disconnected. In that case, any open programs in your desktop are stopped.
nLog o and disconnect from a remote desktop.
Option Action
From within the desktop OS Use the Windows Start menu to log o.
From the menu bar Select Options > Disconnect and Log .
If you use this procedure, les that are open on the remote desktop will be
closed without being saved rst.
nDisconnect from a remote application.
Option Action
Disconnect from the application but
not the server
Quit the application in the usual manner, for example, click the Close
buon in the corner of the application window.
Disconnect from the application
and the server
Perform one of the following actions:
nIn the upper-left corner of the application selector window, click the
Disconnect from this server icon and click Yes in the warning box.
nRight-click the Horizon Client icon in the system tray and select Quit.
Close the application selector
window but leave the application
running
Clicking the Close buon only closes the application selector window.
nLog o when you do not have a remote desktop open.
If you use this procedure, les that are open on the remote desktop will be closed without being saved
rst.
a Start Horizon Client, connect to the View Connection Server that provides access to the remote
desktop, and supply your authentication credentials.
b Right-click the desktop icon and select .
Chapter 4 Managing Remote Desktop and Application Connections
VMware, Inc. 71
Using VMware Horizon Client for Windows
72 VMware, Inc.
Working in a Remote Desktop or
Application 5
View provides the familiar, personalized desktop and application environment that end users expect. End
users can access USB and other devices connected to their local computer, send documents to any printer
that their local computer can detect, authenticate with smart cards, and use multiple display monitors.
This chapter includes the following topics:
n“Feature Support Matrix for Windows Clients,” on page 73
n“Internationalization,” on page 77
n“Enabling Support for Onscreen Keyboards,” on page 78
n“Monitors and Screen Resolution,” on page 78
n“Connect USB Devices,” on page 83
n“Using the Real-Time Audio-Video Feature for Webcams and Microphones,” on page 86
n“Copying and Pasting Text and Images,” on page 88
n“Using Remote Applications,” on page 89
n“Printing from a Remote Desktop or Application,” on page 89
n“Control Adobe Flash Display,” on page 91
n“Clicking URL Links That Open Outside of Horizon Client,” on page 92
n“Using the Relative Mouse Feature for CAD and 3D Applications,” on page 92
n“Using Scanners,” on page 92
n“Using Serial Port Redirection,” on page 93
n“Keyboard Shortcuts,” on page 95
Feature Support Matrix for Windows Clients
Some features are supported on one type of Horizon Client but not on another.
When planning which display protocol and features to make available to your end users, use the following
information to determine which client operating systems support the feature.
VMware, Inc. 73
Table 5‑1. Remote Desktop Features Supported on Windows-Based Horizon Client Systems
Feature
Windows XP
Desktop (View
Agent 6.0.2 and
earlier)
Windows Vista
Desktop (View
Agent 6.0.2 and
earlier)
Windows
7 Desktop
Windows
8.x
Desktop
Windows
10
Desktop
Windows
Server
2008/2012 R2
Desktop or
Windows
Server 2016
Desktop
USB redirection Limited Limited X X X X
Client drive
redirection
X X X X
Real-Time Audio-
Video (RTAV)
Limited Limited X X X X
Scanner
redirection
Limited X X X X
Serial port
redirection
X X X X
Blast Extreme
display protocol
X X X X
RDP display
protocol
Limited Limited X X X X
PCoIP display
protocol
Limited Limited X X X X
Persona
Management
Limited Limited X X
Wyse MMR Limited Limited
Windows Media
MMR
X X X
Location-based
printing
Limited Limited X X X X
Virtual printing Limited Limited X X X X
Smart cards Limited Limited X X X X
RSA SecurID or
RADIUS
Limited Limited X X X X
Single sign-on Limited Limited X X X X
Multiple monitors Limited Limited X X X X
Windows 10 desktops require View Agent 6.2 or later, or Horizon Agent 7.0 or later. Windows Server 2012
R2 desktops require View Agent 6.1 or later, or Horizon Agent 7.0 or later.
I View Agent 6.1 and later releases do not support Windows XP and Windows Vista desktops.
View Agent 6.0.2 is the last View release that supports these guest operating systems. Customers who have
an extended support agreement with Microsoft for Windows XP and Vista, and an extended support
agreement with VMware for these guest operating systems, can deploy the View Agent 6.0.2 version of their
Windows XP and Vista desktops with View Connection Server 6.1.
For information about which editions of each client operating system are supported, or which service packs,
see “System Requirements for Windows Clients,” on page 10.
Using VMware Horizon Client for Windows
74 VMware, Inc.
Feature Support for Session-Based Desktops on RDS Hosts
RDS hosts are server computers that have Windows Remote Desktop Services and View Agent or
Horizon Agent installed. Multiple users can have desktop sessions on an RDS host simultaneously. An RDS
host can be either a physical machine or a virtual machine.
N The following table contains rows only for the features that are supported. Where the text species a
minimum version of View Agent, the text "and later" is meant to include Horizon Agent 7.0.x and later.
Table 5‑2. Features Supported for RDS Hosts with View Agent 6.0.x or Later, or Horizon Agent 7.0.x or
Later, Installed
Feature
Windows Server 2008 R2
RDS Host
Windows Server 2012
RDS Host
Windows Server 2016 RDS
Host
RSA SecurID or RADIUS X X Horizon Agent 7.0.2 and later
Smart card View Agent 6.1 and later View Agent 6.1 and later Horizon Agent 7.0.2 and later
Single sign-on X X Horizon Agent 7.0.2 and later
RDP display protocol (for
desktop clients)
X X Horizon Agent 7.0.2 and later
PCoIP display protocol X X Horizon Agent 7.0.2 and later
VMware Blast display
protocol
Horizon Agent 7.0 and later Horizon Agent 7.0 and
later
Horizon Agent 7.0.2 and later
HTML Access View Agent 6.0.2 and later
(virtual machine only)
View Agent 6.0.2 and
later (virtual machine
only)
Horizon Agent 7.0.2 and later
Windows Media MMR View Agent 6.1.1 and later View Agent 6.1.1 and
later
Horizon Agent 7.0.2 and later
USB redirection (USB
storage devices only)
View Agent 6.1 and later Horizon Agent 7.0.2 and later
Client drive redirection View Agent 6.1.1 and later View Agent 6.1.1 and
later
Horizon Agent 7.0.2 and later
Virtual printing (for desktop
clients)
View Agent 6.0.1 and later
(virtual machine only)
View Agent 6.0.1 and
later (virtual machine
only)
Horizon Agent 7.0.2 and later
(virtual machine only)
Scanner redirection View Agent 6.0.2 and later View Agent 6.0.2 and
later
Horizon Agent 7.0.2 and later
Location-based printing View Agent 6.0.1 and later
(virtual machine only)
View Agent 6.0.1 and
later (virtual machine
only)
Horizon Agent 7.0.2 and later
(virtual machine only)
Multiple monitors (for
desktop clients)
X X Horizon Agent 7.0.2 and later
Unity Touch (for mobile and
Chrome OS clients)
X X Horizon Agent 7.0.2 and later
Real-Time Audio-Video
(RTAV)
Horizon Agent 7.0.2 and
later
Horizon Agent 7.0.2 and
later
Horizon Agent 7.0.3 and later
For information about which editions of each guest operating system are supported, or which service packs,
see the "Supported Operating Systems for View Agent" topic in the View 5.x or 6.x installation
documentation. See the "Supported Operating Systems for Horizon Agent" topic in the Horizon 7
installation documentation.
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 75
Limitations for Specific Features
Features that are supported on Windows-based clients have the following restrictions.
Table 5‑3. Requirements for Specific Features
Feature Requirements
Windows Media MMR Requires View Agent 6.0.2 or later. To use the Windows Media MMR feature with RDS
desktops, you must have View Agent 6.1.1 or later, or Horizon Agent 7.0 or later.
If you use the VMware Blast Extreme display protocol, you must have Horizon Agent 7.0
or later.
Serial port redirection Requires View Agent 6.1.1 or later. For Windows 10, requires View Agent 6.2 or later, or
Horizon Agent 7.0 or later.
If you use the VMware Blast Extreme display protocol, you must have Horizon Agent 7.0
or later.
Virtual printing and location-
based printing for Windows
Server 2008 R2 desktops, RDS
desktops (on virtual machine
RDS hosts), and remote
applications
Requires Horizon 6.0.1 with View or later.
If you use the VMware Blast Extreme display protocol for this feature, you must have
Horizon Agent 7.0 or later.
Scanner redirection Requires View Agent 6.0.2 or later. Requires the PCoIP display protocol. For Windows
10, requires View Agent 6.2 or later, or Horizon Agent 7.0 or later.
If you use the VMware Blast Extreme display protocol, you must have Horizon Agent 7.0
or later.
Client drive redirection For single-user virtual machine desktops and session-based desktops on RDS hosts,
requires View Agent 6.1.1 or later, or Horizon Agent 7.0 or later.
If you use the VMware Blast Extreme display protocol, you must have Horizon Agent 7.0
or later.
N You can also use Horizon Client to securely access remote Windows-based applications, in addition
to remote desktops. Selecting an application in Horizon Client opens a window for that application on the
local client device, and the application looks and behaves as if it were locally installed.
You can use remote applications only if you are connected to Connection Server 6.0 or later. For information
about which operating systems are supported for the RDS (Remote Desktop Sessions) host, which provides
remote applications and session-based desktops, see "Supported Operating Systems for Horizon Agent"
topic in the View 5.x or 6.x installation documentation. See the "Supported Operating Systems for
Horizon Agent" topic in the Horizon 7 installation documentation.
For descriptions of these features and their limitations, see the View Architecture Planning document.
Feature Support for Linux Desktops
Some Linux guest operating systems are supported if you have View Agent 6.1.1 or later, or Horizon Agent
7.0 or later. For a list of supported Linux operating systems and information about supported features, see
Seing Up Horizon 6 for Linux Desktops, which is part of the Horizon 6, version 6.1 documentation.
Using VMware Horizon Client for Windows
76 VMware, Inc.
Features Supported in Nested Mode
Nested mode is sometimes used for zero clients or thin clients, where, when the end user logs in to the zero
client, Horizon Client automatically starts and logs the user in to a remote desktop. From this remote
desktop, the user launches hosted applications.
In this setup, the remote desktop is either a single-user virtual machine desktop or a desktop provided by an
RDS host. In either case, to provide hosted applications, the Horizon Client software must be installed in the
remote desktop. This setup is called nested mode because the client connects to a desktop that also has the
client installed.
The following operating systems are supported when running Horizon Client in nested mode.
nWindows Server 2008 R2
nWindows Server 2012 R2
nWindows 7 Enterprise SP1
nWindows 10 Enterprise, version 1607
The following features are supported when a user uses Horizon Client in nested mode.
nVMware Blast, PCoIP, and RDP display protocols
nLocation-based printing
nVirtual printing
nSingle sign-on (without smart card)
nClipboard redirection
nURL Content Redirection
Internationalization
The user interface and documentation are available in English, Japanese, French, German, Simplied
Chinese, Traditional Chinese, Korean, and Spanish.
Use a Local IME with Remote Applications
When using non-English keyboards and locales, you can use an IME (input method editor) installed in your
local system to send non-English characters to a remote hosted application.
You can also use hot keys and icons in the notication area (system tray) of your local system to switch to a
dierent IME. No IME is required to be installed in the remote RDS host.
When this feature is turned on, the local IME is used. If an IME is installed and congured on the RDS host
where the remote application is installed, that remote IME is ignored.
By default the feature is turned o. Whenever you change the seing to turn the feature on or o, you must
disconnect from the server and log in again before the change can take eect.
Prerequisites
nVerify that one or more IMEs are installed in the client system.
nMake sure that the input language on your local client system matches the language used in your IME.
The input language on the RDS host is not applicable.
nVerify that the remote desktop has View Agent 6.0.2, or Horizon Agent 7.0 or later, installed.
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 77
Procedure
1 In the desktop and application selector window of Horizon Client, right-click a remote application and
select .
2 In the Remote Applications pane that appears, select Extend the local IME to hosted applications
check box and click OK.
3 Restart the session by using one of the following options:
Option Description
Log off of the server Disconnect from the server and then log in to the server again and connect
to the application again. You can resume your applications, which were
disconnected but not closed, as were any remote desktops.
Reset the applications Right-click a remote application icon, select , and click Reset.
Using this option, if you have any remote desktops open, they are not
disconnected. All the remote applications are closed, however, and you
must start them again.
The seing takes eect only after you restart the session. The seing applies to all remote hosted
applications on the server.
4 Use the local IME as you would with any locally installed applications.
The language designation and an icon for the IME appear in the notication area (system tray) of your local
client system. You can use hot keys to switch to a dierent language or IME. Key combinations that perform
certain actions, such as CTRL+X for cuing text and Alt+Right Arrow for moving to a dierent tab, will still
work correctly.
N On Windows 7 and 8.x systems, you can specify hot keys for IMEs by using the Text Services and
Input Languages dialog box (available by going to Control Panel > Region and Language > Keyboards and
Languages tab > Change Keyboards  > Text Services and Input Languages > Advanced Key
 tab).
Enabling Support for Onscreen Keyboards
You can congure your client system so that if a Horizon Client window has focus, then physical keyboard,
onscreen keyboard, mouse, and handwriting pad events are sent to the remote desktop or remote
application, even if the mouse or onscreen keyboard is outside of the Horizon Client window.
This feature is especially useful if you are using an x86-based Windows tablet, such as a Windows Surface
Pro. To use this feature, you must set the Windows Registry key EnableSoftKeypad to true. The location of
this key depends on the type of system:
nFor 32-bit Windows: HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware VDM\Client\
nFor 64-bit Windows: HKLM\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VDM\Client\
Monitors and Screen Resolution
You can extend a remote desktop to multiple monitors. If you have a high-resolution monitor, you can see
the remote desktop or application in full resolution.
The All Monitors display mode displays a remote desktop window on multiple monitors. The remote
desktop window appears on all monitors by default. You can use the selective multiple-monitor feature to
display a remote desktop window on a subset of your monitors.
Using VMware Horizon Client for Windows
78 VMware, Inc.
If you are using All Monitors mode and click the Minimize buon, if you then maximize the window, the
window goes back to All Monitors mode. Similarly, if you are using Fullscreen mode and minimize the
window, when you maximize the window, the window goes back to Fullscreen mode on one monitor.
If you have Horizon Client use all monitors, if you maximize an application window, the window expands
to the full screen of only the monitor that contains it.
Supported Multiple Monitor Configurations
Horizon Client supports the following multiple monitor congurations.
nIf you use two monitors, the monitors are not required to be in the same mode. For example, if you are
using a laptop connected to an external monitor, the external monitor can be in portrait mode or
landscape mode.
nMonitors can be placed side by side, stacked two by two, or vertically stacked only if you are using two
monitors and the total height is less than 4096 pixels.
nTo use the selective multiple-monitor feature, you must use the VMware Blast display protocol or the
PCoIP display protocol. For more information, see “Select Specic Monitors in a Multiple-Monitor
Setup,” on page 80.
nTo use the 3D rendering feature, you must use the VMware Blast display protocol or the PCoIP display
protocol. You can use up to two monitors, with a resolution of up to 1920 X 1200. For a resolution of 4K
(3840 X 2160), only one monitor is supported.
nIf you use instant clone desktops pools, the maximum number of monitors that you can use to display a
remote desktop is two, with a resolution of up to 2560 X 1600.
nWith the VMware Blast display protocol or the PCoIP display protocol, a remote desktop screen
resolution of 4K (3840 x 2160) is supported. The number of 4K displays that are supported depends on
the hardware version of the desktop virtual machine and the Windows version.
Hardware Version Windows Version
Number of 4K Displays
Supported
10 (ESXi 5.5.x compatible) 7, 8, 8.x, 10 1
11 (ESXi 6.0 compatible) 7 (3D rendering feature disabled and Windows Aero
disabled)
3
11 7 (3D rendering feature enabled) 1
11 8, 8.x, 10 1
The remote desktop must have View Agent 6.2 or later, or Horizon Agent 7.0 or later, installed. For best
performance, the virtual machine should have at least 2 GB of RAM and 2 vCPUs. This feature might
require good network conditions, such as a bandwidth of 1000 Mbps with low network latency and a
low package loss rate.
N When the remote desktop screen resolution is set to 3840 x 2160 (4K), items on the screen might
appear smaller, and you might not be able to use the Screen Resolution dialog box in the remote
desktop to make text and other items larger. In this scenario, you can set the client machine's DPI to the
proper seing and enable the DPI Synchronization feature to redirect the client machine's DPI seing to
the remote desktop.
nIf you use Microsoft RDP 7, the maximum number of monitors that you can use to display a remote
desktop is 16.
nIf you use Microsoft RDP display protocol, you must have Microsoft Remote Desktop Connection
(RDC) 6.0 or later installed in the remote desktop.
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 79
Select Specific Monitors in a Multiple-Monitor Setup
You can use the selective multiple-monitor feature to select the monitors on which to display a remote
desktop window. For example, if you have three monitors, you can specify that the remote desktop window
appears on only two of those monitors. By default, a remote desktop window appears on all monitors in a
multiple-monitor setup.
You can select up to four adjacent monitors. The monitors can be side by side, stacked two by two, or
stacked vertically. A maximum of two monitors can be stacked vertically.
This feature is not supported for remote applications.
Procedure
1 Start Horizon Client and log in to a server.
2 In the desktop and application selection window, right-click the remote desktop and select .
3 Select PCoIP or VMware Blast from the Connect Via drop-down menu.
4 Select All Monitors from the Display drop-down menu.
Thumbnails of the monitors that are currently connected to your client system appear under Display
seings. The display topology matches the display seings on your client system.
5 Click a thumbnail to select or deselect a monitor on which to display the remote desktop window.
When you select a monitor, its thumbnail turns green. A warning message appears if you violate a
display selection rule.
6 Click Apply to save your changes.
7 Click OK to close the dialog box.
8 Connect to the remote desktop.
Your changes are applied immediately when you connect to the remote desktop. Your changes are
saved in the Horizon Client preferences le for the remote desktop after you exit from Horizon Client.
Use One Monitor in a Multiple-Monitor Setup
If you have multiple monitors but want a remote desktop window to appear on only one monitor, you can
congure the remote desktop window to open on a single monitor.
This preference is not supported for remote applications.
Procedure
1 Start Horizon Client and log in to a server.
2 In the desktop and application selection window, right-click the remote desktop and select .
3 Select PCoIP or VMware Blast from the Connect Via drop-down menu.
4 From the Display menu, select Window - Large, Window - Small, or Custom.
If you select Custom, you can select a specic window size.
5 Click Apply to save your changes.
Your changes take eect immediately after you click Apply.
6 Click OK to close the dialog box.
Using VMware Horizon Client for Windows
80 VMware, Inc.
By default, the remote desktop window opens on the primary monitor. You can drag the remote desktop
window to a non-primary monitor, and the next time you open the remote desktop, the remote desktop
window appears on that same monitor. The window is opened and centered in the monitor and uses the
window size you selected for the display mode, not a size that you might have created by dragging the
window to resize it.
Use Display Scaling
A user who has a high-resolution screen such as a 4K monitor, or who has poor eyesight, generally has
scaling enabled by seing the DPI (Dots Per Inch) on the client machine to greater than 100 percent. With the
Display Scaling feature, the remote desktop or application supports the client machine's scaling seing, and
the remote desktop or application appears normal-sized instead of very small.
Horizon Client saves the display scaling seing for each remote desktop separately. For remote applications,
the display scaling seing applies to all remote applications that are available to the currently logged-in
user. The display scaling seing appears, even if the DPI seing is 100 percent on the client machine.
An administrator can hide the display scaling seing by enabling the Horizon Client Locked Guest Size
group policy seing. Enabling the Locked Guest Size group policy seing does not disable the DPI
Synchronization feature. To disable the DPI Synchronization feature, an administrator must disable the DPI
Synchronization group policy seing. For more information, see “Using DPI Synchronization,” on
page 81.
In a multiple-monitor setup, using display scaling does not aect the number of monitors and the maximum
resolutions that Horizon Client supports. When display scaling is allowed and in eect, scaling is based on
the DPI seing of the primary monitor.
This procedure describes how to enable the Display Scaling feature before you connect to a remote desktop
or application. You can enable the Display Scaling feature after you connect to a remote desktop by selecting
Options > Allow Display Scaling.
Procedure
1 Start Horizon Client and connect to a server.
2 In the desktop and application selection window, right-click the remote desktop or application and
select .
3 Select the Allow display scaling check box.
4 Click Apply to save your changes.
5 Click OK to close the dialog box.
Using DPI Synchronization
The DPI Synchronization feature ensures that the remote desktop's DPI seing matches the client machine's
DPI seing for new remote sessions. When you start a new session, Horizon Agent sets the DPI value in the
remote desktop to match the DPI value of the client machine.
The DPI Synchronization feature cannot change the DPI seing for active remote sessions. If you reconnect
to an existing remote session, the Display Scaling feature (if enabled) scales the remote desktop or
application appropriately.
The DPI Synchronization feature is enabled by default. An administrator can disable the DPI
Synchronization feature by disabling the Horizon Agent DPI Synchronization group policy seing. You
must log out and log in again to make the conguration change take eect. For more information, see
"Horizon Agent Conguration ADM Template Seings" in the Seing Up Desktop and Application Pools in
View document.
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 81
When the DPI Synchronization feature and the Display Scaling feature are both enabled, only one feature
takes eect at any given time. Display scaling occurs only when DPI synchronization has not yet taken eect
(that is, before the DPI seing on the remote desktop matches the DPI seing on the client machine), and
display scaling stops working after the DPI seings match.
The DPI Synchronization feature requires Windows 7 or later for single-session desktops, Windows Server
2008 R2 or later for session-based desktops and applications on RDS hosts, Horizon Agent 7.0.2 or later, and
Horizon Client 4.2 or later.
N The DPI Synchronization feature is not available if you use Horizon Client 4.2 with Horizon Agent
7.0 or 7.0.1, or Horizon Client 4.0 or 4.1 with Horizon Agent 7.0.2 or later. Only the Display Scaling feature is
available in these scenarios.
Following are tips for using the DPI Synchronization feature:
nIf you change the DPI seing on the client machine, you must log out and log in again to make
Horizon Client aware of the new DPI seing on the client machine. This requirement applies even if the
client machine is running Windows 10.
nIf you start a remote session on a client machine that has a DPI seing of more than 100 percent, and
then use the same session on another client machine that has a dierent DPI seing of more than 100
percent, you must log out and log back in to the session on the second client machine to make DPI
synchronization work on the second client machine.
nAlthough Windows 10 and Windows 8.x machines support dierent DPI seings on dierent monitors,
the DPI Synchronization feature uses only the DPI value that is set on the client machine's primary
monitor. All monitors in the remote desktop also use the same DPI seing as the client machine's
primary monitor. Horizon Client does not support dierent DPI seings in dierent monitors.
nIf an administrator changes the DPI Synchronization group policy seing value for Horizon Agent,
you must log out and log in again to make the new seing take eect.
nWhen you connect a laptop that supports dierent DPI seings on dierent monitors to an external
monitor, and you set the external monitor to be the primary monitor, Windows automatically changes
the primary monitor and primary monitor DPI seing every time you detach or reaach the external
monitor. In this situation, you must log out and log back in to the client system to make Horizon Client
aware of the primary monitor change, and you must log out and log back in to the remote desktop or
application to make the DPI seings match between the client system and remote desktop or
application.
Change the Display Mode While a Desktop Window Is Open
You can change display modes, such as from All Monitors mode to Fullscreen mode, without having to
disconnect from a remote desktop.
This feature is not supported for remote applications.
Prerequisites
Verify that you are using VMware Blast display protocol or the PCoIP display protocol.
Procedure
1 On the client system, in the notication area (system tray), right-click the Horizon Client icon and select
the option to open the Seings window.
N You can also open the Seings window from the application and desktop selection window.
2 Select the remote desktop and select a display option.
Using VMware Horizon Client for Windows
82 VMware, Inc.
Connect USB Devices
You can use locally aached USB devices, such as thumb ash drives, cameras, and printers, from a remote
desktop. This feature is called USB redirection.
When you use this feature, most USB devices that are aached to the local client system become available
from a menu in Horizon Client. You use the menu to connect and disconnect the devices.
N With View Agent 6.1 or later, or Horizon Agent 7.0 or later, you can also redirect locally connected
USB thumb ash drives and hard disks for use in RDS desktops and applications. Other types of USB
devices, including other types of storage devices, such as security storage drives and USB CD-ROM, are not
supported in RDS desktops and applications.
Using USB devices with remote desktops has the following limitations:
nWhen you access a USB device from a menu in Horizon Client and use the device in a remote desktop,
you cannot access the device on the local computer.
nUSB devices that do not appear in the menu, but are available in a remote desktop, include human
interface devices such as keyboards and pointing devices. The remote desktop and the local computer
use these devices at the same time. Interaction with these devices can sometimes be slow because of
network latency.
nLarge USB disk drives can take several minutes to appear in the desktop.
nSome USB devices require specic drivers. If a required driver is not already installed on a remote
desktop, you might be prompted to install it when you connect the USB device to the remote desktop.
nIf you plan to aach USB devices that use MTP drivers, such as Android-based Samsung smart phones
and tablets, congure Horizon Client so that it automatically connects USB devices to your remote
desktop. Otherwise, if you try to manually redirect the USB device by using a menu item, the device is
not redirected unless you unplug the device and then plug it in again.
nDo not connect to scanners by using the Connect USB Device menu. To use a scanner device, use the
scanner redirection feature. This feature is available for Horizon Client when used with View Agent
6.0.2 or later or Horizon Agent 7.0 or later. See “Using Scanners,” on page 92.
nWebcams are not supported for USB redirection using the Connect USB Device menu. To use a
webcam or audio input device, you must use the Real-Time Audio-Video feature. This feature is
available when used with View 5.2 Feature Pack 2 or a later release. See “Using the Real-Time Audio-
Video Feature for Webcams and Microphones,” on page 86.
nThe redirection of USB audio devices depends on the state of the network and is not reliable. Some
devices require a high data throughput even when they are idle. If you have the Real-Time Audio-
Video feature, included with View 5.2 Feature Pack 2 or a later release, audio input and output devices
work well using that feature, and you do not need to use USB redirection for those devices.
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 83
You can connect USB devices to a remote desktop either manually or automatically.
N Do not redirect USB devices such as USB Ethernet devices and touch screen devices to the remote
desktop. If you redirect a USB Ethernet device, your client system loses network connectivity. If you redirect
a touch screen device, the remote desktop receives touch input but not keyboard input. If you have set your
virtual desktop to autoconnect USB devices, you can congure a policy to exclude specic devices. See the
topic "Conguring Filter Policy Seings for USB Devices" in the Seing Up Desktop and Application Pools in
View document.
I This procedure tells how to use a VMware Horizon Client menu item to congure
autoconnecting USB devices to a remote desktop. You can also congure autoconnecting by using the
Horizon Client command-line interface or by creating a group policy.
For more information about the command-line interface, see “Running Horizon Client from the Command
Line,” on page 57. For more information about creating group policies, see the Seing Up Desktop and
Application Pools in View document.
Prerequisites
nTo use USB devices with a remote desktop, a View administrator must have enabled the USB feature for
the remote desktop.
This task includes installing the USB Redirection component of the agent, and can include seing
policies regarding USB redirection. For more information, see the View Administration document if you
are using Connection Server and Agent 5.3.x. See Seing Up Desktop and Application Pools in View if you
are using Connection Server and Agent 6.0 or later.
nWhen Horizon Client was installed, the USB Redirection component must have been installed. If you
did not include this component in the installation, uninstall the client and run the installer again to
include the USB Redirection component.
Procedure
nManually connect the USB device to a remote desktop.
a Connect the USB device to your local client system.
b From the VMware Horizon Client menu bar, click Connect USB Device.
c Select the USB device.
The device is manually redirected from the local system to the remote desktop.
nConnect the USB device to a remote hosted application.
a In the desktop and application selector window, open the remote application.
The name of the application is the name that your administrator has congured for the application.
b In the desktop and application selector window, right-click the application icon and select .
c In the left pane, select USB Devices.
d In the right pane, select the USB device and click Connect.
Using VMware Horizon Client for Windows
84 VMware, Inc.
e Select the application, and click OK.
N The name of the application in the list comes from the application itself and might not
match the application name that your administrator congured to appear in the desktop and
application selector window.
You can now use the USB device with the remote application. After you close the application, the
USB device is not released right away.
f When you are nished using the application, to release the USB device so that you can access it
from your local system, in the desktop and application selector window, open the Seings window
again, select USB Devices, and select Disconnect.
nCongure Horizon Client to connect USB devices automatically to the remote desktop when you plug
them in to the local system.
Use the autoconnect feature if you plan to connect devices that use MTP drivers, such as Android-based
Samsung smart phones and tablets.
a Before you plug in the USB device, start Horizon Client and connect to a remote desktop.
b From the VMware Horizon Client menu bar, select Connect USB Device > Autoconnect USB
Devices when Inserted.
c Plug in the USB device.
USB devices that you connect to your local system after you start Horizon Client are redirected to the
remote desktop.
nCongure Horizon Client to connect USB devices automatically to the remote desktop when
Horizon Client starts.
a From the VMware Horizon Client menu bar, select Connect USB Device > Autoconnect USB
Devices at Startup.
b Plug in the USB device and restart Horizon Client.
USB devices that are connected to the local system when you start Horizon Client are redirected to the
remote desktop.
The USB device appears in the desktop. A USB device might take up to 20 seconds to appear in the desktop.
The rst time you connect the device to the desktop you might be prompted to install drivers.
If the USB device does not appear in the desktop after several minutes, disconnect and reconnect the device
to the client computer.
What to do next
If you have problems with USB redirection, see the topic about troubleshooting USB redirection problems in
the Seing Up Desktop and Application Pools in View document.
Configure Clients to Reconnect When USB Devices Restart
If you do not congure Horizon Client to automatically connect USB devices to your View desktop, you can
still congure Horizon Client to reconnect to specic devices that occasionally restart. Otherwise, when a
device restarts during an upgrade, the device will connect to the local system rather than to the View
desktop.
If you plan to aach a USB device such as a smart phone or tablet, which is automatically restarted during
operating system upgrades, you can set Horizon Client to reconnect that specic device to the View desktop.
To perform this task, you edit a conguration le on the client.
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 85
If you use the Automatically Connect When Inserted option in Horizon Client, all devices that you plug in
to the client system get redirected to the View desktop. If you do not want all devices to be connected, use
the following procedure to congure Horizon Client so that only certain USB devices get automatically
reconnected.
Prerequisites
Determine the hexadecimal format of the vendor ID (VID) and product ID (PID) of the device. For
instructions see the VMware KB article at hp://kb.vmware.com/kb/1011600.
Procedure
1 Use a text editor to open the config.ini le on the client.
OS Version File Path
Windows 7 or 8.x C:\ProgramData\VMware\VMware USB Arbitration
Service\config.ini
Windows XP C:\Documents and Settings\All Users\Application
Data\VMware\VMware USB Arbitration Service\config.ini
2 Set the slow-reconnect property for the specic device or devices.
usb.quirks.device0 = "vid:pid slow-reconnect"
Here, vid:pid represent the vendor ID and product ID, in hexadecimal format, for the device. For
example, the following lines set this property for two USB devices:
usb.quirks.device0 = "0x0529:0x0001 slow-reconnect"
usb.quirks.device1 = "0x0601:0x0009 slow-reconnect"
Specify the usb.quirks.deviceN device properties in order, starting from 0. For example, if the line
usb.quirks.device0 is followed by a line with usb.quirks.device2 rather than usb.quirks.device1,
only the rst line is read.
When devices such as smart phones and tablets undergo a rmware or operating system upgrade, the
upgrade will succeed because the device will restart and connect to the View desktop that manages it.
Using the Real-Time Audio-Video Feature for Webcams and
Microphones
With the Real-Time Audio-Video feature, you can use your local computer's webcam or microphone on your
remote desktop. Real-Time Audio-Video is compatible with standard conferencing applications and
browser-based video applications, and supports standard webcams, audio USB devices, and analog audio
input.
For information about seing up the Real-Time Audio-Video feature and conguring the frame rate and
image resolution in a remote desktop, see the VMware Horizon View Feature Pack Installation and
Administration document (for View 5.3.x desktops) or the Seing Up Desktop and Application Pools in View
document (for Horizon 6.0 with View and later desktops). For information about conguring these seings
on client systems, see the VMware knowledge base article Seing Frame Rates and Resolution for Real-Time
Audio-Video on Horizon View Clients, at hp://kb.vmware.com/kb/2053644.
To download a test application that veries the correct installation and operation of the Real-Time Audio-
Video functionality, go to hp://labs.vmware.com/ings/real-time-audio-video-test-application. This test
application is available as a VMware ing, and therefore no technical support is available for it.
Using VMware Horizon Client for Windows
86 VMware, Inc.
When You Can Use Your Webcam
If a View administrator has congured the Real-Time Audio-Video feature, and if you use the VMware Blast
display protocol or the PCoIP display protocol, a webcam that is built-in or connected to your local
computer can be used on your desktop. You can use the webcam in conferencing applications such as Skype,
Webex, or Google Hangouts.
During the setup of an application such as Skype, Webex, or Google Hangouts on your remote desktop, you
can choose input and output devices from menus in the application. For virtual machine desktops, you can
choose VMware Virtual Microphone and VMware Virtual Webcam. For RDS desktops, you can choose
Remote Audio Device and VMware Virtual Webcam.
With many applications, however, this feature will just work, and selecting an input device will not be
necessary.
If the webcam is currently being used by your local computer it cannot be used by the remote desktop
simultaneously. Also, if the webcam is being used by the remote desktop it cannot be used by your local
computer at the same time.
I If you are using a USB webcam, do not connect it from the Connect USB Device menu in
Horizon Client. To do so routes the device through USB redirection, and the performance will be unusable
for video chat.
If you have more than one webcam connected to your local computer, you can congure a preferred
webcam to use on your remote desktop.
Select a Preferred Webcam or Microphone on a Windows Client System
With the Real-Time Audio-Video feature, if you have multiple webcams or microphones on your client
system, only one of them is used on your remote desktop or application. To specify which webcam or
microphone is preferred, you can congure Real-Time Audio-Video seings in Horizon Client.
The preferred webcam or microphone is used on the remote desktop or application if it is available, and if
not, another webcam or microphone is used.
With the Real-Time Audio-Video feature, video devices, audio input devices, and audio output devices
work without requiring the use of USB redirection, and the amount of network bandwidth required is
greatly reduced. Analog audio input devices are also supported.
N If you are using a USB webcam or microphone, do not connect it from the Connect USB Device
menu in Horizon Client. To do so routes the device through USB redirection, so that the device cannot use
the Real-Time Audio-Video feature.
Prerequisites
nVerify that you have a USB webcam, or USB microphone or other type of microphone, installed and
operational on your client system.
nVerify that you are using the VMware Blast display protocol or the PCoIP display protocol for your
remote desktop or application.
nConnect to a server.
Procedure
1 Open the Seings dialog box and select Real-Time Audio-Video in the left pane.
You can open the Seings dialog box by clicking the  (gear) icon in the upper right corner of the
desktop and application screen, or by right-clicking a desktop or application icon and selecting
.
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 87
2 Select the preferred webcam from the Preferred webcam drop-down menu and the preferred
microphone from the Preferred microphone drop-down menu.
The drop-down menus show the available webcams and microphones on the client system.
3 Click OK or Apply to save your changes.
The next time you start a remote desktop or application, the preferred webcam and microphone that you
selected are redirected to the remote desktop or application.
Copying and Pasting Text and Images
By default, you can copy and paste text from your client system to a remote desktop or application. If a View
administrator enables the feature, you can also copy and paste text from a remote desktop or application to
your client system or between two remote desktops or applications. Supported le formats include text,
images, and RTF (Rich Text Format). Some restrictions apply.
If you use the VMware Blast display protocol or the PCoIP display protocol, a View administrator can set
this feature so that copy and paste operations are allowed only from your client system to a remote desktop
or application, or only from a remote desktop or application to your client system, or both, or neither.
View administrators congure the ability to copy and paste by conguring group policy seings that pertain
to Horizon Agent. Depending on the Horizon server and agent version, administrators might also be able to
use group policies to restrict clipboard formats during copy and paste operations or use Smart Policies to
control copy and paste behavior in remote desktops. For more information, see the Seing Up Desktop and
Application Pools in View document.
In Horizon 7 version 7.0 and earlier and Horizon Client 4.0 and earlier, the clipboard can accommodate 1
MB of data for copy and paste operations. In Horizon 7 version 7.0.1 and later and Horizon Client 4.1 and
later, the clipboard memory size is congurable for both the server and the client. When a PCoIP or VMware
Blast session is established, the server sends its clipboard memory size to the client. The eective clipboard
memory size is the lesser of the server and client clipboard memory size values.
If you are copying formaed text, some of the data is text and some of the data is formaing information. If
you copy a large amount of formaed text or text and an image, when you aempt to paste the text and
image, you might see some or all of the plain text but no formaing or image. The reason is that the three
types of data are sometimes stored separately. For example, depending on the type of document you are
copying from, images might be stored as images or as RTF data.
If the text and RTF data together use less than maximum clipboard size, the formaed text is pasted. Often
the RTF data cannot be truncated, so that if the text and formaing use more than the maximum clipboard
size amount, the RTF data is discarded, and plain text is pasted.
If you are unable to paste all of the formaed text and images you selected in one operation, you might need
to copy and paste smaller amounts in each operation.
You cannot copy and paste les between a remote desktop and the le system on your client computer.
Configuring the Client Clipboard Memory Size
In Horizon 7 version 7.0.1 and later and Horizon Client 4.1 and later, the clipboard memory size is
congurable for both the server and the client.
When a PCoIP or VMware Blast session is established, the server sends its clipboard memory size to the
client. The eective clipboard memory size is the lesser of the server and client clipboard memory size
values.
Using VMware Horizon Client for Windows
88 VMware, Inc.
To set the clipboard memory size, modify the Windows registry value HKLM\Software\VMware, Inc.\VMware
VDPService\Plugins\MKSVchan\ClientClipboardSize. The value type is REG_DWORD. The value is specied
in KB. If you specify 0 or do not specify a value, the default client clipboard memory size is 8192 KB (8 MB).
A large clipboard memory size can negatively aect performance, depending on your network. VMware
recommends that you do not set the clipboard memory size to a value greater than 16 MB.
Using Remote Applications
Remote applications look and feel like applications that are installed on your client PC or laptop.
nYou can minimize and maximize a remote application through the application. When a remote
application is minimized, it appears in the taskbar of your client system. You can also minimize and
maximize the remote application by clicking its icon in the taskbar.
nYou can quit a remote application through the application or by right-clicking its icon in the taskbar.
nYou can press Alt+Tab to switch between open remote applications.
nIf a remote application creates a Windows System Tray item, that item also appears in the system tray
on your Windows client computer. By default, the system tray icons only appear to show notications,
but you can customize this behavior just as you do with natively installed applications.
N If you open the Control Panel to customize the notication area icons, the names of the icons for
remote applications are listed as VMware Horizon Client - application name.
Saving Documents in a Remote Application
With certain remote applications, such as Microsoft Word or WordPad, you can create and save documents.
Where these documents are saved depends on your company's network environment. For example, your
documents might be saved to a home share mounted on your local computer.
Administrators can use an ADMX template le to set a group policy that species where documents are
saved. This policy is called "Set Remote Desktop Services User Home Directory." For more information, see
the "RDS Proles Seings" topic in the Seing Up Desktop and Application Pools in View document.
Printing from a Remote Desktop or Application
From a remote desktop, you can print to a virtual printer or to a USB printer that is aached to your client
computer. Virtual printing and USB printing work together without conict.
You can use the virtual printing feature with the following types of remote desktops and applications:
nRemote desktops that run Windows Server operating systems
nSession-based desktops (on virtual machine RDS hosts)
nRemote hosted applications
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 89
Set Printing Preferences for the Virtual Printer Feature on a Remote Desktop
The virtual printing feature lets end users use local or network printers from a remote desktop without
requiring that additional print drivers be installed in the remote desktop. For each printer available through
this feature, you can set preferences for data compression, print quality, double-sided printing, color, and so
on.
After a printer is added on the local computer, Horizon Client adds that printer to the list of available
printers on the remote desktop. No further conguration is required. Users who have administrator
privileges can still install printer drivers on the remote desktop without creating a conict with the virtual
printer component.
I This feature is not available for the following types of printers:
nUSB printers that are using the USB redirection feature to connect to a virtual USB port in the remote
desktop
You must disconnect the USB printer from the remote desktop in order to use the virtual printing
feature with it.
nThe Windows feature for printing to a le
Selecting the Print to  check box in a Print dialog box does not work. Using a printer driver that
creates a le does work. For example, you can use a PDF writer to print to a PDF le.
This procedure is wrien for a remote desktop that has a Windows 7 or Windows 8.x (Desktop) operating
system. The procedure is similar but not exactly the same for Windows Server 2008 and Windows Server
2012.
Prerequisites
Verify that the Virtual Printing component of the agent is installed on the remote desktop. In the remote
desktop le system, verify that the following folder exists: C:\Program Files\Common Files\ThinPrint.
To use virtual printing, the View administrator must have enabled the virtual printing feature for the remote
desktop. This task includes enabling the Virtual Printing setup option in the agent installer, and can include
seing policies regarding virtual printing behavior. For more information, see the View Administration
document if you are using Connection Server and View Agent 5.x or an earlier version. See Seing Up
Desktop and Application Pools in View if you are using Horizon 6 or later.
Procedure
1 In the Windows 7 or Windows 8.x remote desktop, click Start > Devices and Printers.
2 In the Devices and Printers window, right-click the default printer, select Printer Properties from the
context menu, and select the printer.
Virtual printers appear as <printer_name> in single-user virtual machine desktops and as
<printer_name>(s<session_ID>) in session-based desktops on RDS hosts if View Agent 6.2 or later, or
Horizon Agent 7.0 or later, is installed. If View Agent 6.1 or earlier is installed in the remote desktop,
virtual printers appear as <printer_name>#:<number>.
3 In the Printer Properties window, click the Device Setup tab and specify which seings to use.
4 On the General tab, click Preferences and specify which seings to use.
5 In the Printing Preferences dialog box, select the dierent tabs and specify which seings to use.
For the Page Adjustment advanced seing, VMware recommends that you retain the default seings.
6 Click OK.
Using VMware Horizon Client for Windows
90 VMware, Inc.
7 To use custom paper forms, dene the forms on the client.
a Go to Control Panel > Hardware and Sound > Devices and Printers.
b Select the printer and click Print Server Properties at the top of the screen.
c On the Forms tab, specify the seings and click Save Form.
This form will now be available in the remote desktop.
Using USB Printers
In an View environment, virtual printers and redirected USB printers can work together without conict.
A USB printer is a printer that is aached to a USB port on the local client system. To send print jobs to a
USB printer, you can either use the USB redirection feature or use the virtual printing feature. USB printing
can sometimes be faster than virtual printing, depending on network conditions.
nYou can use the USB redirection feature to aach a USB printer to a virtual USB port in the remote
desktop as long as the required drivers are also installed on the remote desktop.
If you use this redirection feature the printer is no longer logically aached to the physical USB port on
the client and this is why the USB printer does not appear in the list of local printers on the local client
machine. This also means that you can print to the USB printer from the remote desktop but not from
the local client machine.
In the remote desktop, redirected USB printers appear as <printer_name>.
For information about how to connect a USB printer, see “Connect USB Devices,” on page 83.
nOn some clients, you can alternatively use the virtual printing feature to send print jobs to a USB
printer. If you use the virtual printing feature you can print to the USB printer from both the remote
desktop and the local client, and you do not need to install print drivers on the remote desktop.
Control Adobe Flash Display
The View administrator can set Adobe Flash content to display in your View desktop at a level designed to
conserve computing resources. In some cases, these seings can result in low playback quality. By moving
the mouse pointer into the Adobe Flash content, you can override the Adobe Flash seings that your View
administrator species.
Adobe Flash display control is available for Internet Explorer sessions on Windows only, and for Adobe
Flash versions 9 and 10 only. To control Adobe Flash display quality, Adobe Flash must not be running in
full screen mode.
Procedure
1 From Internet Explorer in the View desktop, browse to the relevant Adobe Flash content and start it if
necessary.
Depending on how your View administrator congured Adobe Flash seings, you might notice
dropped frames or low playback quality.
2 Move the mouse pointer into the Adobe Flash content while it is playing.
Display quality is improved as long as the cursor remains in the Adobe Flash content.
3 To retain the improvement in quality, double-click inside the Adobe Flash content.
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 91
Clicking URL Links That Open Outside of Horizon Client
An administrator can congure URL links that you click inside a remote desktop or application to open in
the default browser on your client system. A link might be to a Web page, a phone number, an email
address, or other type of link. This feature is called URL Content Redirection.
An administrator can also congure URL links that you click inside a browser or application on your client
system to open in a remote desktop or application. In this scenario, if Horizon Client is not already open, it
starts and prompts you to log in.
An administrator might set up the URL Content Redirection feature for security purposes. For example, if
you are inside your company network and click a link that points to a URL that is outside the network, the
link might be more safely opened in a remote application. An administrator can congure which application
opens the link.
Each company congures its own URL redirection policies. If you have questions about how the URL
Content Redirection feature behaves at your company, contact a system administrator.
Using the Relative Mouse Feature for CAD and 3D Applications
If you use the Blast Extreme display protocol or the PCoIP display protocol when using CAD or 3D
applications in a View 5.2 or later desktop, mouse performance improves when you enable the relative
mouse feature.
In most circumstances, if you are using applications that do not require 3D rendering, Horizon Client
transmits information about mouse pointer movements by using absolute coordinates. Using absolute
coordinates, the client renders the mouse movements locally, which improves performance, especially if you
are outside the corporate network.
For work that requires using graphics-intensive applications, such as AutoCAD, or for playing 3D video
games, you can improve mouse performance by enabling the relative mouse feature, which uses relative,
rather than absolute, coordinates. To use this feature, select Options > Enable Relative Mouse from the
Horizon Client menu bar.
N If you use Horizon Client in windowed mode, rather than full screen mode, and the relative mouse
feature is enabled, you might not be able to move the mouse pointer to the Horizon Client menu options or
move the pointer outside of the Horizon Client window. To resolve this situation, press Ctrl+Alt.
When the relative mouse feature is enabled, performance might be slow if you are outside the corporate
network, on a WAN.
I This feature requires a View 5.2 or later desktop, and you must turn on 3D rendering for the
desktop pool. For more information about pool seings and the options available for 3D rendering, see the
View Administration document if you are using Vew Connection Server and Agent 5.x or an earlier version.
See Seing Up Desktop and Application Pools in View if you are using View Connection Server and Agent 6.0 or
later.
Using Scanners
You can scan information into your remote desktops and applications with scanners that are connected to
your local client system. This feature redirects scanning data with a signicantly lower bandwidth than can
be achieved by using USB redirection.
Scanner redirection supports standard scanning devices that are compatible with the TWAIN and WIA
(Windows Image Acquisition) formats. Although you must have the scanner device drivers installed on the
client system, you do not need to install the scanner device drivers on the remote desktop operating system
where the agent is installed.
Using VMware Horizon Client for Windows
92 VMware, Inc.
If a View administrator has congured the scanner redirection feature, and if you use the Blast Extreme
display protocol or the PCoIP display protocol, a scanner connected to your local system can be used in a
remote desktop or application.
I If you are using a scanner, do not connect it from the Connect USB Device menu in
Horizon Client. To do so routes the device through USB redirection, and the performance will be unusable.
When scanning data is redirected to a remote desktop or application, you cannot access the scanner on the
local computer. Conversely, when a scanner is in use on the local computer, you cannot access it on the
remote desktop or application.
Tips for Using the Scanner Redirection Feature
nClick the scanner icon ( ) in the system tray, or notication area, of the remote desktop to select a non-
default scanner or to change conguration seings. On RDS applications, the system tray icon is
redirected to the local client computer.
You do not have to use the menu that appears when you click this icon. Scanner redirection works
without any further conguration. The icon menu allows you to congure options such as changing
which device to use if more than one device is connected to the client computer.
N If the menu that appears does not list any scanners it means that an incompatible scanner is
connected to the client computer. If the scanner icon is not present, it means that the scanner redirection
feature is disabled or not installed on the remote desktop. Also, this icon does not appear on Mac or
Linux client systems because the feature is not supported on those systems.
nClick the Preferences option in the menu to select options to control image compression, hide webcams
from the scanner redirection menu, and determine how to select the default scanner.
You can select the option to hide webcams if you plan to use the Real-Time Audio-Video feature to
redirect webcams, which is what VMware recommends. Use scanner redirection with webcams to take
a photograph of yourself and scan it.
N If you congure scanner redirection to use a specic scanner and that scanner is not available,
scanner redirection will not work.
nAlthough most TWAIN scanners display the a scanner seings dialog box by default, some do not. For
those that do not display seings options, you can use the Preferences option in the scanner icon menu,
and select Always show Scanner  dialog option.
nScanning too large an image or scanning at too high a resolution might not work. In this case, you
might see the scanning progress indicator freeze, or the scanner application might exit unexpectedly. If
you minimize the View desktop, an error message might appear on your client system, notifying you
that the resolution is set too high. To resolve this issue, reduce the resolution or crop the image to a
smaller size and scan again.
Using Serial Port Redirection
With this feature, users can redirect locally connected, serial (COM) ports such as built-in RS232 ports or
USB-to-serial adapters. Devices such as printers, bar code readers, and other serial devices can be connected
to these ports and used in the remote desktops.
If a View administrator has congured the serial port redirection feature, and if you use the VMware Blast
Extreme or the PCoIP display protocol, serial port redirection works on your remote desktop without
further conguration. For example, COM1 on the local client system is redirected as COM1 on the remote
desktop. COM2 is redirected as COM2, unless the COM port is already in use. If so the COM port is mapped
to avoid conicts. For example, if COM1 and COM2 already exist on the remote desktop, COM1 on the
client is mapped to COM3 by default.
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 93
Although you must have any required device drivers installed on the client system, you do not need to
install the device drivers on the remote desktop operating system where the agent is installed. For example,
if you use a USB-to-serial adapter that requires specic device drivers to work on your local client system,
you must install those drivers but only on the client system.
I If you are using a device that plugs in to a USB-to-serial adapter, do not connect the device
from the Connect USB Device menu in Horizon Client. To do so routes the device through USB redirection,
and bypasses the serial port redirection functionality.
Tips for Using the Serial Port Redirection Feature
nClick the serial port icon ( ) in the system tray, or notication area, of the remote desktop to connect,
disconnect, and customize the mapped COM ports.
When you click the serial port icon, the Serial COM Redirection for VMware Horizon context menu
appears.
N If the items in the context menu are grayed out, it means that the administrator has locked the
conguration. Also note that the icon appears only if you use the required versions of the agent and
Horizon Client for Windows, and you must connect over Blast Extreme or PCoIP. The icon does not
appear if you connect to a remote desktop from a Mac, Linux, or mobile client.
nIn the context menu, the port items are listed using the following format, for example: COM1 mapped
to COM3. The rst port, which is COM1 in this example, is the physical port or the USB-to-serial
adapter used on the local client system. The second port, which is COM3 in this example, is the port
used in the virtual desktop.
nRight-click a COM port to select the Port Properties command.
In the COM Properties dialog box, you can congure a port to connect automatically when a remote
desktop session is started, or you can ignore DSR (that is, ignore the data-set-ready signal), which is
required for some modems and other devices.
You can also change the port number used in the remote desktop. For example, if the COM1 port on the
client is mapped to COM3 in the remote desktop, but the application you are using requires COM1, you
can change the port number to COM1. If COM1 already exists in the remote desktop, you might see
COM1 (Overlapped). You can still use this overlapped port. The remote desktop can receive serial data
through the port from the ESXi host and also from the client system.
nMake sure you connect to a mapped COM port before you aempt to launch an application that
requires access to this port. For example, right-click a COM port and select Connect to use the port in
the remote desktop. When you launch the application, the application opens the serial port.
When a redirected COM port is opened and in use on a remote desktop, you cannot access the port on
the local computer. Conversely, when a COM port is in use on the local computer, you cannot access the
port on the remote desktop.
nIn the remote desktop, you can use the Windows Device Manager Port  tab to set the default
Baud rate for a particular COM port. Be sure to use the same seings in the Windows Device Manager
on your client system. Note that the seings from this tab are used only if the application does not
specify the port seings.
nBefore you can disconnect the COM port, you must close the port in the application or close the
application. You can then select the Disconnect command to disconnect and make the physical COM
port available for use on the client computer.
Using VMware Horizon Client for Windows
94 VMware, Inc.
nIf you congure a serial port to connect automatically, launch an application that opens the serial port,
and then disconnect and resonnect the desktop session, the auto-connect feature does not work. You
also cannot connect using the serial port's system tray icon's menu option. In most cases, the application
can no longer use the serial port. This is expected behavior. You must terminate the application,
disconnect the desktop session and reconnect again to resolve the problem.
Keyboard Shortcuts
You can use keyboard shortcuts for menu commands and common actions.
Shortcuts That Work the Same Way in Horizon Client as in All Applications
Table 5‑4. Common Keyboard Shortcuts
Action Key or Key Combination
Click the highlighted buon in a dialog box. Press Enter.
Invoke the context menu. Press Shift+F10.
Click the Cancel buon in a dialog box. Press ESC.
Navigate between items in the server section window or
the desktop and applications selection window.
Use an arrow key to move in the direction of the arrow.
Press Tab to move to the right. Press Shift+Tab to move to
the left.
Delete an item from the server section window or the
desktop and applications selection window.
Press Delete.
In Windows 8.x, navigate between the Start screen and the
desktop screen
Press the Windows key.
Horizon Client Window (Server Selection List) Shortcuts
Table 5‑5. Key Combinations Specific to the Window Where You Specify Which Server to Connect To
Menu Command or Action Key Combination
Open the help system in a browser window Alt+O+H, Ctrl+H
New Server command Alt+N
Display the Support Information window Alt+O+S
Display the About Horizon Client window Alt+O+V
 SSL command Alt+O+O
Hide selector after launching an item command Alt+O+I
Remote Desktop and Application Selector Shortcuts
Table 5‑6. Keys and Key Combinations to Use in the Desktop and Application Selection Window
Menu Command or Action Key Combination
Open the help system in a browser window Alt+O+H, Ctrl+H
Display Options menu Alt+O
Display the Support Information window Alt+O+S
Display the About Horizon Client window Alt+O+V
Log o from the remote desktop Shift+F10+O
Disconnect and log o from the server Alt+D
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 95
Table 5‑6. Keys and Key Combinations to Use in the Desktop and Application Selection Window
(Continued)
Menu Command or Action Key Combination
Toggle between Show Favorites and Show All Alt+F
While showing favorites, after typing the rst few
characters of the application or desktop name, go to the
next item that matches the search
F4
While showing favorites, go to the previous item that
matches the search
Shift+F4
Mark as a favorite or remove favorite designation Shift+F10+F
Display  menu Alt+S, or Shift+F10+S
Launch the selected item Enter, or Shift+F10+L
Pin a shortcut for the remote desktop or application to the
client system's Start menu (for Windows 7 and earlier) or
the Start screen (for Windows 8.x)
Shift+F10+A
Display the Display Seings context menu for the selected
remote desktop
Shift+F10+D
Use the PCoIP display protocol to connect to the selected
remote desktop
Shift+F10+P
Use the RDP display protocol to connect to the selected
remote desktop
Shift+F10+M
Create a desktop shortcut for the selected item Shift+F10+C
Add the selected item to your Start menu or Start screen Shift+F10+A
Reset the selected desktop (if your administrator allows
you to reset)
Shift+F10+R
Refresh the desktop and application list F5
Desktop Window (with a PCoIP or VMware Blast Extreme Session) Shortcuts
These shortcuts work if you rst press Ctrl+Alt or click on the Horizon Client menu bar, rather than inside
the remote desktop operating system, before you press the keys.
Table 5‑7. Key Combinations for PCoIP and VMware Blast Sessions
Menu Command or Action Key Combination
Release the mouse cursor so that it is no longer inside the
remote desktop operating system
Ctrl+Alt
Display Options menu Alt+O
Display the Support Information window Alt+O+M
Display the About Horizon Client window Alt+O+V
Invoke the Share Folders Seings dialog Alt+O+F
Toggle Enable display scaling Alt+O+N
Switch to Other Desktop command Alt+O+S
Autoconnect to this Desktop command Alt+O+A
Enable Relative Mouse command Alt+O+E
Send Ctrl+Alt+Del command Alt+O+C
Disconnect command Alt+O+D
Using VMware Horizon Client for Windows
96 VMware, Inc.
Table 5‑7. Key Combinations for PCoIP and VMware Blast Sessions (Continued)
Menu Command or Action Key Combination
Disconnect and Log  command Alt+O+L
Connect USB Device command Alt+U
Chapter 5 Working in a Remote Desktop or Application
VMware, Inc. 97
Using VMware Horizon Client for Windows
98 VMware, Inc.
Troubleshooting Horizon Client 6
You can solve most problems with Horizon Client by reseing the desktop or by reinstalling the
VMware Horizon Client application.
This chapter includes the following topics:
n“Problems with Keyboard Input,” on page 99
n“What to Do If Horizon Client Exits Unexpectedly,” on page 99
n“Reset a Remote Desktop or Application,” on page 100
n“Uninstalling Horizon Client,” on page 100
Problems with Keyboard Input
If, when you type in a remote desktop or application, none of the keystrokes seem to work, the issue might
be with security software on your local client system.
Problem
While connected to a remote desktop or application, no characters appear when you type. Another
symptom might be that a single key keeps repeating itself.
Cause
Some security software, such as Norton 360 Total Security, includes a feature that detects keylogger
programs and blocks keystroke logging. This security feature is meant to protect the system against
unwanted spyware that, for example, steals passwords and credit card numbers. Unfortunately, this security
software might block Horizon Client from sending keystrokes to the remote desktop or application.
Solution
uOn the client system, turn o the keylogger detection feature of your antivirus or security software.
What to Do If Horizon Client Exits Unexpectedly
Horizon Client might exit even if you do not close it.
Problem
Horizon Client might exit unexpectedly. Depending on your View Connection Server conguration, you
might see a message such as There is no secure connection to the View Connection Server. In some
cases, no message is displayed.
Cause
This problem occurs when the connection to View Connection Server is lost.
VMware, Inc. 99
Solution
uRestart Horizon Client. You can connect successfully as soon as View Connection Server is running
again. If you continue to have connection problems, contact your View administrator.
Reset a Remote Desktop or Application
You might need to reset a desktop or application if the application or desktop operating system stops
responding. Reseing a remote desktop shuts down and restarts the desktop. Reseing your remote
applications quits the applications. Unsaved data is lost.
Reseing a remote desktop is the equivalent of pressing the Reset buon on a physical PC to force the PC to
restart. Any les that are open on the remote desktop will be closed without being saved rst.
Reseing applications is the equivalent of quiing all remote applications without saving any unsaved data.
All open applications are closed, even if the applications come from dierent RDS server farms.
You can reset a remote desktop only if your administrator has enabled this feature.
Procedure
1 To reset a remote desktop, use the Reset Desktop command.
Option Action
From within the desktop OS Select Options > Reset Desktop from the menu bar.
From the desktop and application
selection window
Right-click the desktop icon and select Reset Desktop.
2 To reset your applications, use the Reset buon in the desktop and application selection window.
a Click the  buon (gear icon) in the menu bar.
b Select Applications in the left pane, click the Reset buon in the right pane, and click OK.
For a remote desktop, the operating system in the remote desktop is rebooted. The client disconnects from
the desktop. For remote applications, the applications are quit.
What to do next
Wait an appropriate amount of time for system startup before aempting to connect to the remote desktop.
Uninstalling Horizon Client
You can sometimes resolve problems with Horizon Client by uninstalling and reinstalling the
Horizon Client application.
You uninstall Horizon Client by using the same method that you usually use to uninstall any other
application.
For example, use the Add or Remove Programs applet available in your Windows operating system to
remove the VMware Horizon Client application.
After uninstalling is complete, you can reinstall the application.
See Chapter 2, “Installing Horizon Client for Windows,” on page 23.
Using VMware Horizon Client for Windows
100 VMware, Inc.
Index
Numerics
3D applications 92
A
ADM template files, View components 42
Adobe Flash video, control 91
Adobe Media Server 15
agent, installation requirements 18
application reconnection behavior 41
autoconnect USB devices 83
C
CAD applications 92
certificates, ignoring problems 39, 40
client drive redirection 66
client installer 23
client software requirements 9
client-side GPOs 42
clipboard memory size 88
COM ports, redirecting serial 12, 93
configuration settings 33
configuring Horizon Client 33
connect
to a desktop 63
to View Connection Server 63
USB devices 83, 85
Connection Server 19
control, Adobe Flash video display 91
copying text and images 88
customer experience program, desktop pool
data 20
D
desktop
connect to 63
display options 63
display protocol 63
log off from 70
reset 100
switch 70
desktop and application selector 66
device authentication, requirements 18
devices, connecting USB 83, 85
disconnecting from a remote desktop 70
display options, desktop 63
display protocol, desktop 63
display mode for monitors 82
display protocols
Microsoft RDP 73
View PCoIP 73
display scaling 81
domain 63
DPI synchronization 81
F
favorites 66
feature support matrix 73
FIPS mode 23
Flash Redirection 14
Flash URL Redirection, system requirements 15
folder sharing 66
G
GPO settings, general 49
group policies 42
H
hardware requirements
for Windows systems 10
smart card authentication 17
hiding the Horizon Client window 68
Horizon Clients, upgrading 30
Horizon Client
configuration file 60
disconnect from a desktop 70
exits unexpectedly 99
running from the command line 57
troubleshooting 99
I
icons on the desktop and application selector 66
images, copying 88
IME (input method editor) 77
K
keyboard shortcuts 95
keyboards, onscreen 78
keyloggers 99
L
log in, View Connection Server 63
VMware, Inc. 101
log off 70
M
media file formats, supported 13
Microsoft Lync support 16
Microsoft RDP 73, 78
Microsoft Windows Installer
command-line options for silent installation 28
properties for View Client 27
multimedia redirection (MMR) 13
multiple monitors 78–80
N
nested mode 77
O
onscreen keyboards 78
operating systems, supported on the agent 18
options
display protocol 63
screen layout 63
P
pasting text and images 88
PCoIP 73
PCoIP client session variables 54
preferences, desktop 63
preferred microphone 87
preferred webcam 87
prerequisites for client devices 19
print from a desktop 89
printers, setting up 90
R
RDP GPO settings 47
Real-Time Audio-Video, system requirements 11
registry
settings equivalent to command-line
commands 60
settings for View Client 60
relative mouse 92
remote applications 89
reset desktop 100
S
saving documents in a remote application 89
scanner redirection 12, 92
screen layout 63
security servers 19
security settings GPOs 44
serial port redirection 12, 93
server connections 63
server certificate verification 39
sharing files and folders from the client
system 66
shortcut keys 95
shortcuts, for remote desktops and
applications 69
silent installation, View Client 25
smart card authentication, requirements 17
SSL certificates, verifying 39
SSL options 41
streaming multimedia 13
switch desktops 70
system requirements, for Windows 10
T
text, copying 88
thin client support 73
ThinPrint setup 90
timeouts 69
TWAIN scanners 12, 92
U
Unified Communications 16
uninstalling Horizon Client 100
upgrading Horizon Client 30
URI examples 37
URI syntax for Horizon Clients 34
URIs (uniform resource identifiers) 34
URL Content Redirection 15, 92
USB devices
setting GPOs for 42
using with View desktops 73
USB settings, GPOs 51
USB printers 89, 91
V
vdm_client.adm file for setting GPOs 42
verification modes for certificate checking 39
View Client
command syntax 57
installing on a Windows PC or laptop 24
installing silently on a Windows PC or
laptop 25
registry settings 60
silent installation properties 27
system requirements for Windows 10
View Connection Server, connect to 63
virtual printers 89
virtual printing feature 73, 90
virtual profiles 73
VMware Blast 19
vmware-view command
configuration file 60
syntax 57
Using VMware Horizon Client for Windows
102 VMware, Inc.
VoIP (voice over IP) 16
W
webcam 86, 87
WIA scanners 12, 92
Windows, installing View Client on 10
Windows computers, installing View Client 24
Wyse MMR 73
Index
VMware, Inc. 103
Using VMware Horizon Client for Windows
104 VMware, Inc.

Navigation menu