Configuring Remote Desktop Features

n
For Horizon Agent, se the Exclude VidPid From Split policy to o:vid-xxx_pid-yyyy, where xxx and
yyyy are the appropriate IDs.
Allow automatic device spliing for desktops and specify policies for spliing specic devices on client
computers:
n
For Horizon Agent, set the Allow Auto Device Splitting policy to Allow - Override Client Setting.
n
For the client device, set the Include Vid/Pid Device lter policy to include the specic device that you
want to split; for example, vid-0781_pid-554c.
n
For the client device, set the Split Vid/Pid Device policy to vid-0781_pid-554c(exintf:00;exintf:01)
for example, to split a specied composite USB device so that interface 00 and interface 01 are excluded
from redirection.
Configuring Filter Policy Settings for USB Devices
Filter policy seings that you congure for Horizon Agent and Horizon Client establish which USB devices
can be redirected from a client computer to a remote desktop or application. USB device ltering is often
used by companies to disable the use of mass storage devices on remote desktops, or to block a specic type
of device from being forwarded, such as a USB-to-Ethernet adapter that connects the client device to the
remote desktop.
When you connect to a desktop or application, Horizon Client downloads the Horizon Agent USB policy
seings and uses them in conjunction with the Horizon Client USB policy seings to decide which USB
devices it will allow you to redirect from the client computer.
Horizon 7 applies any device spliing policy seings before it applies the lter policy seings. If you have
split a composite USB device, Horizon 7 examines each of the device's interfaces to decide which should be
excluded or included according to the lter policy seings. If you have not split a composite USB device,
Horizon 7 applies the lter policy seings to the entire device.
The device spliing policies are included in the Horizon Agent Conguration ADMX template le
(vdm_agent.admx).
Interaction of Agent-Enforced USB Settings
The following table shows the modiers that specify how Horizon Client handles a Horizon Agent lter
policy seing for an agent-enforceable seing if an equivalent lter policy seing exists for Horizon Client.
Table 4‑7. Filter Modifiers for Agent-Enforceable Settings
Modifier Description
m (merge)
Horizon Client applies the Horizon Agent lter policy seing in addition to the
Horizon Client lter policy seing. In the case of Boolean, or true/false, seings, if the client
policy is not set, the agent seings are used. If the client policy is set, the agent seings are
ignored, except for the Exclude All Devices seing. If the Exclude All Devices policy
is set on the agent side, the policy overrides the client seing.
o (override)
Horizon Client uses the Horizon Agent lter policy seing instead of the Horizon Client
lter policy seing.
For example, the following policy on the agent side overrides any include rules on the client side, and only
device VID-0911_PID-149a will have an include rule applied:
IncludeVidPid: o:VID-0911_PID-149a
You can also use asterisks as wildcard characters; for example: o:vid-0911_pid-****
I If you congure the agent side without the o or m modier, the conguration rule is considered
invalid and will be ignored.
Chapter 4 Using USB Devices with Remote Desktops and Applications
VMware, Inc. 79