RGR Posted August 2 Share Posted August 2 (edited) Hello all, I'm reaching out for some guidance on an issue we're facing with USB auto-connect/redirect settings via GPOs, specifically using the connectUSBOnInsert and connectUSBonStartup policies in combination with Yealink headsets (WH62 and WH66). While we successfully manage to exclude certain USB device families like mouse, video, and storage using the "Exclude Automatically Connection Device Family" setting, our headsets are being misclassified as "keyboards". Consequently, this misclassification also auto-forwards local keyboards, rendering them unavailable on the local desktop—a significant problem when users need to unlock their workstations. The challenge intensifies as we deal with various keyboard vendors and models, making it impractical to exclude each by PID/VID with the "Exclude Automatically Connection Vid/Pid Device" setting. Ideally, we would prefer an "Include Automatically Connection" setting, if such exists, to specifically target devices we want to redirect without excluding others like fingerprint readers and other USB peripherals that might be connected in the future. We are currently using the latest Horizon 8 Server and Horizon Client 2406 8.13. Any help or suggestions on how to better manage this situation would be greatly appreciated! Best regards, Roger Edited August 2 by RGR Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.