Chrome 45 has been released on 1st September taking NPAPI completely out from the browser disabling the VMware Client Integration Plugin functionality in vSphere Web Client.
The plugin is no longer working also using other browsers like Firefox or Internet Explorer.
As result, in Chrome the Use Windows session authentication option is not working anymore and you have to login by manually entering the credentials.
Unfortunately the login process is not the only feature that has been affected. Also the deployment of an OVF template is not working since the plugin is a required component.
Trying the access using Firefox 40 you receive an error related to an untrusted connection.
Same situation with Internet Explorer.
Reinstalling the VMware plugin doesn't fix this matter and a different solution must be found.
Trying to find a working solution, I found out Opera at the moment is the only browser that still works with VMware Client Integration Plugin. Normally I don't use this browser but I had to install the browser on my computers to manage vSphere.
From Opera website, download and run the installer.
When the installation has completed, type in the browser the vCenter Server address. The Use Windows session authentication feature is available to login. Enable the option and click Login to access vSphere Web Client.
Browser may ask to update Flash Player. Click Update Flash to proceed.
Using Opera, the vSphere Web Client is fully working.
Also the deployment of OVF packages works perfectly.
I think time has come for VMware to quickly implement a new web client maybe HTML based to avoid all these problems.
A new version of CIP package has been released to restore the plugin functionality that no longer relies on NPAPI. The fix works for both vSphere 6.0 and vSphere 6.0 Update 1.
Download the Client Integration Plugin from VMware website.
Thanks for the VMware client plugin solution! Opera is the only thing that works for me. Thank you.
Hello Paolo. Have you ever deployed esxi in e nested environment? i have been living trouble when i try to migrate Standard switch to Virtual distributed switch, virtual machines port groups are not migrating. I am following the standard migration policy. Here is my scenario.
installed ESXI on HP proliant.
3 esxi is installed on that (nested)
Vcenter is installed to my physical ESXI (main one)
Technically nested esxi's vds is connected to vswitch of my main esxi.
Main esxi's physical NIC connected to Cisco 3560.