Hide Forgot
Description of problem: USBClerk service from usbclerk msi installer (mingw-usbclerk-0.3.3-1.el6_5) fails to install winusb driver for USB device which should be redirected due to policy issues, the error message from usbclerk log: 816::INFO::2013-12-04 18:51:40,250::install_winusb_driver::Device 0951:162d driver install failed -- System policy has been modified to reject unsigned drivers (-19) Once I installed the mentioned usbclerk from mingw-usbclerk-0.3.3-1.el6_5 and installed usbclerk-win-0.1-11 which was shipped in RHEV3.2, It's same with the other way, when updating to 0.3.3-1 usb redirection stops working. This problem I cannot observe on Windows 7 client. Here is log of failed installation, then downgrade to usbclerk-win-0.1-11 and winusb driver installed successfully: 816::INFO::2013-12-04 18:51:39,343::dispatch_message::Installing winusb driver for 0951:162d 816::INFO::2013-12-04 18:51:39,343::get_dev_info::Cannot get device service name 13 816::INFO::2013-12-04 18:51:39,343::install_winusb_driver::Looking for device vid:pid 0951:162d 816::INFO::2013-12-04 18:51:39,343::install_winusb_driver::Device 0951:162d found 816::INFO::2013-12-04 18:51:39,343::install_winusb_driver::Installing driver for USB device: "USB Mass Storage Device" (0951:162d) inf: usb_device_0951_162d.inf 816::INFO::2013-12-04 18:51:40,250::install_winusb_driver::Device 0951:162d driver install failed -- System policy has been modified to reject unsigned drivers (-19) 816::INFO::2013-12-04 18:51:40,250::dispatch_message::Failed 816::INFO::2013-12-04 18:51:41,484::dispatch_message::Removing winusb driver for 0951:162d 816::INFO::2013-12-04 18:51:41,484::get_dev_info::Cannot get device service name 13 816::INFO::2013-12-04 18:51:41,484::remove_winusb_driver::WinUSB driver is not installed 816::INFO::2013-12-04 18:51:41,484::dispatch_message::Failed 4056::INFO::2013-12-04 19:14:56,546::USBClerk::main::***Service started*** 3204::INFO::2013-12-04 19:18:59,453::USBClerk::dispatch_message::Installing winusb driver for 0951:162d 3204::INFO::2013-12-04 19:18:59,453::USBClerk::get_dev_info::Cannot get device service name 13 3204::INFO::2013-12-04 19:18:59,484::USBClerk::install_winusb_driver::Looking for device vid:pid 0951:162d 3204::INFO::2013-12-04 19:18:59,484::USBClerk::install_winusb_driver::Device 0951:162d found 3204::INFO::2013-12-04 19:18:59,484::USBClerk::install_winusb_driver::Installing driver for USB device: "USB Mass Storage Device" (0951:162d) inf: usb_device_0951_162d.inf 3204::INFO::2013-12-04 19:19:04,250::USBClerk::dispatch_message::Completed successfully Version-Release number of selected component (if applicable): mingw-usbclerk-0.3.3-1.el6_5 on Windows XP client with any guest. How reproducible: Always Steps to Reproduce: 1. Install mingw-usbclerk-0.3.3-1.el6_5 on Windows XP client. 2. Establish spice session with USB redirection support to any guest. 3. Try to redirect any USB device to the guest from WinXP client. Actual results: Failed driver installation due to: System policy has been modified to reject unsigned drivers Expected results: Successful installation of winusb driver Additional info:
Related to rhbz#1037642 ?
(In reply to Christophe Fergeau from comment #2) > Related to rhbz#1037642 ? Maybe, although Win7 x64 seems to be working and in general Win7x64 is pickier about unsigned stuff.
(In reply to Marian Krcmarik from comment #0) > Description of problem: > USBClerk service from usbclerk msi installer (mingw-usbclerk-0.3.3-1.el6_5) > fails to install winusb driver for USB device which should be redirected due > to policy issues, the error message from usbclerk log: > 816::INFO::2013-12-04 18:51:40,250::install_winusb_driver::Device 0951:162d > driver install failed -- System policy has been modified to reject unsigned > drivers (-19) > Once I installed the mentioned usbclerk from mingw-usbclerk-0.3.3-1.el6_5 > and installed usbclerk-win-0.1-11 which was shipped in RHEV3.2, It's same > with the other way, when updating to 0.3.3-1 usb redirection stops working. > This problem I cannot observe on Windows 7 client. > Could you clarify, is the combination usbclerk-win-0.1-11 from 3.2 + virt-viewer msi from 3.3 working? Is it XP SP3 Pro without modification? I don't remember having this problem, would be nice to double-check.
(In reply to Marc-Andre Lureau from comment #4) > (In reply to Marian Krcmarik from comment #0) > > Description of problem: > > USBClerk service from usbclerk msi installer (mingw-usbclerk-0.3.3-1.el6_5) > > fails to install winusb driver for USB device which should be redirected due > > to policy issues, the error message from usbclerk log: > > 816::INFO::2013-12-04 18:51:40,250::install_winusb_driver::Device 0951:162d > > driver install failed -- System policy has been modified to reject unsigned > > drivers (-19) > > Once I installed the mentioned usbclerk from mingw-usbclerk-0.3.3-1.el6_5 > > and installed usbclerk-win-0.1-11 which was shipped in RHEV3.2, It's same > > with the other way, when updating to 0.3.3-1 usb redirection stops working. > > This problem I cannot observe on Windows 7 client. > > > > Could you clarify, is the combination usbclerk-win-0.1-11 from 3.2 + > virt-viewer msi from 3.3 working? Yes, It is working in such combination. > > Is it XP SP3 Pro without modification? I don't remember having this problem, > would be nice to double-check. Yes and I do not remember to make any special modifications. Maybe If anyone can try to confirm It would be nice too. But anyway, downgrade to usbclerk-win-0.1-11 helps on the machine (whatever I could possibly do with it).
It seems that XP wants the Interactive flag of usbclerk service to be set.
Created attachment 838321 [details] MSI: make service interactive
I've tried on Win7/32 client and usbclerk 0.1-11 with virt-viewer 0.5.615 and I've got Error in Event log (system) during install: "The USB Clerk service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly." USB device could not be redirected. But after restart of client machine everything was nice and easy.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0059.html