Keep in mind that the CIP also has some issues with Mozilla Firefox starting from version 39 onwards, but they can be fixed by flipping some flags. The best course of action at the moment is to switch browsers if you need the special features provided by the CIP, provided that you haven’t updated to vCenter 6.0 already. There’s a fix promised coming within a short while, but since Google has been threatening with retiring NPAPI for 2 years now, I would not hold my breath for a quick resolution. And if you want to continue using vCenter 6.0, they have released a new Client Integration Plugin (CIP) that works with vCenter 6.0.īut, the bad news is that the new CIP doesn’t fix compatibility with older versions of vCenter, for example 5.1 and 5.5, which I’d wager is still a sizable part of the VMware vSphere installations out there. So as long as you update, you’ll be fine. The good news is that VMware has fixed the whole issue in vCenter 6.0 Update 1. Now that Google has released version 45 of Chrome the NPAPI enable-trick that I showed you a couple of months ago has finally stopped working. ![]() VMware Client Integration Plug-In not Working in Chrome? – Round 2 Home › Tech › VMware Client Integration Plug-In not Working in Chrome? – Round 2
0 Comments
Leave a Reply. |