RGR Posted August 2 Share Posted August 2 Hello all, I'm reaching out for some guidance on an issue we're facing with our Yealink headsets (UH62 and UH66) as they are being misclassified as "keyboard". We're using USB auto-connect settings via GPOs, specifically we are using the connectUSBOnInsert and connectUSBonStartup policies. We already successfully manage to exclude certain USB device families like mouse, video and storage using the "Exclude Automatically Connection Device Family", but we can't exclude "keyboard" for the former reason. Consequently, this misclassification will auto-forward 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 or unknown 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 would be greatly appreciated! Best regards, Roger Quote Link to comment Share on other sites More sharing options...
Employee Jack McMichael Posted August 8 Employee Share Posted August 8 I don't understand why the PID/VID wouldn't work? That's exactly what it's for is for scenarios you're describing. 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.