One of the prior challenges for vSphere Administrators was that they were unable to see the real time status for their environment, causing them to continue using the Legacy C# Client or abuse the Refresh button – both of which can cause extreme load on vCenter Server. Some of the key changes to this client are:įigure 2: Live refresh enabled sections of vSphere Web Client In vSphere 6.5, we have made significant improvements to enhance the user experience of the vSphere Web Client. Until the vSphere Client achieves feature parity, we might continue to enhance and/or add new features to vSphere Web Client. The vSphere Client (HTML5) released in vSphere 6.5 has a subset of features of the vSphere Web Client (Flash/Flex). We encourage you to try the Fling and give us feedback on any missing features you want to see sooner using the built-in feedback tool. It will take some time for the vSphere Client to achieve feature parity, but we are also continually working to make the vSphere Client a great user experience. Progress can be seen on the Fling site as it develops, and is the best measure available. Note that Administrators may look to the vSphere Client Fling to get the latest features but the Fling remains UNSUPPORTED. Updates to the supported version of the vSphere Client will probably be released on a quarterly cadence, but we will continue to release new features every week via the Fling. The vSphere Client released in version 6.5 is using fling bits as of v2.7. Another source to check if a feature is available in the vSphere Client is the changelog section of the Flings page.