Allow/Block USB devices in VMware Horizon

No comments

In some cases, customers need to allow or block determined devices when user trying to connect a usb thumb drive into Virtual Machine or Application Virtualization.

This is a tradicional question which I receive from lots of people. This post will explain how is the best way to configure simple tasks to allow/block USB devices or allow/block determined devices based on PID / VID.

Easy Configuration

When you are logged into View Connection Server (broker), you can see on the left side of the console, an option called Policies – Global Policies.

This option allow you to set USB Access to Allow / Deny in a global way, which means, all desktop pools and application farms will be denied USB Access.

Figure 1 – View Connection Server – Global Policies

You have another option to block USB Access when you are under Desktop Pool or RDSH Pool. Opening the VDI Pool below, you can see a tab called Policies, which show us the specific configuration for this Pool only.

Figure 2 – Desktop Pool Policies Settings

The Specific Configuration

In some cases, customer has specific requests which needs to allow some family types of devices (e.g: Mass Storage) or specific product to be used into VDI / RDSH access.

When this kind of request came by, my questions are always the follow ones:

  • Which devices do you want your users to have access to?
  • Are they equal or a sort of them are?
  • Why do you need this kind of device?
  • Is this important for your use case?

These questions are not blockers questions. My intention is to explore the use cases why you need to use and if the application is already installed into VDI or published into RDSH.

When we have those answers cleared defined, it’s time to start configuring our Active Directory to create an OU (Organizational Unit) using VMware Horizon Administrative Templates, downloaded from

Figure 3 – Administrative Templates containing VMware Horizon ADMX files.

When you download the ZIP file, you can see the following ADMX files right after you unzip this folder:

Figure 4 – Folder Structure After Unzip

All .ADMX files need to be copied into your Active Directory , under C:\Windows\PolicyDefinitions folder.

Figure 5 – Copying .ADMX files into PolicyDefinitions Folder

All .ADML files (which are inside the folder en-US or es-ES, needs to be copied into C:\Windows\PolicyDefinitions\en-US folder structure.

Note: Copy the whole folder into this address. All folders are related to locale version and used idioms.

Figure 6 – Copying .ADML folders into PolicyDefinitions Folder

When you are creating a new OU and editing the Policy, this will be information you have it now after uploading the .ADMX e .ADML files.

Figure 7 – VMware Horizon Policies Appearing for you into Group Policy Management

Configuration will be done into VMware Horizon Client Configuration – View USB Configuration,under Computer Configuration.

Figure 8 – View USB Configuration using Administrative Templates

At this point, you need to check what is the VDI (Vendor ID) and PID (Product ID) to the related device you need to configure.

E.g.: VID: 0781 and PID: 544c

To know how to get this information, check it out using Device Manager into your Windows Client or Windows Server. Check the screenshot below:

Figure 9 – Check VID / PID using Device Manager

For the Use Case I worked with, my customer would like to exclude the following device. So my configuration was the following:

Figure 10 – Exclude VID/PID Device using USB Configuration

The VDI os RDSH needs to be rebooted or gpupdate /force into command line to force to get the news policies for your teste.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.