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
By default, Horizon 7 blocks certain device families from being redirected to the remote desktop or
application. For example, HID (human interface devices) and keyboards are blocked from appearing in the
guest. Some released BadUSB code targets USB keyboard devices.
You can prevent specic device families from being redirected to the remote desktop or application. For
example, you can block all video, audio, and mass storage devices:
ExcludeDeviceFamily o:video;audio;storage
Conversely, you can create a whitelist by preventing all devices from being redirected but allowing a specic
device family to be used. For example, you can block all devices except storage devices:
ExcludeAllDevices Enabled
IncludeDeviceFamily o:storage
Another risk can arise when a remote user logs into a desktop or application and infects it. You can prevent
USB access to any Horizon 7 connections that originate from outside the company rewall. The USB device
can be used internally but not externally.
Be aware that if you block TCP port 32111 to disable external access to USB devices, time zone
synchronization will not work because port 32111 is also used for time zone synchronization. For zero
clients, the USB trac is embedded inside a virtual channel on UDP port 4172. Because port 4172 is used for
the display protocol as well as for USB redirection, you cannot block port 4172. If required, you can disable
USB redirection on zero clients. For details, see the zero client product literature or contact the zero client
vendor.
Seing policies to block certain device families or specic devices can help to mitigate the risk of being
infected with BadUSB malware. These policies do not mitigate all risk, but they can be an eective part of an
overall security strategy.
Using Log Files for Troubleshooting and to Determine USB Device IDs
Useful log les for USB are located on both the client system and the remote desktop operating system or
RDS host. Use the log les in both locations for troubleshooting. To nd product IDs for specic devices, use
the client-side logs.
If you are trying to congure USB device spliing or ltering, or if you are trying to determine why a
particular device does not appear in a Horizon Client menu, look in the client-side logs. Client logs are
produced for the USB arbitrator and the Horizon View USB Service. Logging on Windows and Linux clients
is enabled by default. On Mac clients, logging is disabled by default. To enable logging on Mac clients, see
the Using VMware Horizon Client for Mac document.
When you congure policies for spliing and ltering out USB devices, some values you set require the VID
(vendor ID) and PID (product ID) for the USB device. To nd the VID and PID, you can search on the
Internet for the product name combined with vid and pid. Alternatively, you can look in the client-side log
le after you plug in the USB device to the local system when Horizon Client is running. The following table
shows the default location of the log les.
Table 4‑2. Log File Locations
Client or Agent Path to Log Files
Windows client
%PROGRAMDATA%\VMware\VDM\logs\debug-*.txt
C:\Windows\Temp\vmware-SYSTEM\vmware-usbarb-*.log
Horizon Agent
%PROGRAMDATA%\VMware\VDM\logs\debug-*.txt
Chapter 4 Using USB Devices with Remote Desktops and Applications
VMware, Inc. 75