Following are the two Solutions to resolve this issue:

Solution 1

Install the printer drivers for the USB printer on the VDA. If the USB printer has system tray services and other applications that install, if you are in a single image environment you have now installed them for all VDAs, and you must educate the user to print to the local printer object rather than the auto-created printer.

Solution 2

Prevent the USB printer from redirecting to the VDA.
Solution 2 is recommended in this scenario as the way the user works is not changed and/or configurations of the virtual desktops are not manipulated.
The following procedure implements Solution 2.

Configuring USB Support

Refer to the following Citrix documentation on this feature - Configure USB support.

Following are few important points:

• Enabling a device to redirect, that must not redirect, involves allowing the device on the VDA and the endpoint.

• Disabling a device from redirecting only requires configuring the VDA or the endpoint.

• Local or group policy of the device dictates behavior. (This is translated to a registry value, but this example uses policy.)

The ADM template for USB policy is found on the product installation ISO.

• XenDesktop 4: <operating system>enSupportConfigurationicaclient_usb.adm

• XenDesktop 5: SupportConfigurationenicaclient_usb.adm

USB device rules use one or more of six identifiers for USB devices. For specific rules, refer to www.usb.org. This website has the identifiers to use with XenDesktop.

This procedure builds upon the following Default rules which are evaluated prior to additional instructions. The default rules are held in a separate registry location than the policies created later in the procedure.

These are the default rules on the VDA:

These rules are found in the following locations:

*location is under WOW6432node in 64-bit operating systems.

The endpoint has mor​e restrictive default rules to prevent devices such as USB mice (HID device) from redirecting which redirects the mouse to the virtual desktop, causing the user to lose control of the endpoint. Now that the default expected behavior is known, gather information on the device. A great tool to do this is USBDeview from Nirsoft.
Following is an example screen shot:

This tool shows any device that was ever connected to USB on the computer. Devices that are shaded and have a green light on the left side are currently active.
This example prevents the USB Audio device from redirecting to the VDA. An audio device must stay local to the endpoint rather than connect to the VDA unless audio is required in the VDA session. There are several ways to prevent this device from redirecting. A specific VID (VendorID) and PID (ProductID) is noticed. A simple VID rule would prevent the device from redirection.
Create the following rule:
DENY: vid=0763 pid=2015
Decide to create the rule - on the endpoint or on the VDA. If all VDA computer accounts are in the same OU or use the same base image (Provisioning Services), applying a GPO at an Organizational Unit (OU) level or a local policy setting to the base image affects all VDAs. Endpoints can reside in separate OUs and usually do not have a common base image, so logically rule can be separated using endpoints. In this case, to prevent USB Audio devices from connecting to any of the VDAs with no exception, so we will apply the rule to the VDAs.

1. Create or use an existing GPO that applies to the VDAs, or if using Provisioning Services, open the local GPEdit.msc on the VDA base image.

2. Import icaclient_usb.adm from the installation media.
   

3. Double-click USB Device Rules and enable the policy while creating the DENY rule.
   

4. Click OK and close group policy editor.

5. When the policy is applied, verify the setting in the registry location, see following screen shot.
   

Now, the USB Audio device no longer maps to the VDA. It is important to understand that while the endpoint is not configured to DENY the redirection, after it attempts to redirect the device, the VDA will DENY the redirection based upon the rule applied to the VDA. Configure both the VDA and the endpoint if we are required to allow a device that is denied by default. It is also important to be as specific as possible when configuring a device that is denied by default. We do not want to allow any other devices by accident and yield unwanted results.
What if we want to be more general on this deny rule and prevent ANY USB Audio device from connecting to our VDAs? Look at the Class of our audio device (01). What does “01” include? Refer to http://www.usb.org/developers/defined_class and note that Class 01 is an Audio interface. If we want to prevent all USB Audio interfaces from redirecting to the VDA, we could include the entire class.
This rule will encompass all USB Audio devices:
DENY: Class=01
If we apply this rule to the VDA, we never have to worry about USB Audio devices redirecting through USB. What if there is an exception? Device rules are processed sequentially so we can add an ALLOW rule after the DENY rule for an exception. Say we want only that particular USB Audio device in our previous example to redirect:
This rule will DENY all USB Audio devices, but allow one model in particular:
DENY: Class=01
ALLOW: vid=0763 pid=2015
Note: When entering multiple rules in Group Policy Editor, separate rules with a semicolon. Refer to the Help section of the GPO setting.
The last rule to process takes precedence over the previous rules. In reality, the complete processing of rules includes the default rules and our rules. This is what the entire chain looks like:

In conclusion, remember that ALLOW rules must exist on the endpoint AND the VDA, otherwise a single DENY wins. A DENY rule on either side prevents redirection; placement is dependent of your scenario.

Disclaimer

downloadWhy can't I download this file? Citrix does not support USB devices that require low-level port redirection. Because of the large number of USB-based devices that are available and the proprietary nature of each manufacturer implementation of USB, it has not been possible to date to make a generic USB port redirection solution available as a standard part of the product. Citrix is, however, investigating the possibilities for creating USB solutions for particular devices at the high-level device redirection as previously described. Contact Citrix Systems for the possibility of creating customized solutions for such products, or for information on future support for them within the standard product.

USB Drivers and ICA Clients

Note that all of the USB peripheral support above assumes the existence of a proper USB device driver for the operating system on the client device, and for a corresponding Citrix ICA Client for that same operating system that supports the mapping functionality at hand. For example, not all Citrix ICA clients support the use of smart cards whether or not a device driver from the manufacturer exists.

USB Printers on Macintosh Computers

The Citrix ICA Client for Macintosh OS provides general support for printers attached by using Macintosh USB ports. Some manufacturers supply printer drivers that allow a print file to be sent directly to specific USB printers. Another alternative is to print by using a network print server, instead of using the Client Printer Mapping functionality in the ICA Client. Refer to Citrix Documentation - Mac Printing to Map client devices.

Citrix Remote Usb Device Driver Download

USB Printers on Windows Based Terminals

USB support for Windows Based Terminal client devices is vendor dependent. Contact the Windows Based Terminal vendor for the latest information about USB solutions for their devices.

Citrix Usb Devices Driver Download Windows 10

Additional Resources

Citrix Usb Devices Driver Download Software

• CTX129558 - How to Redirect USB Devices in XenDesktop
• CTX137939 - Citrix Generic USB Redirection Configuration Guide
• Citrix Documentation - VM Hosted Apps
• Citrix Documentation - Configuring USB Support

Additional Resources

Citrix Usb Devices Driver Download Windows 7