A fundamental part of this high touch engagement model is users staying as up-to-date as possible, and most of our Fling users are doing just that, so thank you! While this pace and model of delivery may not be used for the fully supported releases, due to testing time required, we likely will continue to use the Fling releases to stay on track with users. Sometimes this means simple bug fixes, sometimes this means changing our priorities to better address user needs. More importantly, we’ve been able to quickly incorporate user feedback into the product. We’ve been able to release a new version of the Fling every week, with new features, bug fixes, and performance improvements. One benefit of the Fling delivery model is very fast turnaround. We also plan on making additional improvements to make it easier for C# users to transition. With this Fling, we’ll keep the user experience mostly the same as the Web Client, which we’ve improved, based on your feedback. Many have already tried out the Fling ( ), with approximately 40% of survey respondents deploying it into Production and using it daily to manage their critical environments. The new vSphere Client is the best way to achieve that goal. This decision is about VMware trying to provide the best user experience: a fast, reliable, scalable modern interface that allows you to get your work done is our primary goal. We decided to focus on bringing the new vSphere Client (HTML5 based) up to speed as fast as possible, simultaneously offering a great user experience and getting off of Flash. This may have been okay in a vacuum, but the required resources would have severely impacted the progress of the new vSphere Client, only to end up with four clients for users to juggle.
But now that time is ending.Īdditionally, due to the shift in backend services going from vSphere 6.0 to the next version, updating the Desktop client would have required a huge investment. We have made the Desktop client available during this period, which was much longer than originally planned.
VSPHERE DESKTOP CLIENT DOWNLOAD UPDATE
We also continued to listen to our customers, making further efforts to improve the Web Client experience have been made across 5.5U3, 6.0U1 and 6.0U2, including VUM (vSphere Update Manager) in 6.0U1 Web Client. While there were certainly issues with the 5.5 and 6.0 Web Client, many users that committed to the experience came to enjoy many of the new features and usability improvements. VSphere Web Client has always been intended to be the replacement for the Desktop client, and many of our users have tried to embrace this during the vSphere 5.5 and vSphere 6.0 periods, spending their time working within the Web Client even with the Desktop client available. The last (and biggest) one to tackle was the management interface for vCenter Server. All three of these were very well received and have become the official interfaces for their respective components. VMware has been working towards the transition to HTML5 with the Platform Services Controller UI, vCenter Server Appliance Management UI, and the Host Client. We’ll be referring to the new client as the vSphere Client, as it better describes the product, and isn’t a ten syllable mouthful (vSphere HTML5 Web Client). Like the Embedded Host Client Fling (which made it into vSphere in 6.0U2), we plan on bringing this product into a supported release soon.
Second, we want to talk about the recent vSphere HTML5 Web Client Fling, user adoption, and VMware’s focus on bringing a great user experience. You’ve heard this from us in the past, but we’ve been waiting for a sufficient replacement before finally moving forward. Current versions of vSphere (6.0, 5.5) will not be affected, as those will follow the standard support period. First, the C# client (AKA Desktop Client/thick client/vSphere Client for Windows) will not be available for the next version of vSphere. Today we have two important announcements.
0 kommentar(er)
