WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / vSphere 6.0 / Quick Tip - Fix for CIP no longer functioning in vSphere Web Client after Chrome 45 update

Quick Tip - Fix for CIP no longer functioning in vSphere Web Client after Chrome 45 update

09.11.2015 by William Lam // 39 Comments

For those of you who recently updated to Chrome 45, which apparently I did as well or more likely it automatically did it for me. You may have noticed that the Client Integration Plugin (CIP) for the vSphere Web Client no longer function when you try to upload an OVA or trying to use the Windows Session Authentication feature. The latest release of Chrome has now completely disabled NPAPI support, but luckily there is a simple fix.

You simply just need to download and install the following new version of the CIP package for either Windows or Mac OS X and you will be able to restore the functionality that you once had which no longer relies on NPAPI. This fix applies to both a vSphere 6.0 and vSphere 6.0 Update 1 environment which I was able to test myself as I have both deployed. If you are still having issues after installing the update, make sure you clear your browser cache as the old plugin may still be cached. Some folks had to perform a reboot, especially if you have more than one user on the system which could still have existing running processes.

UPDATE (10/27/15) - For customers running vSphere 5.5.x, the NPAPI fix has just been released as part vCenter Server 5.5 Update 3a. The fix includes both a server side and client side component. This means to apply the fix, you MUST update BOTH the vCenter Server as well as the updated CIP which is provided when logging into the vSphere Web Client. For vSphere 5.0/5.1 customers, the only work around is by following this VMware KB 2114800.

I want to give a big shoutout to my buddy Blair who shared this KB with me as I was having issues after the Chrome update.

Client Integration Plugin for Windows:

  • http://vsphereclient.vmware.com/vsphereclient/2/9/9/4/0/4/1/VMware-ClientIntegrationPlugin-6.0.0.exe

Client Integration Plugin for Mac OS X

  • http://vsphereclient.vmware.com/vsphereclient/2/9/9/4/0/4/1/VMware-ClientIntegrationPlugin-6.0.0.mac64.dmg

You can also find more details noted in this VMware KB 2130672. For vSphere 5.5 customers, a back port is currently being worked on but there is currently not an ETA. When is it released, the KB will be updated and you can subscribe to it for the announcement.

More from my site

  • Quick Tip - Silent installation of the VMware Client Integration Plugin (CIP)
  • What is the VMware Client Integration Plugin (CIP)?
  • Accessing the vSphere Web Client from a Linux desktop?
  • How to restrict vSphere UI access while maintaining vSphere API functionality?
  • Why does Deploy OVF Template operation show vpxd-extension-[uuid]?

Categories // vSphere 6.0, vSphere Web Client Tags // chrome, CIP, client integration plugin, NPAPI, vsphere web client

Comments

  1. *protectedneocontrast says

    09/12/2015 at 3:43 am

    Is there no package for Linux?

    Reply
    • William Lam says

      09/12/2015 at 4:21 pm

      That's correct, vSphere Web Client is also not officially supported on Linux (though it'll work if you use Chromium, but you won't get certain functionality as CIP is not available)

      Reply
  2. *protectedPsv141 says

    09/12/2015 at 6:02 am

    And what about VCD webmks?

    Reply
    • William Lam says

      09/12/2015 at 4:22 pm

      webmks is for the console which doesn't use NPAPI, it's HTML5 based VMRC. This is only for CIP functionality like upload ISO/OVA and I don't believe this is applicable to VCD

      Reply
  3. *protectedJeff says

    09/12/2015 at 11:49 am

    VMRC on my Mac has been flaky too after last upgrade or couple upgrades. To be honest it seems I have to go back and forth between Chrome and Firefox and Mac and Windows everytime some browser update comes out. I hope eventually all this settle down.

    Reply
  4. *protectedp3opl3sh3ro says

    09/12/2015 at 3:58 pm

    I still have the same issue after installing this updated plugin. Still troubleshooting it...

    Reply
    • *protectedJeff says

      09/12/2015 at 4:02 pm

      I too have the same issue still.

      Reply
      • *protectedp3opl3sh3ro says

        09/12/2015 at 4:11 pm

        Actually, I guess this is only a solution for customers running virtual center 6.0 and we are still on 5.5 and do not appear to have a fix. At this point the option for us is to install a previous version of chrome and disable automatic updates.

        Reply
        • *protectedjeff says

          09/12/2015 at 4:15 pm

          In my test lab of v6 U1 still doesn't work. I reinstalled chrome and the plugin under Mac.

          Reply
          • William Lam says

            09/12/2015 at 4:19 pm

            Can you check to see if you have any vmware-csd processes that might still be running? If so, it could still be loading the old library. You shouldn't need a reboot but in case you haven't tried that to ensure that's all cleared

          • *protectedjeff says

            09/12/2015 at 4:26 pm

            I did reboot and same issue. Frustrating 🙁 We are looking forward and testing our first possible VSAN deployment with v6, but with stuff breaking every browser update it's very concerning.

          • William Lam says

            09/12/2015 at 5:28 pm

            Jeff,

            It is indeed frustrating and sorry to hear this your experience. I've pinged some folks internally to see if they have any other suggestions but I would recommend to you and others who are still having problems after updating to this version of CIP to file an SR, just so we can track it to full resolution. I can confirm that you do not need to be on vSphere 6.0 Update 1 to get the fix, I just installed CIP on another environment (Windows) which is running VCSA 6.0.

            Out of curiosity, what is the platform of your vCenter Server and build of vSphere? as well as your client desktop? This might be helpful to include in the SR

          • *protectedJeff says

            09/12/2015 at 6:13 pm

            I am running 2012R2. All latest patches and all vcenter latest patches. MacBook is all latest patches too. I will will try to look some more as well. I really want the web client to succeed!

  5. *protectedChip says

    09/14/2015 at 2:34 am

    Interesting that this version (both Mac and Win) appear to hang at the "Installing certificates and starting service..." where no previous version did. Eventually it'll succeed, but it takes between a couple to a few minutes.

    Reply
    • William Lam says

      09/14/2015 at 1:08 pm

      Yea, I noticed this as well. I guess it just takes a bit longer but does eventually succeed.

      Reply
  6. *protectedAlex says

    09/14/2015 at 12:49 pm

    What about for those of us using Chrome for v5.5 U2, is there an updated plugin available?

    Reply
    • William Lam says

      09/14/2015 at 1:09 pm

      I had asked about this and PM/Engineering mentioned this is something they're working on, no ETA but will share once that info is out.

      Reply
      • *protectedStu Duncan says

        09/15/2015 at 2:56 pm

        William,

        I very much appreciate you communicating this as it's the only semi-offical communication I've seen that an actual solution is being worked on. But as an enterprise user, it's very frustrating that this wasn't planned better as Google/Chrome had announced this a LONG time ago.

        http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
        http://www.chromium.org/developers/npapi-deprecation

        VMware left many users in the lurch because of their poor planning of a clear roadblock first put there in 2013.

        Reply
        • William Lam says

          09/15/2015 at 5:02 pm

          Stu,

          Appreciate the feedback. As you know, I try to be as transparent as possible and share any findings I know of internally with our customers. I'll definitely relay your feedback to the powers that be and hopefully we can do better in the future.

          Reply
        • *protectedShawn K says

          09/24/2015 at 5:37 pm

          THIS +1

          Reply
  7. *protectedserk says

    09/21/2015 at 9:09 am

    5.5 fix for CIP ?

    Reply
    • William Lam says

      09/21/2015 at 1:50 pm

      Please take a look at the very last paragraph for your answer

      Reply
  8. *protectedserk says

    09/22/2015 at 6:57 am

    thx for reply

    Reply
  9. *protectedsoloporhoy says

    09/22/2015 at 8:14 pm

    vmware its the most EXPENSIVE software i ever use, and now you need, the thick client to do some thing, the web client for other things,non on al browser work, not working client for linux and more stuff like that....... man they really really want us to use another product . . . .

    Reply
    • *protectedbluscreened says

      01/13/2016 at 4:04 pm

      100% agree. They really have botched this whole thing. I just don't get it. vCenter has been a mess since 5

      Reply
  10. *protectedFab says

    10/29/2015 at 12:37 pm

    Worked like a charm on VCSA 6.0 U1 & Chrome 49.
    Give that man a cookie !

    Reply
    • *protectedCorey Loper says

      03/03/2016 at 9:03 pm

      HOW ?? I have been trying to get this fixed for days. I can get the page that says install or upgrade. But the Install button does nothing. Clicking upgrade brings up a pop up. Clicking Install in IE does work, just not chrome.

      Reply
  11. *protectedRyan says

    11/12/2015 at 11:27 am

    Has anyone been able to get the CIP to work on Mac 10.11?

    Reply
    • *protectedlexone27 says

      11/12/2015 at 5:32 pm

      Yes, I have no issues with CIP 6.0 for vSphere 6.0 and CIP 5.6 for vSphere 5.5 in Chrome 46

      Reply
    • *protectedamipb78 says

      12/02/2015 at 5:05 am

      It looks like it doesn't work anymore.

      Reply
      • *protectedamipb78 says

        12/02/2015 at 5:57 am

        Safari 9.0.1 11601.2.7.2

        Reply
  12. *protectedwill says

    11/14/2015 at 12:41 pm

    Awesome! I patched to 5.5 U3a today and running Chrome 46 successfully.

    Reply
  13. *protectedbluscreened says

    01/13/2016 at 3:52 pm

    I'm on 5.5 update 3b and the latest integration client doesn't work in chrome, IE11 or Firefox. For a software company, VMware sure does mess up the basics pretty consistently. Figure out a better way of doing all this. Maybe return to focusing on the vSphere Client? Something that always worked pretty well until VMware decided to abandon it and now there are features spread between the two front ends that don't have counterparts on the other. What a mess this product has become. Sorry, I'm really bitter that it doesn't work.

    Reply
  14. *protectedBlaggy says

    01/27/2016 at 4:30 am

    Same here in my environment as mentioned in "bluscreened" post. Since the update on 5.5 3b was applied the client integration plugin is broken. I tried the all the solutions above (including the vmware kb) but nothing changed, no matter which browser I use.
    I even tried Opera and Safari on my Windows 7 Client. It is pretty poor for a company like VMware. Looks like the only solution is updating to 6.0 U1. Until then it looks like we have to use the Fatclient when deploying OVAs etc. Hopefully this will be stable then and not broken again in 6.1 or what ever the release is called...

    Reply
  15. *protectedSerge Meeuwsen says

    03/05/2016 at 2:17 pm

    And same here... This thing is now permanently broken on my Mac and I'm running 6.0U1 and the latest CIP for Mac. it just doesn't work in either Chrome or Firefox. I just can't believe how VMware just cannot get this fixed. I'm truly sad to say that after about 10 years of investing my time and knowledge in vSphere (and VI before that), I'm starting to reach a point at where it's just not worth it anymore. VMware have been sitting on their virtual laurels for too long and the "rot" has started to set in and by the looks of it, no one in management cares enough anymore to deliver the high quality software that we were used to in the past. It's all talk now. This whole fragmented (and broken on top of that) web/fat client business may well be the straw that will break the camel's back.
    The last 6 years or so I've been following up closely on Hyper-V and with 2012R2 that is now a pretty solid choice and things are only getting better with 2016's introduction of NanoServer. Finally a footprint that is even smaller than ESXi and boots 20 times as fast!!
    Sorry William to vent out on your blog, it's definitely nothing against you, really appreciate all the knowledge you've shared over the years!

    Reply
  16. *protectedSteven Peterson says

    04/06/2016 at 4:07 pm

    Patched my VCSA to 6.0U2 and ALL of the macs in our office stopped working 10.11 in chrome and firefox no CIP issue
    Working around by using fusion pro as a client to push out OVA's

    Royal Pain

    Reply
  17. *protectedannoyedvmwarecustomer says

    06/03/2016 at 6:02 pm

    Same problem here. vCenter CIP 6.0.0 on Mac OS X (El Capitan) won't work in Chrome 50. VMware better deliver that HTML5 interface soon.

    Reply
    • *protectedannoyedvmwarecustomer says

      06/03/2016 at 6:03 pm

      Or Chrome 51.

      Reply
  18. *protectedTotie Bash says

    11/16/2017 at 12:10 pm

    Hi William, what is the latest scoop on CIP for 6.0 U3c is it suppose to be supported/working? I thought it has been deprecated due to NPAPI not supported by latest browser but I got confuse on your article that there is CIP that does not use NPAPI. I know 6.5 has the new Enhance Authentication plugin as their answer but I did not think 5.5 or 6.0 has an answer to CIP issue. My users just want to use "Use Session Host Authentication" as the end goal what do you recommend?

    Reply

Leave a Reply to AlexCancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025