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.
Aug 23, 2020

The update came up to the expectations and really enjoyimg it.

Aug 13, 2020

Feb this year was the last update to this fling. Is it still being supported or actively developed?

Sep 29, 2020

Has this fling been abandoned?

Oct 09, 2020

Hi Garth,
It is not abandoned. There will be new releases but I can not give you ETA currently.

Best regards,
Kaloyan Iliev

Oct 09, 2020

Thank you for your reply. Good to know!!

Jul 15, 2020

A rather annoying issue that I've had to live with is that every time I log into the html5 client, I am presented with a error of a trial license which can not be removed. I understand that being informed about such issues is important, but could it be possible to be able to check a check box to not be reminded about this again? This could be written to a cookie perhaps? Thx!!

Jul 28, 2020

Thank you for your suggestion. The vSphere group has an Aha site (https://vsphere.ideas.aha.io/) where you can solicit support from other customers for your enhancement request. Requests with large customer support are more likely to be implemented in the product.
I encourage you to submit your idea on the vSphere Aha site under the licensing category.

Jul 28, 2020

Outstanding thank you!!

Jun 18, 2020

I am using vSphere Client version and recently stood up FAMI Build 15670023

When attempting to navigate to https://IP.address/UI I am directed to a blue screen with a red banner at the top of the the page containing the following text; "[400] An error occurred while sending a logout request to the vCenter Single Sign-On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - Failed to connect to VMware Lookup Service"

Has anyone else encountered this before and/or does anyone have advice on how to remedy it?

Jun 18, 2020

Nevermind. I found the problem. The DNS settings at https://IP.address:5480/ wouldn't save. Doing some research in this thread I found that changing the file directions was required to activate the UI updates.

Here is the relevant thread.

"due to changing the base operating system for the fling, the DNS system used has changed to systemd-resolved, which operates differently to the one in previous fling releases.

The easiest workaround is to link /etc/resolv.conf to point to /run/systemd/resolve/resolv.conf; the changes made to resolv.conf will then be respected by systemd. To do this, execute the following on the fling appliance:

rm /etc/resolv.conf && ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

The DNS servers added to /etc/resolv.conf will now be used and the changes won't be overwritten."

Once I logged into the VM from the console and ran this command I was able to successfully update the DNS settings AND save them. After that, I no longer received my above error.

Perhaps the developers could look at this as a learning moving forward and enable the actual UI for clients and admins instead of hard coding a vital setting like DNS internally?