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.You can access the list of features/functionality not available in the vSphere Client released in 6.5 by the link in the vCenter Server’s landing page ( which links to this article.You can access this client by this URL – This HTML5 based client was originally released as a fling back in March 2016 and has been releasing a new version every week. The vSphere Client is part of the vCenter Server (both appliance and Windows) and is configured to work out of the box. In vSphere 6.5, we have released a supported version of an HTML5 based web client which we call “vSphere Client”. Our long-term direction is to utilize HTML5. VMware agrees that Flash is not the solution for the long-term. A detailed FAQ can be found here in this KB article a summary of the changes are given below in this blog post. VSphere 6.5 brings with it significant changes to the vCenter Server management clients including the vSphere Web Client and new HTML5 based vSphere Client.
0 kommentar(er)
