Hide Forgot
1. Proposed title of this feature request "Open in full screen" checkbox should be controlled by a setting in "rhevm-config". i.e. there should be an parameter in rhevm-config which will decide if the "Open in full screen" checkbox should be checked or unchecked. --- user portal --> Basic tab --> select vm --> click on SPICE(Edit) --> "Open in Full Screen". ---
we have a client-side property (configurable in Console Options) system wide default is user portal - fullscreen, webadmin - window. it can be also added as a VM-side property, but it can't be enforced...so is it useful?
Yes, that would be useful. The point is not to force the user into full screen or window mode. The users complain that the VDI sessions are started in full screen, when they only wanted it in a window on their desktop. We deployed VDI on RHEV 3.3, where window mode was the default for the user portal. This changed in 3.4 where full screen mode became the default in the user portal. By making the default setting in the user portal configurable by the administrator you make it more usable for environments who require a kiosk mode (full screen, no need for access to the original desktop), AND environments like ours where the VDI session is in addition to their normal desktop, not a replacement for it. (Our Linux desktop users use Windows VDI to access Windows, and our Windows desktop users use Linux VDI to access Linux.) This setting should be configurable in rhevm-config or in a per-vm setting. We do not use a rhevm pool to provide the VDI, so a per pool setting would be of no use. Thanks.
global default should be simple and conver the original use case I wouldn't do per-VM...a bit too much work, and we do have a per-user setting already
*** Bug 1325087 has been marked as a duplicate of this bug. ***
probably in the current build
Verified on version: 4.0.2-0.2.rc1.el7ev Please see Polarion cases.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1743.html