Bug 918605

Summary: [User Portal] Connect automatically doesn't take in effect that for Windows 8/2012 RDP is default
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: ovirt-engine-userportalAssignee: Frantisek Kobzik <fkobzik>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Belka <jbelka>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, dyasny, ecohen, iheim, michal.skrivanek, ofrenkel, Rhev-m-bugs, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: sf13.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot for autoconnect with RDP none

Description Jiri Belka 2013-03-06 15:15:21 UTC 
Description of problem:
Connect automatically doesn't take in effect that for Windows 8/2012 RDP is default. While VM's options, Remote Desktop is default, so it is just auto-connect issue.

Version-Release number of selected component (if applicable):
sf9

How reproducible:
100%

Steps to Reproduce:
1. Windows 8/2012 VM for user in the UP
2. Connect with auto-connect enabled from the login screen
3.
  
Actual results:
Auto-connect opens remote-viewer (SPICE) console

Expected results:
As there is performance issue with unaccelerated SPICE console, RDP was agreed to be default for Windows 8/2012. So make auto-connect to check this correctly.

Additional info:
This is for Windows clients as RHELs do not have RDP at all for the UP.
Comment 1 Jiri Belka 2013-03-20 15:19:52 UTC 
Same situation with VNC, if VNC is default console for VM (defined in Admin Portal), autoconnect opens VNC when logging into User Portal. But when there's no autoconnect enabled, the selected console in User Portal is Remote Desktop.
Comment 2 Frantisek Kobzik 2013-03-20 15:49:58 UTC 
Regarding comment 1:
If VNC is default console, then the auto-connect should use VNC. 
The automatic setting of RDP happens only when SPICE is set and not supported.
Comment 3 Frantisek Kobzik 2013-04-09 07:33:47 UTC 
merged u/s: 8753b55bd95a81636d641734f42bb6e89352c85b
Comment 5 Jiri Belka 2013-04-15 11:49:15 UTC 
ok sf13.1.
Comment 6 Jiri Belka 2013-04-15 13:11:44 UTC 
Ah, there's problem: when IE is clean (no activex is installed - use Reset in IE's Advanced options), there's popup for installing ActiveX for spice components even the console is RDP. After installing this ActiveX for spice, the page refreshes and there's another popup (valid one) requesting installtin ActiveX for RDP, then the page again refreshes and opens RDP with its dialog.

So, this first popup for ActiveX for spice is there incorrectly.
Comment 7 Jiri Belka 2013-04-15 13:12:43 UTC 
Created attachment 735897 [details]
screenshot for autoconnect with RDP

autoconnect - active x for spice when console is RDP
Comment 8 Frantisek Kobzik 2013-04-22 13:11:34 UTC 
This bug could be reproduced neither on my setup nor on the original one (where it has been found). Setting on_qa.
Comment 9 Jiri Belka 2013-04-22 13:21:06 UTC 
OK, sf13.1 (issue in comment #6 was some magic, we tried to reproduce it again couple of times any success - w7 ie9, ie10, w2k8 ie9).
Comment 10 Itamar Heim 2013-06-11 09:50:16 UTC 
3.2 has been released
Comment 11 Itamar Heim 2013-06-11 09:50:33 UTC 
3.2 has been released
Comment 12 Itamar Heim 2013-06-11 09:58:09 UTC 
3.2 has been released