RGR

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

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