VMTN

Hello, My experiense with a small site : 3 hosts vmware essential plus 6.5

Actually, the only working flash web client is [Windows] Internet explorer, not even edge.Firefox with flash hangs randomly, even with clean profiles an fress install.

- [Windows] vmrc plugin is needed. html console, with a french keyboard is a joke.

- Experience with Linux browser is in progress with HTML5 but still unusable cause of HTML VM consoles.

So why replace a [Windows] Fast, easy, reliable tool C# client with a SLOW Browser tool  full of [Windows] required plugins ?

Please, Give us back the thick client. Nothing to gain with the web interface.

Seems that you cannot sort your VMs after Host CPU, Host MEM or Status. Handy "feature" again.

vcenter 6.5 build 4944578.

I just have to say, that this vmware webshit is a gift that just keeps on giving. It's truly made managing servers a living hell and wont be forgotten when we are deciding what to buy next.

Hi hyvokar,

Can you provide a few more details:

1) Which views are you interested in being able to do this on specifically: [vCenter] -> VMs, [Datacenter] -> VMs, etc?  There are very strong performance considerations depending on the view.

2) Is this happening in the Flash based vSphere Web Client?

3) Is this happening in the HTML5 based vSphere Client?

And thanks to who knows what, I'm now unable to access vCenter 6.5 from Chrome...

I am experiencing the same exact issue after updating to 6.5. I have issues with Firefox as well.

Now this is addressed known issue...Shockwave Flash has crashed issue in Chrome.

Not sure I'd consider install a browser that is not part of corporate policy, then add the ridiculously insecure Adobe release of Flash on top, as the issue being addressed.  I'm sure vmware thinks it's a great solution though.

Having the same issue with Chrome.... trying to deploy an OVF template.  Tried IE but can't because it has a 4 GB upload limit. *facepalm*

VMware, listen to your customers!!!!!!!!!  Up until you removed the C# client in 6.5 I was a huge fan and ALWAYS recommended vSphere as the best solution.  Now, I can't.  I have clients that I won't upgrade to 6.5 because they will be frustrated with the web-client (and thus put the blame on me). 

You went from a super-stable C# client that was super fast and slick to a slow, cumbersome web-based client that is relying on third party software that gets updated with no influence or prior testing from VMware.  How anyone thought this was a good idea is beyond me.  You want to support Linux/Apple?  Fine, have the web client AND the C# client. 

I cannot believe that this i still a problem I can only get the web client to work half the time if I am lucky.   There is absolutely no excuse for this and VMware needs to scrap the web client and admit that they were wrong and refund 1 year support to every  company that pays to for support to make up for this total disaster.  I don't have time for this!

a KB article has been published/updated with some workaround steps.  We are continuing to investigate as well

Shockwave Flash crashes with vSphere Web Client 6.5 (2151945) | VMware KB

Pasting the workaround steps here for easy reference (but these may go stale as the KB is updated)

-------------------------

Caution: This has not been verified by Adobe. fp_27.0.0.159 is not the latest version,  the latest Flash version is 27.0.0.170.

Workaround for FireFox:

1. Click Start > run, type appwiz.cpl and click Run.
2. Uninstall Adobe Flash Player 27 NPAPI Version 27.0.0.170.
3. Download https://fpdownload.macromedia.com/pub/flashplayer/installers/archive/fp_27.0.0.159_archive.zip.
4. Extract the fp_27.0.0.159_archive.zip\27_0_r0_159\flashplayer27_0r0_159_win.msi.
5. Close FireFox.
6. Run the extracted flashplayer27_0r0_159_win.msi.
7. Click Start > run, type services.msc and click Run.
8. Disable Adobe Flash Player Update Service.
9. Open the vSphere Web Client in FireFox.

Workaround for Chrome:

1. Download pepflashplayer.7z available at https://bugs.chromium.org/p/chromium/issues/attachment?aid=307292.
2. Extract the pepflashplayer.dll to the Desktop.
3. Open C:\Users\%username%\AppData\Local\Google\Chrome\UserData\PepperFlash\27.0.0.170\ in File Explorer.
4. Rename pepflashplayer.dll to pepflashplayer.old.
5. Copy the pepflashplayer.dll extracted earlier from the desktop to‘C:\Users\%username%\AppData\Local\Google\Chrome\UserData\PepperFlash\27.0.0.170\.
6. Open the vSphere Web Client in Chrome.

Intentionally running an out of date version of Flash is a workaround to use the product I'm paying for?

The problem is that the web client continuously has one issue after another. It has never really worked reliably.

I've always disliked the web client. I've been using VMware products since ESX 3.5 and I've found the thick client to be reliable and stable.

However, the web client is an unmitigated disaster. It's slow and frequently suffers from graphical corruption where sometimes you can't see what you're meant to be clicking until you force a refresh. This is bloody dangerous!

Please listen to your customers AND especially the techies that keep recommending your products; which is becoming more and more difficult!

As if right on cue, a weekly reminder of why downgrading Flash is not a workaround:

Red Hat Product Security has rated this update as having a security impact of Critical. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

 

The flash-plugin package contains a Mozilla Firefox compatible Adobe Flash Player web browser plug-in.

 

This update upgrades Flash Player to version 27.0.0.170.

 

Security Fix(es):

 

* This update fixes one vulnerability in Adobe Flash Player. This vulnerability, detailed in the Adobe Security Bulletin listed in the References section, could allow an attacker to create a specially crafted SWF file that would cause flash-plugin to crash, execute arbitrary code, or disclose sensitive information when the victim loaded a page containing the malicious SWF content. (CVE-2017-11292)