vSphere 6.5 presents with significant changes to the vCentre Server Management clients which includes the vSphere Web Client and new HTML5 based vSphere Client. A comprehensive FAQ can be found here in this KB article; a summary of the changes are given below and If you want to learn more about the VSphere 6.5 you can join Getprotech . Getprotech provides the VMware Training in Delhi .
VMware admit that Flash is not the result of the long term direction is to apply on HTML5. In vSphere 6.5, they issued a supported version of an HTML5 based web client which they call “vSphere client”. The vSphere client is part of the vCenter server (both appliance & Windows) and is designed to work out of the box. One can easily access this client by this URL – http://<FQDN-or-IP-Address-of-VC>/ui. This HTML5 based client was originally issued as a fling back in March 2016 and is been releasing a new version every week.
- One can access the list of features not available in the vSphere Client issued in 6.5 by the link in the vCentre Server’s landing page (http ://< FQDN-or-IP-Address-of-VC>/), which links to this article.
- Another source to check if a feature is available in the vSphere Client is the change log section of the Flings page. The vSphere Client released in version 6.5 is using fling bits as of v2.7.
Updates to the promoted version of the vSphere Client will apparently be released on a quarterly cadence, but VMware will continue to release its new feature every week via Fling. Note that Administrator may looks to the vSphere Client Fling to get the immediately prior features but the Fling remains Unsupported. It will take some time for the vSphere Client to achieve feature parity, but we are also working to make the vSphere Client a great user acquaintance. Progress can be seen on the Fling site as it establish, and is the best measure available.
vSphere Web Client (Flash/Flex)
The vSphere Client (HTML5) released in vSphere 6.5 has a subset of appearance of the vSphere Web Client (Flash/Flex). Until the vSphere Client accomplish feature parity, we may continue to appreciate new features to vSphere Web Client.
In vSphere 6.5, we have made significant improvements to appreciate the user experience of the vSphere Web Client. Some of the key changes of this client are:
- Live Refresh improvements
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 vCentre Server. Live refresh in the vSphere Web Client 6.5 grants vSphere administrator to now see the current state of inventory.
- Client Integration Plugin (CIP) removal
In vSphere 6.5, the vSphere Web Client will have no assurance on CIP as it exits today. There is also no assurance on CIP to install and deploy the vCentre Server Appliance, which allows us to bring a cross platform installer that runs on macOS, Linux and the windows. Not all CIP functionality could be replaced by native browser functions. The “use windows session Authentication” functionality as well as smart card login depends upon the new slimmed down enhanced Authentication Plugin (EAP). All other functions are counterfeit without CIP and function natively in a web browser. It is important to note that OVF expand functionality has slightly changed with the removal of CIP. A user has to select all the related files of the OVF.
- Navigation improvements
The default view in the vSphere Web Client is now Hosts and Clusters instead of the Home page. We all stick with the Inventory Tree through other actions such as performing searches to provide a more spontaneous and seamless experience.
The related objects sub tabs have been planate and brought up as top level tabs, thus reducing the number of clicks required to go to the VMs or other objects.
Tab reorganization – the manage tab is renamed to arrange and sub tabs under the manage tab are now planate which also reduces number of clicks.
- Custom attributes
Based on popular demand, we have brought back the custom attributes to the vSphere web client. One can view and edit the custom aspect in the summary page portlets.
- Performance enhancements
VSphere Web Client performance has been exaggerated to improve the overall experience. A few of the areas which we broadly optimized are Login time, VM configuration, VM Migration and VM provisioning (New VM, Clone VM).
Legacy C# Client:
In may 2016 VMware has announced that the Legacy C# Client will no longer be available with the VSphere 6.5 release. The legacy C# Client connection to vCentre Server 6.5 or ESXi 6.5 host is untested and is not promoted.
The legacy C# Client will still be promoted with all previous non – EOL’vSphere versions. For example, the legacy C# Client would be accessible and continue to work with vSphere 5.5 and 6.0. Starting with vSphere 6.5 onwards, VMware will not ship a newer version of this Client.
VMware have made lots of advancement to the vSphere Client and the new HTML5 based vSphere Client based on your feedback. The vSphere Client comes with a built in feedback tool you can use to send us direct feedback. All the UX, product and engineering teams counsel this feedback and the use this data to itemize next set of features and make amelioration. Even if you don’t have vSphere 6.5 yet, you can use the Fling to manage vCenter 6.0 and provide us feedback.
For more information you can contact for VMware Training