did some more debugging, with our own client, we can make it to work well. But as a plugin to microsoft rdp client, it's not consistent, sometimes, usb devices appear, sometimes not. It seems to do with the time vrdp server starts to send out messages. MS plugin API receives messages after rdp connection is fully established. So can you investigate the server side, to start sending out messages after connection is complete. Right now, we noticed that our client receives messages from rspsnd and vrdpusb channels during connection time. In our client, we can fix this. However, with MS plugin, we don't have a way to hook so early.
--- On Tue, 2/7/12, Klaus Espenlaub <[email protected]> wrote: From: Klaus Espenlaub <[email protected]> Subject: Re: [vbox-dev] any plan to support RDP usb redirection spec? To: [email protected] Date: Tuesday, February 7, 2012, 2:47 AM On 06.02.2012 22:48, Huihong Luo wrote: > Microsoft has published a spec: > http://msdn.microsoft.com/en-us/library/ff635589/ > for usb redirection from rdp client to Hyper-V virtual machines through > a channel extension. similar to vbox's current vrdp usb protocol. From > my implementation of vrdp usb client, it seems not that stable. So I > wonder if microsoft's spec is better. Not immediately, especially as a spec by itself doesn't fix problems. Is your implementation available anywhere? We could potentially help, as the VirtualBox USB redirection is quite stable as such on the platforms where we have RDP client support for it. Klaus _______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
_______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
