Citrix Virtual Apps and Desktops


The following steps should be followed to triage USB redirection related issues:

  1. Validate system requirements are being met for USB redirection. This includes correct CVAD and CWA versions, supported devices and device drivers on the OS platform under consideration.

  2. Ensure the configuration is appropriate based on the components’ versions and platforms in use in your environment. See the note in Legacy USB Redirection Configuration for details on components that require legacy configuration settings.

  3. Validate that device is listed under devices that the client has enumerated.

    1. Workspace Preferences toolbar: Look at the devices enumerated in the Devices tab of the Workspace app Preferences toolbar (Right click CWA icon > Connection Center > Preferences… Click on Devices tab).

    2. CtxUsbDiagnostics.exe (Recommended): Run this tool in a command prompt window. The output gives you device specific information for a specific session. It will tell you if a device is being redirected or not. It will also tell you if a device rule set is causing the device to not be redirected. See, Diagnostics Tool for more information.

    3. USBView or other 3rd party tools: Run a 3rd party tool like USBView in the endpoint / client machine to ensure that the device is detected at the endpoint.

  4. If you see the device being enumerated:

    1. If you see a Deny rule in the CtxUsbDiagnostics tool output for a particular device, check the policies configured in Studio and ensure that the rules are correctly set in Version 2 policy. If the deny rule doesn’t appear in the studio policy, check the client side policy and finally the client side defaults in that order to find the matching deny rule.

    2. If there is no deny rule in the CtxUsbDiagnostics output, then CWA will allow redirection of the device by checking / clicking the appropriate button in the devices tab of the Preferences window (Devices > Manage devices). A device once redirected will be available in the session. This can be verified by checking the device manager / USBView or similar application in the HDX session.

  5. If you do not see the device being presented inside the session:

    1. It is possible that the correct device driver is not installed correctly on the VDA host. Ensure that the latest versions of device drivers are correctly installed on the VDA host. Some device drivers are not supported on terminal server machines so ensure that is not the case with the device you are trying to redirect.

    2. Ensure that the device is not being used on the client endpoint. Some devices require drivers to be installed on the client endpoint as well and this could prevent them from being redirected in the session.

  6. Validate USB related rules are set correctly on the client endpoint:

    1. CWA for Windows :

      1. Validate that group policy on the client (add more detail and SS for this) is appropriately set and does not conflict with the rules set in Studio.

      2. Validate that default rules in the client’s registry.


      (HKLM\SOFTWARE\Wow6432Node\Citrix\PortICA\GenericUSB\DeviceRules) are appropriately set and not in conflict with the rules set in Studio and client group policy.

    2. CWA for Linux - To triage CWA for Linux issues, see USB documentation for CWA for Linux

    3. CWA for Mac - To triage CWA for Mac issues, see CWA for Mac


  • On TSVDA, audio devices are blocked by default from using USB redirection. The recommended way to use those devices is using the optimized Audio VC.
  • Sometimes, USB composite devices might not be split automatically even though a correct device redirection rule is set to split the device. This issue occurs because the device is in low power mode. In these instances, the child device that enters low power mode might not be present in the device list. You can use the following workarounds to overcome this issue:

    • Disconnect the session, insert the USB device, and reconnect to the session.

    • Unplug the USB device and plug it back in. This action results in the device moving out of low power mode.

  • Sometimes, USB battery saver settings may be enabled to optimize battery life. If the client endpoint goes to sleep, the USB device may get disconnected. In such a scenario, you might have to disconnect and reconnect the device in order to present the device again in the session.

Event Logs

Administrators can now monitor for unauthorized devices that users may attempt to redirect and can take the appropriate action. Here are some of the event messages that will be logged in the Event viewer on the VDA host for devices that are allowed to be redirected and for devices that are not.