Bug 1116447

Summary: 3.3 to 3.4 Upgrade changed Windows VM console setting from VNC to RDP
Product: Red Hat Enterprise Virtualization Manager Reporter: Michael Everette <meverett>
Component: ovirt-engineAssignee: Frantisek Kobzik <fkobzik>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.4.0CC: acathrow, iheim, lpeer, michal.skrivanek, ofrenkel, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-18 13:13:14 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:
Embargoed:

Description Michael Everette 2014-07-04 16:09:10 UTC 
Description of problem:

[Initial Issue]
Before upgrading to 3.4 customer used to connect to Windows VMs trough the web-gui rhev-m by clicking on the the little green icon with tooltip "Console". The firefox browser would return a file with .vv extension and he had a script to run the VNC session without problem.

After upgrading to 3.4 when he tried to connect to a windows VM it would return a file with extension .rdp.

All other linux vms are still sending .vv files when I try to console to them.

[Resolution]
-- Right click on the Windows VM where I want to start the console session--> Console Option --> Change from Remote Desktop to VNC Native.

He had this set before with the 3.3 , somehow upgrading to 3.4 this option changed for all windows VM  to "Remote Desktop" .


Version-Release number of selected component (if applicable):
rhevm-3.4.0-0.22.el6ev.noarch 


Would like to know if this is new expected behavior or if this is a bug of some sort.