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.
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.
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.
merged u/s: 8753b55bd95a81636d641734f42bb6e89352c85b
ok sf13.1.
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.
Created attachment 735897 [details] screenshot for autoconnect with RDP autoconnect - active x for spice when console is RDP
This bug could be reproduced neither on my setup nor on the original one (where it has been found). Setting on_qa.
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).
3.2 has been released