Bug 1116447 - 3.3 to 3.4 Upgrade changed Windows VM console setting from VNC to RDP
Summary: 3.3 to 3.4 Upgrade changed Windows VM console setting from VNC to RDP
Keywords:
Status: CLOSED DUPLICATE of bug 1108673
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.5.0
Assignee: Frantisek Kobzik
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-04 16:09 UTC by Michael Everette
Modified: 2019-04-28 09:28 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-18 13:13:14 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1121093 0 None None None Never

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.


Note You need to log in before you can comment on or make changes to this bug.