- This topic has 5 replies, 2 voices, and was last updated 6 months, 3 weeks ago by
.
-
Posts
-
Hello,
I have a PiKVM 4 Mini that I’m controlling an Optiplex 3000 ThinOS thin client with in my lab rack. It works great for testing configurations and OS upgrades, etc, but when I connect an RDP session, the keyboard and mouse stop working. I can VNC to the thin client and interface with the RDP session, but I cannot control the RDP session via PiKVM. Wondering if anyone had any ideas? I’m thinking maybe USB Redirection on the RDP is redirecting the KVM keyboard/mouse and not realizing it’s the actual input devices for the thin client.
Additional testing, this issue is not present on Microsoft AVD v1.8.1819 or v2.0.2102 but IS present on AVD v2.2.2196.
Optiplex 3000
ThinOS v9.4.3087
BIOS v1.11.0
Seems to be a bug (or new USB redirection “feature”?) in the latest Microsoft AVD package. Guess someone needs to report the issue to Dell engineering. Sigh.
You might be able to block the USB device with the policy from USB Redirection.
Yes, further testing revealed it is USB Redirection. The newest AVD seems to redirect more devices and doesn’t realize the PiKVM’s emulated keyboard and mouse are the local input, and redirects them.
You might want to give Relative Mouse mode a try. Here is a link to how to enable it.https://docs.pikvm.org/mouse/#relative-mouse-on-v2-platform-otg-hid
This issue appears resolved in the latest update combo of:
Optiplex 3000
BIOS v1.13.2
ThinOS 2311 (v9.4.4123)
AVD v2.3.2266
I’m no longer having issues controlling RDP sessions on the lab thin client via PiKVM.
I had tried all sorts of RDP session redirection blocking setting for the various detected USB devices of the PiKVM, none worked. Happy that Dell fixed the issue!
- You must be logged in to reply to this topic.