Created attachment 1082796 [details] Unsupported plugin error Description of problem: Accessing VMRC in Win7/Chrome browser throws unsupported plugin error Version-Release number of selected component (if applicable): 5.4.3.0.20151001120745_d11cf59 How reproducible: 100% Steps to Reproduce: 1. Deploy an appliance and manage vsphere 55 provider 2. Navigate to Infrastructure ==> Virtual Machines ==> Choose a VM ==> Click on it 3. Click on the VMRC icon Actual results: Throws unsupported plugin error (Refer the screenshot for further details) Expected results: Should be able to see the vmrc screen Additional info:
Depending on the version of Chrome, the Client Integration plug-in may no longer be supported by Chrome. If you are testing with the latest version of Chrome (cannot tell from the screenshot), that is the case. Please confirm. https://support.google.com/chrome/answer/6213033?hl=en
Hi Brian, Yes I am using the latest version - 45.0.2454 and see this error. Thanks, Ramesh
Thanks Ramesh! This BZ should be closed, the latest versions of Chrome are functioning properly. Any version of Chrome released in September 2015 or later does not support the plugin that is required for VMRC connections. Brian
The VMRC plug-in is an NPAPI plug-in which has been phased out by Chrome. Google Chrome disabled NPAPI plug-in support by default starting at version 42.0.2311, which was released on April 4, 2015. To enable NPAPI plug-ins in this version of Chrome users have to visit [1] and re-enable the browser functionality. Google Chrome removed support for NPAPI plug-ins in version 45.0.2454, which was released on September 1, 2015. I have not been able to discover how to install previous versions of Chrome to test the specific versions noted above (information taken from release notes of the noted versions). I did experience these steps first hand on my machine. I have sent an email requesting the browser support for VMRC connections be updated and recommend that this BZ be closed. [1] chrome://flags/#enable-npapi
Moving this issue to verified state as per the comment#6.
Tested in 5.6.0.8-rc1.20160524155303_f2a5a50
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://access.redhat.com/errata/RHBA-2016:1348