Description of problem: Sections 2.3 - 2.5 reference the old method for installing and updating the Remote Viewer client, specifically Windows, which relied on an ActiveX plugin to push out the Remote Viewer installer for the first time or to update it if a new version was released. That functionality appears to be missing in RHEV 3.3 now that we are using "Native" console launching with the MIME-type file (console.vv). Questions: 1. How are the users supposed to get the Remote Viewer client? 2. If they already have one installed from RHEV 3.2, how does their current client get updated to work with the console.vv files? Version-Release number of selected component (if applicable): Revision 3.3.0-007
After additional testing, it appears that Remote Viewer will auto-install/auto-update as long as "Browser plugin" is selected under "Console invocation" in the "Console settings" GUI. In addition to the above procedure, I believe we should instruct users on how to obtain the proper Remote Viewer software on Windows if they are not using IE. Are the Remote Viewer .msi files hosted on a path that the user can reach in their web browser? The current "Console Client Resources" links to ovirt.org which isn't shipped or supported by Red Hat.
Please see bug 1039802 for additional information that should be added to this section. If the user installs the CAB version of Remote Viewer in 3.3, they will need to manually associate Remote Viewer with the .vv files.
(In reply to Bryan Yount from comment #3) > Please see bug 1039802 for additional information that should be added to > this section. If the user installs the CAB version of Remote Viewer in 3.3, > they will need to manually associate Remote Viewer with the .vv files. This will make transitionning to system MSI even harder, since user preference will be overriding system preference. I would avoid that unsupported path.
(In reply to Marc-Andre Lureau from comment #4) > This will make transitionning to system MSI even harder, since user > preference will be overriding system preference. I would avoid that > unsupported path. I completely understand. I guess at the very least we should be informing the customers as such. Can this be done in the product the first time the customer selects Native console? Or should we just add it to the documentation?
Fixed in 7375, 7379, 30303.
Documentation Link ------------------------------ http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html-single/User_Guide/index.html#Console_Components What Changed ------------------------------ The following topics were created or revised as outlined below. Console Components [30303] Created this topic to provide an outline of consoles. Installing Remote Viewer on Linux [7375-627155] Updated the channel name and revised the overall topic to improve clarity. Installing Remote Viewer for Internet Explorer on Windows [7379-627157] Revised the overall procedure to make it clear this option is to be used when using Internet Explorer as the browser, and the update the file name to SpiceX.cab. Updated revision history: [30106-627193] NVR ------------------------------ Red_Hat_Enterprise_Virtualization-User_Guide-3.4-en-US-3.4-14 Moving to ON_QA.
Verified in the current release. Please open a new bug if you have further feedback. Cheers, Julie