1 person found this helpful
you are 100% right
the new web client is suck (6.5) also
Nice to see the vsphere web client revolt is still going strong. No question the HTML5 version is much better than the POS flash based one but it STILL isn't an administrator level management client. Great to give a developer so they can access a handful of VM's but is complete crap for actually administering your entire company. So sick of VMware ignoring us and simply reassuring us we'll love the next version.
Anyone know how to get the wanna be social media forum to quit showing my real name? What a PITA
Sorry not going to read through 44 pages and 3 years of posts... I never really post anything here for I been hanging on to version 5.5 for the last 3+ years but I am now being asked to upgrade to the latest version 6.5, I have a lab environment and upgrade my vcenter server and esxi hosts to 6.5
My opinion is that vsphere web client was junk 3 years ago when I first tried and it is still JUNK now 2018, and now we are being forced to only use this junkarse piece of code on 6.5
The upgrade did not go smoothly as usual but I worked trough it all and got in, everything working until the last reboot of the vcenter server which I now get this:
The HTML5 version works but I also see this:
NO WAY I UPGRADE TO 6.5 and if really pushed to upgrade I will only go to 6.
For the thousands of $$$$ my company pays VMware to licensing and support one would figure their developers would be working hard to deliver a fully working product, I dont understand why move away from a perfectly working interface like C# to something that is in war between Chrome,IE,Firefox and buggy as heck. Is VMware serious? Maybe it is time to start looking at Hyper-V and cloud based solutions from MS (which will most likely be junk as well)
Done venting and ranting.
Is there away to make the Thick Client work even if it's not supported?
The FLASH and the HTML 5 clients are not working reliably.
If your on 6.5, your screwed, C# does NOT work with 6.5.
And the reason that...along with a million other administrators are staying on Version 6.0 until the end of days. No god damn way would I go to 6.5 with ONLY the WEB CLIENT for Management. That is a F#$%ing Nightmare.
VmWare really do not give a shit about the complaints they get from us...as long as the $$ keep rolling in...why would they care??
They do say: "we listen to our customers" be everyone in this forum knows that its true...they listen.....but DO NOT do anything other than promoting their own agenda.
Done with VmWare......when its time to move past 6.0 we will go MS Hyper V. Vmware just does not care...so piss on them.
"I love it when I go to edit a VM's network settings, only to find out the web client edited a VM other than the one I right clicked on, causing a service outage." -said no one ever. Yet that seems to happen to my staff every week or two.... How hard is it to make the friggin' thing set the context to the device you actually clicked on, wtf.
At least vMware is consistent. Years had passed, but client remains as bad as it can get.
It's actually laughable that they had to take FLING of some guy and implement it as management option.
So after upgrade to 6.5 I'm daily fighting with web client(s). We have two. Bad and worse. Can not decide which one is worse.
Using flash in FF, sometimes keyboard is not working (can not type to flash based content). Need to log out and log in again. Need to see more disks on vm? Need to click some button which shows some small window, where it can not fit.
Perhaps worst is Recent task list -- it keeps scrolling, when there are new task in queue and when you need to check some older task, you can't find it.
Upload and download from datastore - total pain. You are redirected to esxi host (which have vcenter signed certificate - untrusted to browser), so you get error. After adding exception, you will find out, that you need permission to host (Host > Configuration > System Management - manipulate the file system on the host).
...and sometimes flash just crash, and you got only exclamation instead vsphere client.
Years has passed and no working vsphere client.
It has been two months since the last update.
Does this mean 6.5 HTML5 is acceptable for everyone?
We are still on 5.5 and trying to hold off for as long as I can but it's not looking good because now support is starting to use that as an excuse when we have problems.
Should I just bite the bullet and upgrade?
No, I think vmware has just been successful in their effort to beat their own customers into submission by accepting this broken thing as the new normal. I still run into issues with it daily, especially related to it not displaying up to date data, making changes to the wrong entity because the dialog box reflected the correct name but the settings were sent somewhere else, etc. It's a pile of sh*t, and they stopped caring a long time ago. I still get happy hey the vmware CEO wants to hear from you, fill out this awesome survey emails though; always do, nothing changes.
Myself, the author of this post, have been using the vCenter 6.5 latest build with web client, and although it has major refresh issues, and some other quirks, have been much happier than in past days.. That being said, still using FLASH for full functionality, HTML 5 still not fully ready, still shows up as partial functionality when accessing the website.
One things I've pin pissed off about is alerting and logging functionality. It seems to be very finicky and inconsistent. I believe VMware, if it wants to stay on top of the private cloud, needs to start looking deeper at some of the bugs that still exist in the basic functionality and work toward better stabilization.
VMware seems more interesting in competing in public cloud, a space in which it can't compete in at this point, or come even close to winning, than stabilize its private cloud.
Also, this move to outsource support to India, wow talk about horrible support.. if I had a dollar for every ticket I open that I resolve myself before they even get to me I'd be rich..
just a few weeks ago I got tired of the slow boot times and took a look at the VM kernel logs and saw WAY too much time being spent on storage tasks during boot, and I suspected an issue with the new build or possible with our storage config.. I opened a ticket, got back NOTHING of value from support other than "these 2 LUNs have some issue, talk to your storage team." So we opened a ticket with HDS and they said everything was fine. then I opened a post here on VMTN and got the issue resolved instantaneously by others who had the same issue, RDM causing slow boot. Resolution = setting the devices as perennially-reserved. Now, I felt a bit embarrassed not having known about this after having been working with the product for so long, because the KB was a few years old.. which is concerning that the support team wouldn't know this and provide an immediate answer to the support ticket...
VMware - you want to deliver a survey - but you don't need to - you just need to pay attention to what your customers are saying right here.
- bring support back home to the USA with properly trained and experienced engineers, or at least Toronto
- fix the bugs that have existed for a long time, stabilize the private cloud, don't be too confident that you own this space because Apple has already publically announced that it ditched you as its preferred private cloud virtualization layer
- Forget about trying to sell VMware cloud on top of AWS, nobody wants your cloud over cloud solution, its failing.
- work on getting proper documentation updated, its horrible, a total mess.
I have hope this can get better HTML5 Has been . OK 6.7 looks stable so we see
But i would love to see a Mac and Win Thick client Back
1 person found this helpful
Thick client is gone and will never come back.
I updated to 6.5 U1g and the HTML5 client got worse. It's buggy, doesn't reply half the time (needing a refresh and re-accepting vCenter certs), and I can no longer click on top level items and have the client refresh. I have to have the flash client open anyway because there's so many things the HTML5 client can't do, so I guess that's where we are right now.