Please provide your feedback in this short Flings' survey.
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.
Sep 10, 2019

Wow guys, thanks for the update!! Straight in my first problem sadly.

It wont upgrade from 4.2.0... after I run the bsx installer I am told to reconfigure the appliance. Does it not support upgrades anymore?

Sep 18, 2019

Hi Garth,
I see that it writes to reconfigure but if you upgrade from 4.2.0 to 4.3.0 it should not be needed.
After the upgrade, it should working OK.
Does the upgrade complete successfully?
Can you please share the results of the following commands:
cat /usr/local/bin/vsphere-h5-client-installer/installedVersion
rpm -qa | grep vsphere

Best regards,
Kaloyan Iliev

Sep 10, 2019

Is there a plan to have a way to view the LUN ID of an RDM on a VM Edit Settings panel? In the web client, one can select the disk and manage paths to see the LUN ID. Also, it would be nice to see the vmdk pointer filename for the RDM. We have several MS WFCs that require launching the web client to work with RDMs.

Sep 08, 2019

Any news? Five months & counting...

Jun 26, 2019

The original onyx standalone was able to produce javascript. This is a key feature for customers that are using vRealize Orchestrator since it uses javascript. Is this on the roadmap? Is there a way to port the onyx javascript capture to code capture? (original fling

Jun 26, 2019

Fling v4.2.0 added this capability to code-capture where vRO javascript code snippets will be rendered in the code-capture output.

Jun 26, 2019

Apologies...According to changelog it looks like the javascript capture was added to the latest version (4.2) released April 10, 2019.