vSphere Web Client integration plug-in fails in Google Chrome 50.0.2661.94 or FF 46.0.

This are the browsers giving the popup constantly,  Chrome, Firefox and IE. Actually the popup comes up opening Chrome or IE, but references FireFox.

Sorry, PITA?

Pain in the arse (PITA)  a technical term!

This client has always been an issue with current versions of vSphere, I believe is changing in the future, lets hope.

Gotcha, show should close the case/question be closed. I'm not authorized to open a pay per incident case w/VMware.

Please leave it open, and see if anyone else has any ideas.

I've requested that this question be deleted for the following reason:

I cannot open a ticket with VMware and no one else has responded.

Also have this problem and had an open request with VMware for weeks with no solution but to reinstall browsers and integration clients multiple times. THAT'S NOT A SOLUTION. Running 5.1 here

I've removed all clients. Installed 6, but have not removed chrome. Are you saying that removing browser DIDN'T work? This just started when I went to 6. 5.5 worked fine.

I'm on 5.1 and have issues with both Chrome 50.0.2661.102(64-bit) and Firefox 46.0.1 (64-bit) here. the plug in is installed. I've tried rebooting, deleting and reinstalling browsers, deleting and reinstalling the Integration client and nothing gets it to allow the check box on sign-on or the remote console one logged in.

hmmm, I had no problems from 5.1 to 5.5. 6 is my bear.  VMware told you to uninstall clients, pluggin and browser?

Correct and nothing has helped here

Integration client is a big problem for VMware Support.

We have workstations, we have *NEVER* got it to work on.

Great. Guess we better keep a Windows 7 box around that can run the VMware client reliably since Windows 10 can't and the web client apparently can't reliably bring up a console. What a mess.

We've been doing this for years, we have an unpatched Windows XP, Windows 7 VMs for this very purpose, because Windows patches break the vSphere Client, Web Browser Updates break the Web client, and for us as clients, which manage many vSphere installations, it's very important, we have working solutions!

We've been suffering for many years with issues like this...

you can see here logged on EE

https://www.experts-exchange.com/questions/26667285/The-type-initializer-for-'VirtualInfrastructure-Utils-ClientsXml'-threw-an-exception.html

and this was before I started answering questions here.....

Unfortunately we can see why VMware are keen to move away from the C# client, because of patch and Windows issues, and move to a Web Client, but it also has issues with browsers.

Andrew: then why would they terminate the desktop client? I mean, I guess if your wanting to access it from the web, but there's other solutions for this too.

Andrew: then why would they terminate the desktop client? I mean, I guess if your wanting to access it from the web, but there's other solutions for this too.

It's been known for many years, that VMware have been trying to discontinue the vSphere Client C#, less and less plugins and features are available in the vSphere Client e.g. vSAN Management, Shared Nothing Migration, management of v10 and v11 virtual machines.

You would have to discuss the question as to why with VMware,

You can read this post I made here in the VMware Group on EE

https://www.experts-exchange.com/discussions/217602/vSphere-Client-C-R-I-P.html

My guess, double the development, a team developing the C# client, and a team developing the Web Client or HTML 5 Client, cut backs and costs.

The majority of access is Web based and has been for many years, always strange that there was a standalone client, we don't like the decision believe you me, but it's been made.

don't work here, we only run 32 bit Firefox! fails on all other browsers, but Windows XP works fine!

however Chrome End of Life on WinXP.

I had no problems until upgrading to the vCenter Appliance. Since it's linux is there a Client pluggin specifically for that?

it's the same for both Web Clients on Appliance and Windows

I don't know then. I don't like it though. Is this a known issue with VMware?

Yes, its problematic!

Still no solid solution to this problem.

Still no solid solution to this problem and don't have the funds to open a ticket with VMware.