So, my question is what should I do about this. This means the windows 10 machine I tested on ONLY has the xHCI controller, and therefore cannot forward the devices We need to support do not have any other controllers than the xHCI controller, which Intel uses EXCLUSIVELY on chips after the 5th generation. In is handled by the generic USB controller using the EHCI controller standard, but with the 3.0 port, it is handled by the intel USB 3.0 eXtensible controller which uses xHCI and Remote Desktop no longer sees the device. I have verified that it is only due to this difference in controllers by checking the Device Instance Path on all related devices, to confirm the chain of inheritance. No longer sees that a device is able to be forwarded. However, if I connect the device to the USB 3.0 hub (which is handled by the Intel USB 3.0 eXtensible Host Controller and uses the xHCI standard) Remote desktop The EHCI standard for USB 2.0) everything works fine and remote desktop can forward the device. When I attempt to forward USB with RemoteFX on the Win7 machine, if I have it plugged into the USB 2.0 slot (which is handled by the Generic USB Hub controller, which uses
On the Win7 machine, it has a generic USB Hub and the old EHCIĬontroller installed, as well as the new xHCI controller and hub for the usb 3.0 ports. I have tested this on two machines, one running windows 7 SP1 and the other running Windows 10, both connecting to the same Windows Server 2012 R2 box, with the appropriate RD roles installed.
0 kommentar(er)
