Setting Up Desktop and Application Pools in View

Table Of Contents
USB Settings in the View Agent Configuration ADM Template
You can define USB policy settings for both View Agent and Horizon Client. On connection, Horizon Client
downloads the USB policy settings from View Agent and uses them in conjunction with the Horizon Client
USB policy settings to decide which devices it will allow to be available for redirection from the client
computer.
The View Agent Configuration ADM template file (vdm_agent.adm) contains policy settings related to the
authentication and environmental components of View Agent, including USB redirection. The settings
apply at the computer level. View Agent preferentially reads the settings from the GPO at the computer
level, and otherwise from the registry at HKLM\Software\Policies\VMware, Inc.\VMware VDM\Agent\USB
Settings for Configuring USB Device Splitting
The following table describes each policy setting for splitting composite USB devices in the View Agent
Configuration ADM template file. View Agent does not enforce these settings. View Agent passes the
settings to Horizon Client for interpretation and enforcement according to whether you specify the merge
(m) or override (o) modifier. Horizon Client uses the settings to decide whether to split composite USB
devices into their component devices, and whether to exclude the component devices from being available
for redirection. For a description of how View applies the policies for splitting composite USB devices, see
“Configuring Device Splitting Policy Settings for Composite USB Devices,” on page 186.
Table 1411. View Agent Configuration Template: Device-Splitting Settings
Setting Properties
Allow Auto Device
Splitting
Property:
AllowAutoDeviceSplitting
Allows the automatic splitting of composite USB devices.
The default value is undefined, which equates to false.
Exclude Vid/Pid Device
From Split
Property: SplitExcludeVidPid
Excludes a composite USB device specified by vendor and product IDs from
splitting. The format of the setting is {m|o}: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: o:vid-0781_pid-55**
The default value is undefined.
Split Vid/Pid Device
Property: SplitVidPid
Treats the components of a composite USB device specified by vendor and product
IDs as separate devices. The format of the setting is
{m|o}:vid-xxxx_pid-yyyy(exintf:zz[;exintf:ww])
or
{m|o}: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: o:vid-0781_pid-554c(exintf:01;exintf:02)
NOTE View does not automatically include the components that you have not
explicitly excluded. You must specify a filter policy such as Include Vid/Pid
Device to include those components.
The default value is undefined.
Chapter 14 Using USB Devices with Remote Desktops and Applications
VMware, Inc. 193