Yes, this fling has the features that are compatible with vCenter 6.5 and 6.0. There are certain feature like vCenter High Availability in the fling which are not compatible with the 6.5 vCenter APIs, so you will not be able to use those features using the fling.
A fully supported version of the HTML5 client is released with vSphere 6.5, and the official name will be vSphere Client. We won't be renaming this Fling, but may start saying things like 'vSphere Client Fling' in addition to the other terms we've used before. Fling features are not guaranteed to be implemented into the product.
Apr 02, 2019
The SPAM remarks that are being posted here of late, are really uncalled for. Can they be deleted & blocked?
Mar 28, 2019
In an older build I noticed that I could go to the root URL (https://vcenter.domain) and it would redirect/load the /UI page automatically. Now after upgrading to the most recent build, if I try to reach the same URL I get a 404 error:
HTTP Status 404 – Not Found
Type Status Report
Message ProxyServlet: /
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
If I use the full URL of https://vcenter.domain/ui the fling loads properly (my main vcenter is https://vcenter01.domain).
Any reason why this changed?
Mar 28, 2019
After the 4.x upgrade, I cannot login to the https://IP:5490 page. The message is Login failed. How can I fix it?
Apr 01, 2019
Have you tried with:
user:root
password:demova
The root account may be locked if you fill in wrong password too many times.
Load more
Does the fling have feature parity with current v6.5 vCenter? Could I use this for all vCenters not at 6.7 ? Or just use for those below 6.5 ???