Fixing the VMware Client Integration Plugins in Chrome 45

Chrome 45 sounds a bit like a weapon, and if you’re an NPAPI based plugin consider yourself shot. Earlier this month, version 45 was released which killed off all support for NPAPI plugins including the VMware Client Integration Plugin for vCenter version 5.x. If you’re like some of us who upgraded to vCenter 6.0 to avoid this quandary all together, you were no doubt surprised when the plugin suddenly stopped working.

Thankfully, VMware has fixed this issue with vCenter 6.0 U1. Although I have yet to upgrade my production vCenter server to U1, this fix seems to work with 6.0. Once we have vetted out the compatibility of vCenter 6.0 U1 among our-third party products we will complete the upgrade. Running the updated plugin on an older vCenter is likely not supported, but will get us through until the upgrade is complete.

Download the vCenter Server Appliance ISO (even if you are running a Windows vCenter Server)

Close all running instances of Chrome (Use taskkill /F /IM chrome.exe for an extra heavy-handed approach)

Crack open the ISO and open the vcsa directory

Launch the VMware-ClientIntegrationPlugin-6.0.0.exe installer

Complete the installation

Launch Chrome and navigate to your vCenter server

You should now be able to use your Windows Session Authentication again

If you are still unable to use your Windows Session Authentication…

Close all running instances of Chrome (use taskkill /F /IM chrome.exe for a satisfyingly heavy-handed approach)

Open C:\Users\User Name\AppData\Local\Google\Chrome\User Data\Local State with notepad

Delete “vmware-csd”:false,

Save the file

Relaunch Chrome and navigate to your vCenter server

You will be prompted to launch the VMware Client Integration Plugin. Remember my choice and click Launch Application

Matt Bradford

Post navigation

4 Comments

Really weird of them not to increase the version number of the fixed version of the plugin. It’s still 6.0.0 (in the file name at least), but it replaces all the files with newer versions/dates (Feb 2015 to Aug 2015).

I have noticed that with Chrome v49 that if I first login without using the “Use Windows session authentication” checkbox, but use my domain credentials then immediately logout and then use the checkbox it works correctly. So far this has worked 100% of the time for me.

If I do try to use the checkbox first after Chrome has been completely closed (and all Chrome.exe processes ended), it will fail.