UPDATE (05/31/15) - If you are connecting directly to an ESXi host you can either use the vSphere API to query for the VM MoRef ID or you can easily pull it by running the following command directly in the ESXi Shell: You can subscribe to VMware KB 2091284 which will be updated when the download is available. You can continue using the existing methods to connect to your VM Console, the new Standalone VMRC is NOT required but the links have been put in place to proactively get ready for NPAPI deprecation (more details below).
UPDATE (10/12/14) - It looks like the standalone VMRC is currently not available for download just yet. UPDATE (10/21/14) - Looks like the standalone VMRC has just been made available and you can now download it by either following the link in the vSphere Web Client if you are on vSphere 5.5 Update 2b OR simply by going to As a result, you might be unable to open the virtual machine console using the Google Chrome browser and you might not be able to connect to devices.
When the NPAPI support in Google Chrome is deprecated, the virtual machine console provided in the vSphere Client Integration Plugin might no longer function when the Chrome browser is updated. Inability to open virtual machine console using Google Chrome browser when NPAPI support is deprecated
Here is a quick excerpt from the vSphere 5.5 Update 2b release notes: The reason for this is due to the deprecated and eventual removal of NPAPI ( Netscape Plugin Application Programming Interface) based plugin support from all modern web browsers which the current VMRC implementation leverages. In the latest vSphere 5.5 Update 2b release, a new standalone VMRC has been re-introduced to provide an alternative way to launch a VM console. The VMRC (VM Remote Console) has gone through several transitions from initially being available as a standalone Windows application to an integrated browser based plugin with the release of the vSphere Web Client.
0 kommentar(er)
