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
Table 5‑10. Horizon PCoIP Session Bandwidth Variables (Continued)
Setting Description
Configure the PCoIP session MTU
Species 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 aected by
this seing.
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 seing applies to Horizon Agent and the client. If the two
endpoints have dierent MTU size seings, the lowest size is used.
If this seing is disabled or not congured, the client uses the default
value in the negotiation with Horizon Agent.
Configure the PCoIP session audio
bandwidth limit
Species the maximum bandwidth that can be used for audio (sound
playback) in a PCoIP session.
The audio processing monitors the bandwidth used for audio. The
processing selects the audio compression algorithm that provides the
best audio possible, given the current bandwidth utilization. If a
bandwidth limit is set, the processing reduces quality by changing the
compression algorithm selection until the bandwidth limit is reached. If
minimum quality audio cannot be provided within the bandwidth limit
specied, audio is disabled.
To allow for uncompressed high quality stereo audio, set this value to
higher than 1600 kbit/s. A value of 450 kbit/s and higher allows for
stereo, high-quality, compressed audio. A value between 50 kbit/s and
450 kbit/s results in audio that ranges between FM radio and phone call
quality. A value below 50 kbit/s might result in no audio playback.
This seing applies to Horizon Agent only. You must enable audio on
both endpoints before this seing has any eect.
In addition, this seing has no eect on USB audio.
If this seing is disabled or not congured, a default audio bandwidth
limit of 500 kilobits per second is congured to constrain the audio
compression algorithm selected. If the seing is congured, the value is
measured in kilobits per second, with a default audio bandwidth limit
of 500 kilobits per second.
This seing applies to View 4.6 and later. It has no eect on earlier
versions of View.
When this seing is modied during an active PCoIP session, the
change takes eect immediately.
Turn off Build-to-Lossless feature
Species whether to turn the build-to-lossless feature of the PCoIP
protocol o or on. This feature is turned o by default.
If this seing is enabled or not congured, the build-to-lossless feature is
turned o, and images and other desktop and application content are
never built to a lossless state. In network environments with constrained
bandwidth, turning o the build-to-lossless feature can provide
bandwidth savings.
If this seing is disabled, the build-to-lossless feature is turned on.
Turning on the build-to-lossless feature is recommended in
environments that require images and other desktop and application
content to be built to a lossless state.
When this seing is modied during an active PCoIP session, the
change takes eect immediately.
For more information about the PCoIP build-to-lossless feature, see
“PCoIP Build-to-Lossless Feature,” on page 123.
Configuring Remote Desktop Features in Horizon 7
122 VMware, Inc.










