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.
Jun 18, 2019

It's been over two months, how soon can we expect 4.3?

Jun 25, 2019

Is this fling still being activly developed?

Jun 26, 2019

Yes, it is actively developed, just that the features which are working on would require extended times to release in the fling version.

Jun 26, 2019

Yes. It is developed. But I can not give you release date for 4.3.

Jun 26, 2019

That's great to hear. Thx for the info!!

Jul 17, 2019

Any idea how soon the update will be released?

Aug 01, 2019

I literally check here every day to see if the update has been released. Can you perhaps give an estimation of how much longer it will be before the next version is released? Weeks, months? Thanks!!

Jun 14, 2019

Hello,

I installed the HTML5 fling in order to use code capture. The HTML client works - I am able to log in, and see the UI, but the code capture red button is missing.
I installed the fling from h5ngcVA-4.2.0.0-13172979_OVF10.ova with VCSA 6.5 build 4944578
Is there anything I have missed in the installation steps, or something else is wrong?

Jun 14, 2019

Hi Kris,

the code capture feature (and the red button) is hidden by default. In order for it to appear, you have to navigate to Developer Center > Code Capture, and enable code capture through the toggle. The setting will be persisted across sessions, so you won't have to enable it every time.

Jun 14, 2019

Hello Martin,

Thank you for the swift reply! After enabling it, it works, and I was able to record the needed action - it is a life-saver :)

Kind Regards,
Kristian

Jun 04, 2019

I have Vcenter 6.0 u3 running on Windows. I am trying to run server-configure and getting this error:

Using the get-machine-id as get-ldu is returning an error for this vcenter.
Error 100001: An unknown option was present on the command line.
Using the default reverseproxyport=443 since no custom port found.
Creating ds.properties file...

Everything is installed in the default Program Files folder path. Has anyone encountered and resolved this?

Jun 12, 2019

Hi Jacob,
Sorry for the late response.
Steps for 6.0 Windows VC WITH EMBDED PSC NODE:
1.) Copy the provided 'server-configure.bat' to any directory on the vCenter for Windows. (This file is one of the Fling downloads on the top left from https://flings.vmware.com/vsphere-html5-web-client)
2.) NOTE: If you have installed vCenter into any folder other than default (%PROGRAMFILES%), the script may not find the appropriate files.
You will need to edit the file and replace the two references to %PROGRAMFILES% with the appropriate path so that the “KEYTOOL” and “VECS_CLI” paths line up.
These two variables are at the top of the file.You may also need to change this at the end of the file to the correct path (this is for the ds.properties file):
SET CLIENT_DIR=%PROGRAMDATA%\VMware\vCenterServer\cfg\vsphere-client
3.) Open an Administrator Command Prompt and run the 'server-configure.bat' script. The following files will get generated:
i) store.jks
ii) ds.properties
iii) webclient.properties

4.) In webclient.properties change
keystore.jks.path=/etc/vmware/vsphere-ui/store.jks

5.) Login to the appliance and create the following folders:
/etc/vmware/vsphere-ui and /etc/vmware/vsphere-ui/config
6.) Copy "store.jks" and "webclient.properties" from the vCenter for Windows to folder "/etc/vmware/vsphere-ui" at the appliance.
7.) Copy "ds.properties" from the vCenter for Windows to folder "/etc/vmware/vsphere-ui/config" at the appliance.
8.) At the appliance change the owner of folder "/etc/vmware/vsphere-ui" to user vsphere-ui:
chown -R vsphere-ui /etc/vmware/vsphere-ui
9.) Restart the vsphere-ui service:
service-control --restart vsphere-ui

If you have external PSC node the steps are different!

May 23, 2019

Getting this when trying to connect to vc
Unknown command: `scp'
Configuration process was not successful
Configuration unsuccessful: could not connect to SSO

May 23, 2019

Unknown command: `mkdir'

Jun 12, 2019

Hi,
The auto configuration script works only on Linux VC. For windows there are manual configuration steps:
Steps for Windows VC:
1.) Copy the provided 'server-configure.bat' to any directory on the vCenter for Windows. (This file is one of the Fling downloads on the top left from https://flings.vmware.com/vsphere-html5-web-client)
2.) NOTE: If you have installed vCenter into any folder other than default (%PROGRAMFILES%), the script may not find the appropriate files.
You will need to edit the file and replace the two references to %PROGRAMFILES% with the appropriate path so that the “KEYTOOL” and “VECS_CLI” paths line up.
These two variables are at the top of the file.You may also need to change this at the end of the file to the correct path (this is for the ds.properties file):
SET CLIENT_DIR=%PROGRAMDATA%\VMware\vCenterServer\cfg\vsphere-client
3.) Open an Administrator Command Prompt and run the 'server-configure.bat' script. The following files will get generated:
i) store.jks
ii) ds.properties
iii) webclient.properties

4.) In webclient.properties change
keystore.jks.path=/etc/vmware/vsphere-ui/store.jks

5.) Login to the appliance and create the following folders:
/etc/vmware/vsphere-ui and /etc/vmware/vsphere-ui/config
6.) Copy "store.jks" and "webclient.properties" from the vCenter for Windows to folder "/etc/vmware/vsphere-ui" at the appliance.
7.) Copy "ds.properties" from the vCenter for Windows to folder "/etc/vmware/vsphere-ui/config" at the appliance.
8.) At the appliance change the owner of folder "/etc/vmware/vsphere-ui" to user vsphere-ui:
chown -R vsphere-ui /etc/vmware/vsphere-ui
9.) Restart the vsphere-ui service:
service-control --restart vsphere-ui