Hard to belive that vmware force his management down to hyper v and ignore all shouts of the community for one complete major release.
Just to clarify i love esxi the hypervisor relieable and high end technology but this web client is a pain and the customers ignored it in 5.1 and complained about the "performance" 24/7.
But vmware does not need to listen and going straight forward in 5.5 and promised better performance. They missed to in fix the performance issues (which is by design with java and flash and this is a known fact since 10 years) wich does not exist in the vic client in the most of my customers environments.
Now we are at the stage that you cant belive the vic client because lot of features are not maintained to display stats and settings (like port number of standard switch) of the vsphere version 5.5 and we have an increadible useless for all web client not for use in an enterprise enironment because of the dependency of java, flash, ie security, local admin rights, gpos and all the other security features vmware ignores for one major release.
Thank you vmware to close the management tool gap between vmware and hyper v wich is increadible shit.
And keep stop listen to the companies below gardner top 100, no one need them!!
And by the way i want Maps back, this feature disappeared completely.
VMware hears you!
We understand that the vSphere Web Client is not meeting expectations and we are actively working on solutions. We apologize for our missteps and hope that you will continue to provide candid feedback so we can get this right.
A global team has been assembled and is working around the clock (literally) in parallel work streams to address the concerns expressed by our customers. Performance and usability of the vSphere Web Client will be addressed in both near-term and long-term product roadmaps. In addition we are exploring the feasibility of extending the life of the vSphere Client (aka C# Client) and future options with HTML5.
If you would like to be directly involved in this process please give us your contact information at http://www.surveymethods.com/EndUser.aspx?D4F09C85DD91888ED2
Group Product Line Manager
Thanks for info, Matt. At least we see someone is listening and VMware is aware of the situation, working on solution. Too late imho, but better late then never...
I do not want to mix into your business, but if (as you wrote) VMware is trying a) to extend C#-client life, b) to improve performance & usability of current web-client and c) to develop (I hope!) new html5-based client, you are terribly splitting your dev-resources. Maybe it would be better to skip "b". Just to fix C#-client asap so that it can do everything what current web-client can (except freezing, crashing, etc), then to concentrate fully on developing "next-gen" (maybe html5-based) client.
I mean, forget current flash-based web-client. It is not worth the effort. Even if you improve it, who is going to use it? And for how long? I see it in my everyday life: more and more of my business-partners strictly forbid any flash on corporate-network. No exception, not even for ESXi, period. Some of them even moved to different hypervisor, just because of this (and if they accepted those extra costs, they will probably never move back to ESXi). You know it is happening, and it should fire alarm in VMware-headquarters (if it is not already ringing).
I remember reading somewhere 2014 being called "the year when flash died". The clock is running, so you'd better have something ready ASAP. I personally could live for year or two with C#-client (with added functionality which I'm terribly missing). But I'm pretty sure I will not be able to manage ESXi-servers with your flash-based web-client for year or two even if web-client was much faster...
MATT - thanks for your reply! I hoped this post is a catalyst for change, and in the meantime its a good place to vent when dealing with the web client, we all need a place to scream without disturbing the neighboring cubicles..
Matt, I thank you as well for the response. I ran across this thread from a search for "vsphere web client lacking" after a somewhat frustrating day of working with it. I'm a newcomer to vMWare in general, so I don't have a huge background with the C# client or a bias toward it all that much. But I can say that trying to work with the web client is hard to get used to, even with only a little exposure to the alternative.
Menus are in different places (different doesn't mean bad, necessarily, but it seems like there isn't much reason to many of the changes). It runs much slower than the old client, but I do also know as another poster mentioned that this could be due to resources being underprovisioned on our vSphere (as well as the rest of our virtual environment). That said, the C# client still operates much faster than the web client. In general, I don't like web-based management solutions because they all seem to be less efficient than their predecessors (Lync 2010/2013 vs OCS, for example).
I may be brave and join that volunteer corps myself...
Frustrated Enduser Hat on:
Being in the IT for more than a decade, I always hated the new technology that has come up at first since I had been so much used to the older one but got used to the new ones in due time and started loving it. For ex: facebook interfaces changing 6 months, Win8, Mgmt UI for Servers.
But in the specific case of webclient, doesn't matter how much I try to like it by using it every day in my day to day work, it still stands to be hated tough, given the base idea that it is supposed to ease our work with one point of management on different products of VMware. It stands out an exemplary example to have a look at other options and the Basic question "Why the force move asking users to use web interface rather than the C#"? Its the move like these which got several giants topple..
Frustrated Enduser Hat off:
I do have to agree that VMware is trying to patch up the issues addressed on the webclient front. But with heavy products relying on vSphere platform and more and more features being available only on webclient, its a very very slow process in a race to the mountain"
"In other words, VMware bought a knife to a Bazooka fight "
Just to add a few more, I have been using from GSX time and was very attached to the web browser we need to use to manage servers till 3.0.x and when I heard about webclient coming back, I was pretty happy to install and use it . Meh...
I fully agree. I can see a reason to have a webclient to create a portal for a user that has delegated access to one or more VMs. Even for monitoring the environment from an operational point of view. But to do the main management of your VMs as an admin on a day-to-day basis you need either a client or a really fast responding webclient (which this one is not). The vSphere client isn't blazing fast either but at least it feels more comfortable.
Since I am not the only one saying this I hope VMware will listen to what customers are saying and will make the right decisions. The options I see are:
- either find a way to make the websclient super-responsive and as comfortable as a desktopclient
- or go for the desktop client again
- or start developing for both clients again
I totally agree, and absolutely hate the web client. Web apps in general suck, but for an app as complex as the vSphere client it is totally insane. DUMP THE WEB APP, NOT THE WINDOWS CLIENT!!!!
Frankly, most web clients are a horrible disappointment. The purpose of them was to be platform agnostic (Windows [WhichOne?]?, Linux?, Mac?) and provide a more streamlined approach to delivering upgrades and enhancements without having to install new software and manage client cycles in addition to the server side.
With very few exceptions, NO ONE has been able to do that. I would list some very specific software-based network management products from a major network equipment manufacturer, but I don't want to create any problems.
Suffice it to say that every new version requires specific versions of specific browsers and specific versions of Java -- and the versions haven't been all the same or compatible in the past resulting in the need for different VMs just to run the clients to manage the VM-based server installs. Maddening!
I agree with many voices out there: dump the web-client and just give us an app (C#-client). With all the work you're going through to try to make it fast and cross-platform compatible, cross-browser compatible, whatever, you could have had great client for Windows (or linux, or whatever) -- but the OS doesn't really matter because most people are going to run it in a VM anyhow! Just make a linux-only version and tell us to run it in a VM -- problem solved (and stable.)
I have to agree with the OP.
I have tried my best to use the web client with an open mind, but I am constantly asking myself why I bother to use it. I use the webclient nearly 90% of the time, but I do fall back on the desktop application or powercli when doing some things.
Things I dislike:
- UI design is radically different from old desktop client. Navigation is generally slower even if the webclient were to be more performant (there is more clicking involved).
- Requirement of a plugin (which is buggy and doesn't fully work)
- Performance (slow login, slow page loads, etc. There is even a delay to load the login dialog box!)
- Snapshot management (now multiple pages)
- Bug with VM lists. Sometimes webclient allows you to expand the list, but mostly you have to click on the list and scroll through it on the right.
- Update Manager is clunky to use. Keeping hosts patched should be a priority!
I REALLY hope that the C# client remains forever, or until Windows becomes a thing of the past. I know that you've put many hours and cash into the web client, but I fear that you may be trying to pimp out a Yugo. (sorry, that was the only analogy I can think of at the moment) However, if it is mandated I would suggest at least keeping the layout of the original client, and add/change things a little bit at a time as newer releases come out. I think that would help with the transition.
I like that you bring up the plugin issue. I'm not sure what bug(s) in particular you're referring to, but to me it seems like having to download and install a plugin defeats the purpose of *not* having to download and install a client. Isn't the purpose of getting rid of the C# client to prevent users from having to download software in order to manage VMware?
Outside of that, I honestly don't understand the industry-wide move toward web interfaces. If you still have to install special plugins and/or software, how are they improving anything? Just some more thoughts!
For our company (Finacial) it is a operational risk that our VM's with VM version 10 cannot be managed in case our vCenter goes down. VMX10 support in C# client should be prio 1.
Thanks for acting, even though it's almost too late.