Configuring Remote Desktop Features
Table Of Contents
- Configuring Remote Desktop Features in Horizon 7
- Contents
- Configuring Remote Desktop Features in Horizon 7
- Configuring Remote Desktop Features
- Configuring Unity Touch
- Configuring Flash URL Redirection for Multicast or Unicast Streaming
- Configuring Flash Redirection
- Configuring Real-Time Audio-Video
- Configuration Choices for Real-Time Audio-Video
- System Requirements for Real-Time Audio-Video
- Ensuring That Real-Time Audio-Video Is Used Instead of USB Redirection
- Selecting Preferred Webcams and Microphones
- Select a Preferred Webcam or Microphone on a Windows Client System
- Select a Default Microphone on a Mac Client System
- Configuring Real-Time Audio-Video on a Mac Client
- Configure a Preferred Webcam or Microphone on a Mac Client System
- Select a Default Microphone on a Linux Client System
- Select a Preferred Webcam or Microphone on a Linux Client System
- Configuring Real-Time Audio-Video Group Policy Settings
- Real-Time Audio-Video Bandwidth
- Configuring Scanner Redirection
- Configuring Serial Port Redirection
- Managing Access to Windows Media Multimedia Redirection (MMR)
- Managing Access to Client Drive Redirection
- Configure Skype for Business
- Configuring URL Content Redirection
- Understanding URL Content Redirection
- Requirements for URL Content Redirection
- Using URL Content Redirection in a Cloud Pod Architecture Environment
- Installing Horizon Agent with the URL Content Redirection Feature
- Configuring Agent-to-Client Redirection
- Configuring Client-to-Agent Redirection
- Installing Horizon Client for Windows with the URL Content Redirection Feature
- Using the vdmutil Command-Line Utility
- Create a Local URL Content Redirection Setting
- Create a Global URL Content Redirection Setting
- Assign a URL Content Redirection Setting to a User or Group
- Test a URL Content Redirection Setting
- Managing URL Content Redirection Settings
- Using Group Policy Settings to Configure Client-to-Agent Redirection
- URL Content Redirection Limitations
- Unsupported URL Content Redirection Features
- Using USB Devices with Remote Desktops and Applications
- Limitations Regarding USB Device Types
- Overview of Setting Up USB Redirection
- Network Traffic and USB Redirection
- Automatic Connections to USB Devices
- Deploying USB Devices in a Secure Horizon 7 Environment
- Using Log Files for Troubleshooting and to Determine USB Device IDs
- Using Policies to Control USB Redirection
- Troubleshooting USB Redirection Problems
- Configuring Policies for Desktop and Application Pools
- Setting Policies in Horizon Administrator
- Using Smart Policies
- Using Active Directory Group Policies
- Using Horizon 7 Group Policy Administrative Template Files
- Horizon 7 ADMX Template Files
- Add the ADMX Template Files to Active Directory
- Horizon Agent Configuration ADMX Template Settings
- PCoIP Policy Settings
- VMware Blast Policy Settings
- Using Remote Desktop Services Group Policies
- Configure the RDS Per Device CAL Storage
- Add the Remote Desktop Services ADMX Files to Active Directory
- RDS Application Compatibility Settings
- RDS Connections Settings
- RDS Device and Resource Redirection Settings
- RDS Licensing Settings
- RDS Printer Redirection Settings
- RDS Profiles Settings
- RDS Connection Server Settings
- RDS Remote Session Environment Settings
- RDS Security Settings
- RDS Session Time Limits
- RDS Temporary Folders Settings
- Setting Up Location-Based Printing
- Active Directory Group Policy Example
- Active Directory Group Policy Example
- Index
Network Traffic and USB Redirection
USB redirection works independently of the display protocol (RDP or PCoIP) and USB trac usually uses
TCP port 32111.
Network trac between a client system and a remote desktop or application can travel various routes,
depending on whether the client system is inside the corporate network and how the administrator has
chosen to set up security.
1 If the client system is inside the corporate network, so that a direct connection can be made between the
client and desktop or application, USB trac uses TCP port 32111.
2 If the client system is outside the corporate network, the client can connect through a View security
server.
A security server resides within a DMZ and acts as a proxy host for connections inside your trusted
network. This design provides an additional layer of security by shielding the View Connection Server
instance from the public-facing Internet and by forcing all unprotected session requests through the
security server.
A DMZ-based security server deployment requires a few ports to be opened on the rewall to allow
clients to connect with security servers inside the DMZ. You must also congure ports for
communication between security servers and the View Connection Server instances in the internal
network.
For information on specic ports, see "Firewall Rules for DMZ-Based Security Servers" in the View
Architecture Planning Guide.
3 If the client system is outside the corporate network, you can use View Administrator to enable the
HTTPS Secure Tunnel. The client then makes a further HTTPS connection to the View Connection
Server or security server host when users connect to a remote desktop or application. The connection is
tunneled using HTTPS port 443 to the security server, and then the onward connection for USB trac
from the server to the remote desktop or application uses TCP port 32111. USB device performance is
slightly degraded when using this tunnel.
N If you are using a zero client, USB trac is redirected using a PCoIP virtual channel, rather than
through TCP 32111. Data is encapsulated and encrypted by the PCoIP Secure Gateway using TCP/UDP
port 4172. If you are using only zero clients, it is not necessary to open TCP port 32111.
Automatic Connections to USB Devices
On some client systems, administrators, end users, or both can congure automatic connections of USB
devices to a remote desktop. Automatic connections can be made either when the user plugs a USB device in
to the client system or when the client connects to the remote desktop.
Some devices, such as smart phones and tablets, require automatic connections because these devices are
restarted, and therefore disconnected, during an upgrade. If these devices are not set to automatically
reconnect to the remote desktop, during an upgrade, after the devices restart, they connect to the local client
system instead.
Conguration properties for automatic USB connections that administrators set on the client, or that end
users set by using a Horizon Client menu item, apply to all USB devices unless the devices are congured to
be excluded from USB redirection. For example, in some client versions, webcams and microphones are
excluded from USB redirection by default because these devices work beer through the Real-Time Audio-
Configuring Remote Desktop Features in Horizon 7
72 VMware, Inc.










