Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Force HID Device USB reconnection from Horizon Client (76596)

Last Updated: 10/16/2023Categories: TroubleshootingTotal Views: 4903Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

While forwarding an HID device with USB instead of sharing it between the client host system and the guest VM desktop. The Automatically connect when inserted is set but when he disconnects and reconnects the keyboard/HID device, it does not automatically reconnect as a USB device to the VM.

Example:
A USB composite device(keyboard) falls into the hid bootable category(its interface 1 is hid-bootable).
vmware-view-usbd-XXXX.log:

2023-10-13T15:04:31.414-05:00| vmware-usbd| I125: DevFltr: Interface [0] - Family(s): keyboard
2023-10-13T15:04:31.414-05:00| vmware-usbd| I125: DevFltr: Interface [1] - Family(s): hid,hid-bootable
2023-10-13T15:04:31.414-05:00| vmware-usbd| I125: DevFltr: Interface [2] - Family(s): hid

Behaviour:

When we connect to the desktop, the device is automatically connected to the desktop, because the "Automatically connect at Startup" is checked.

If you unplug the device and replug it, the device does not get connected to the desktop automatically because of the above rules.

Cause

The default Horizon Client behaviour is not to auto-reconnect USB HID-bootable devices, even if the "Automatically connected when inserted " option is checked.

This is by design as HID devices are not usually redirected as USB devices, they are shared between the local system and the VM.

When the HID device is multi-function, for instance, a keyboard with a card reader, you may want to forward the device with USB.

However, the default behaviour on reconnecting is to make the HID device available to the local client system.

Resolution

This is a known issue.

Workaround

Configuration file Location

Guest O/S

File Location

Windows

C:\ProgramData\VMware\VMware USB Arbitrator Service\config.ini

Linux

/etc/vmware/config

macOS

Library/Preferences/VMware Fusion/config

Procedure to add a device quirk to a Horizon Client:

This will force the client to automatically re-attach a device

Document the usage of this key within your organization and ideally validate functionality after a client upgrade

Back up and edit the appropriate configuration file.

Edit the config file by adding a line to set the device quirk:

usb.quirks.device0="<Device Vendor ID>:<Device Product ID> allow”

Note: You can obtain the Device Vendor ID and Product ID by following the VMware Docs page Using Log Files for Troubleshooting and to Determine USB Device IDs.

Restart the VMware USB arbitrator service or reboot the Client endpoint for the quirks to take effect.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vCloud Director 设备安装最佳实践 (76559)

KB
•
vCloud Director Appliance のインストールのベスト プラクティス (76559)

KB
•
vCenter Server Appliance のディスク容量が不足する (76563)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon Client for Windows

VMware Horizon Client for Mac OS X

VMware Horizon Client for Linux

VMware Horizon Client

VMware Horizon

Related Versions:

VMware Horizon Client for Windows 5.3.x

VMware Horizon Client for Windows 5.2.x

VMware Horizon Client for Windows 5.1.x

VMware Horizon Client for Windows 5.0.x

VMware Horizon Client for Windows 4.9.x

VMware Horizon Client for Windows 4.8.x

VMware Horizon Client for Windows 4.7.x

VMware Horizon Client for Windows 4.6.x

VMware Horizon Client for Windows 4.5.x

VMware Horizon Client for Windows 4.4.x

VMware Horizon Client for Windows 4.3.x

VMware Horizon Client for Windows 4.2.x

VMware Horizon Client for Windows 4.10.x

VMware Horizon Client for Windows 4.1.x

VMware Horizon Client for Windows 4.0.x

VMware Horizon Client for Mac OS X 5.3.x

VMware Horizon Client for Mac OS X 5.2.x

VMware Horizon Client for Mac OS X 5.1.x

VMware Horizon Client for Mac OS X 5.0.x

VMware Horizon Client for Mac OS X 4.9.x

VMware Horizon Client for Mac OS X 4.8.x

VMware Horizon Client for Mac OS X 4.7.x

VMware Horizon Client for Mac OS X 4.6.x

VMware Horizon Client for Mac OS X 4.5.x

VMware Horizon Client for Mac OS X 4.4.x

VMware Horizon Client for Mac OS X 4.3.x

VMware Horizon Client for Mac OS X 4.2.x

VMware Horizon Client for Mac OS X 4.10.x

VMware Horizon Client for Mac OS X 4.0.x

VMware Horizon Client for Mac 4.6.x

VMware Horizon Client for Mac 4.5.x

VMware Horizon Client for Linux 5.3.x

VMware Horizon Client for Linux 5.2.x

VMware Horizon Client for Linux 5.1.x

VMware Horizon Client for Linux 5.0.x

VMware Horizon Client for Linux 4.9.x

VMware Horizon Client for Linux 4.8.x

VMware Horizon Client for Linux 4.7.x

VMware Horizon Client for Linux 4.6.x

VMware Horizon Client for Linux 4.5.x

VMware Horizon Client for Linux 4.4.x

VMware Horizon Client for Linux 4.3.x

VMware Horizon Client for Linux 4.2.x

VMware Horizon Client for Linux 4.10.x

VMware Horizon Client for Linux 4.1.x

VMware Horizon Client for Linux 4.0.x

view all

Take Our Survey

Support Assistant