Applicable Products

• XenDesktop
• XenApp
• Receiver for Windows

Hi, I was advised by a Dell technician a while ago that it is recommended to download the latest device drivers from the Dell Support site to a USB stick before doing a clean installation of Windows 8.1. Should I download the drivers to my hard drive (c: drive) and then copy and paste them over to the USB flash drive. Insert a USB-A to USB Micro-B cable between the device and a USB-3.1 high-power port on the computer. Standard USB ports on the computer do not supply sufficient power and cannot be used. On the M-Series device, open Settings Storage & USB. Long-press the front button to show the menu. Select USB Mode. Change the mode to File transfers.

Objective

This article describles how to configure USB Redirection in a XenDesktop environment.

USB Devices not optimized for virtual channel support will fall back to the Generic USB virtual channel using raw USB redirection.

For XenApp per user audio redirection is supported, for each client user account receiver gpo has to be set for enabling audio through Generic USB.

Instructions

USB Device Redirection Introduction

Generic USB redirection feature allows redirection of arbitrary USB devices from client machines to XenDesktop virtual desktops. With this feature, the end users have the ability to interact with a wide selection of generic USB devices in their XenDesktop session as if it had been physical plugged into it.

Generic USB redirection works at a low level and redirect USB request and response message between client machines and XenDesktop virtual desktop. It avoids the requirement for compatible device drivers on the client machine and the driver is expected to be supported on the virtual desktop only.

Generic USB Redirection Configuration

By default, USB redirection configuration is not enabled. To use it, USB redirection policy and specific redirection rules must be enabled and configured.

Enabling Generic USB Redirection

1. Open Desktop Studio on XenDesktop server, click Start > All Programs > Citrix > Desktop Studio.

2. Expand HDX Policy.

3. Select Users.

4. Click Edit > Settings.

5. In the Policy console, scroll down to USB Devices.

6. Click Add on Client USB device redirection.

7. Select Allowed and click OK.

Creating USB Redirection Policy Rules

When the user tries to redirect USB device to Virtual Desktop, it is checked against each USB policy rules in turn until a match is found. The first match for any devices is considered final. If the first match is an Allow rule, the matched device is allowed to be redirected to the virtual desktop. If the first match is a Deny rule, the matched device is only available in the local desktop.

Drivers Vuzix Usb Devices Free

1. Open Desktop Studio on XenDesktop server and click Start > All Programs > Citrix > Desktop Studio.

2. Expand HDX Policy.

3. Select Users.

4. Click Edit > Settings.

5. In the Policy console, scroll down to USB Devices.

6. Click Add on Client USB device redirection rules.

7. Select Use default value and click OK.

   You can find the default rules in the following registry in virtual desktop:

   Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

   HKLMSOFTWARECitrixPortICAGenericUSBDeviceRules for 32-bit OS

   Or

   HKLMSOFTWAREWow6432NodeCitrixPortICAGenericUSBDeviceRules for 64-bit OS

Creating Client USB device optimization rules

Drivers Vuzix Usb Devices Download

In XenApp and XenDesktop 7.6 FP3, the Client USB device optimization rules can be applied to devices to disable generic usb optimization for interrupt devices, or to change the optimization mode.

When a user plugs in a USB input device, the host checks if the device is allowed by the USB policy settings. If the device is allowed, the host then checks the Client USB device optimization rules for the device. If no rule is specified, then the device is handled as Interactive mode (02). Capture mode (04) is the recommended mode for signature devices.

For more details follow link.

Settings for Audio redirection of XenApp (per user )

For Server OS enable audio through Generic USB from client policy, supported from Receiver 4.5 and XenApp / XenDesktop 7.8

For enabling audio redirection for logged in user you must perform following steps:

1. On Client copy receiver.admx from C:Program Files (x86)CitrixICA ClientConfiguration to C:WindowsPolicyDefinitions
   Note: For x86 Client instead of Program Files (x86) go to Program Files

2. On Client copy receiver .adml from C:Program Files (x86)CitrixICA ClientConfigurationen-US to C:WindowsPolicyDefinitionsen-US
   Note: For x86 Client instead of Program Files (x86) go to Program Files

3. On Client launch GPO by running gpedit.msc

4. Go to ComputerConfiguration->Administrative Templates->Citrix Receiver->User experience and right click edit “Audio through Generic USB Redirection”
   

5. Enable the policy and on client run gpupdate /force from command prompt
   

6. Launch XenApp session and redirect the audio device .

Settings for Specific USB Devices

Besides generic USB redirection, XenDesktop provides optimized redirection methods for some specific USB devices. Some advanced functions such as, data compression is provided by these dedicated virtual channels:

Using the USB Device Rules Policy

1. Open the Local Group Policy Editor and go to Administrative Templates > Citrix Components > Citrix Receiver > Remoting client devices > Generic USB Remoting.
2. Open the USB Device Rules setting and enable the setting. Add the USB Device rule as in this example,
   The Allow: VID=1230 PID=0007 rule allows the device with Vendor ID 1230 and Product ID 0007:
   Note:Use the Allow: VID=xxxx PID=xxxx rule when a specific device must be on top of the device rules list.

​
Note: Refer to Hardware/Device property details to find the Vendor ID or a tool like USBVIEW or on the Receiver Toolbar, go to Devices > Manage Devices > and mouse over on any device as shown in the following figure:

3. For Citrix Receiver 4.6 and lower, generally, the following USB Error appears when the device is in use on the endpoint. Identify the process using the device and kill it:

   “Device appears to be in use and cannot be attached. Close any…”

From Citrix Receiver 4.7 onwards, USB Error allows to forcefully redirect the device by clicking on Yes button

Workaround

Note: On Windows Receiver 3.0 version and later, there is a workaround to suppress the USB Error.

There is a registry setting available to force-redirect USB devices, even if a client-side application is using the device:

1. Open HKLMSOFTWARECitrixICA ClientGenericUSB for 32-bit OS.

   Or

   HKLMSOFTWAREWow6432NodeCitrixICA ClientGenericUSB for 64-bit OS.

2. Set REG_DWORD value EnableForceRestartForHID to 1.

Drivers Vuzix Usb Devices Windows 7

Additional Resources

Drivers Vuzix USB Devices

Citrix Documentation - Configure USB support

Drivers Vuzix Usb Devices Windows 10

• August 22, 2019 2.9.8

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.8	Released August 22, 2019	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added several internal interfaces for particular sensors (J003).

• January 25, 2019 2.9.6

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.6	Released January 25, 2019	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added missing Tonemapping Auto property.

• May 4, 2018 2.9.5

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.5	Released May 4, 2018	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Enabled tonemapping for 8bit video formats, e.g. Y800, RGB24 and RGB32.

• November 21, 2017 2.9.4

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.4	Released November 21, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Repaired not working J003 mono sensor pattern fix on particular video formats. This driver version is the last that works in Windows XP.

• January 9, 2017 2.9.3

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.3	Released January 9, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added a pattern fix for J003 mono sensors.

• January 9, 2017 2.9.1

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.1	Released January 9, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed the driver signature Code 52 error on new Windows 10 v1607 systems.

• January 15, 2016 2.8.9

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.9	Released January 15, 2016	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Changed certificates so that the driver can also be installed in Vista.

• November 9, 2015 2.8.7

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.7	Released November 9, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed an error which can appear when using sharpness on older CPUs.

• October 20, 2015 2.8.5

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.5	Released October 20, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed a bug which can appear on LivePause call.

• July 15, 2015 2.8.0

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.0	Released July 15, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Support of DFK ECU010-L34 with serial number property. Added tone mapping.

• February 17, 2015 2.7.33

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.33	Released February 17, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog The Auto Focus Onepush Running flag now resets correctly after the auto focus has finished.

• February 5, 2015 2.7.32

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.32	Released February 5, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Video format MJPG (2592x1944) of DFK AFU050-L34 camera can now be used.

• January 14, 2015 2.7.31

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.31	Released January 14, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Support for IMX236 based cameras. Support for RGB64 color formats. Several performance improvements.

• June 6, 2014 2.7.9.1152

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.9.1152	Released June 6, 2014	Type ZIP	Filesize 2.1MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added new properties: Brightness, sharpness, de-noise, saturation, hue and contrast. Added new property: Highlight reduction. Added new property: White balance temperature controls. Pixelfix for Y16 cameras now works as expected. VideoControl_ExternalTrigger (DirectShow property) can now be set as expected.

• January 1, 2014 2.6.5.1014

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.6.5.1014	Released January 1, 2014	Type ZIP	Filesize 1.9MB
  Requirements Intel Pentium IV or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed missing auto-gain for DFK AFU130. Fixed focus when start value is out of auto_focus_range. Fixed problem with AUTOFOCUS_ROI_RIGHT: minimum possibly wrong. Fixed auto focus ROI not working for 21*UC cameras. Fixed crash on load/connect with certain cameras 22/72xUC. Fixed previous exposure settings not being loaded on reconnect. Complete reworking of internal property system. Fixed Windows XP driver load crash. Fixed drop counter to be accessible from DirectShow. Fixed Windows 8 problem with certain video formats needing converters with standard DirectShow filters (e.g. Y800, capturing to an Y800 avi file was not possible). Fixed a problem with Windows 8 usbxhci driver not allowing transfers larger then 4 MB.

• February 26, 2013 2.4.14.851

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.4.14.851	Released February 26, 2013	Type ZIP	Filesize 1.9MB
  Requirements Intel Pentium IV or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit) DirectX 9.0c or higher
  Changelog WHQL certification.