(Yes, I have done a bit of testing with USB device passthrough over RDP. And, your RDP bits for both ends must be 6.1 or higher. When you initiate the RDP session the scanner sould be detected an installed within that session (you should see the little hardware detection widget show up). Also, you don't install the drivers in the target VM if you are using the RDP passthrough. If they are not compliant with the framework then you smiply have the scanner doing keyboard emulation and then I would expect it to be a driver issue. ![]() For USB redirections to work 100% the drivers have to use the Windows Device Driver Framework. If the scanner is operating independently, then it is the drivers. If the scanner is participating as a keyboard wedge (generally also involves a special dongle), then you will just be sending keyboard connands and not installing any drivers. ![]() The other key is the driver of the scanner. And the bug would be in the RDP transport. The question is: Whose bug is it? Have you tried using an RDC connection for a client external to the Hyper-V host? and do you get the same results? If so, then you have an RDP bug.
0 Comments
Leave a Reply. |