Bug 1038697

Summary:	Accessing the UP in RHEV-M, doesn't install the USBClerk, only SpiceX and virt-viewer.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Bill Sanford <bsanford>
Component:	ovirt-engine-userportal	Assignee:	Nobody <nobody>
Status:	CLOSED WONTFIX	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	acathrow, dblechte, ecohen, iheim, michal.skrivanek, mkrcmari, pvine, Rhev-m-bugs, vipatel, yeylon
Target Milestone:	---	Keywords:	Regression
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-16 21:07:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Bill Sanford 2013-12-05 16:10:59 UTC

Description of problem:
I first installed RHEV-M and did a local install of spice-client-msi-3.3-6. I rebooted the RHEV-M server and then accessed it from the RHEV-M UP. The instance of IE on the SPICE client would then download the SpiceX.dll and virt-viewer.exe. This is also when the "usbclerk.exe" file would also be installed. 

The "usbclerk.exe" file was never installed and had to do that manually from brew. 

Version-Release number of selected component (if applicable):
RHEV-M:
RHEV-M 3.3 (is 24.2)
RHEL6.5-20131111.0-Server-x86_64-DVD1.iso
spice-client-msi-3.3-6

Hosts:
RHEL6.5-20131111.0-Server-x86_64-DVD1.iso

Guest: 
Windows W2K8R2
rhev-guest-tools-iso-3.3-6.noarch.rpm
vdagent - https://brewweb.devel.redhat.com/buildinfo?buildID=310319

Client: 
Windows 7x64 - Using IE9

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Michal Skrivanek 2013-12-16 21:07:12 UTC

Due to the issues with 32 vs 64 bit deployment the usbclerk was removed from the activex bundle by spice team. It's now a separate installer you have to run depending on your platform. This is supposed to be documented by bug 997418 which is a blocker for 3.3 as well