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.
Mar 29, 2016

Followed the instructions and it works great! So glad to see this is in development. I'm doping you guys add VUM capabilities to this appliance!

Mar 29, 2016

It's a very long road to get all the functionality, but VUM is on the list

Mar 29, 2016

/etc/init.d/vsphere-client configure --start yes --user root --vc
Connecting to SSO server, you will be prompted for user's credentials
The authenticity of host 'nyarvc01p (10.31.40.99)' can't be established.
ECDSA key fingerprint is 47:98:aa:d1:3b:fe:fb:e3:6a:50:97:51:0f:4a:c5:94 [MD5].
Are you sure you want to continue connecting (yes/no)? yes
root@Sever password:
Unknown command: `mkdir'
Creating /etc/vmware/vsphere-client/config directory
Creating /etc/vmware/vsphere-client/vsphere-client directory
Creating /etc/vmware/vsphereFeatures directory
Generating keystore file and property files.
root@server password:
Unknown command: `bash'
Downloading keystore file and property files.
root@server password:
Unknown command: `scp'
mv: cannot stat â/etc/vmware/vsphere-client/webclient.propertiesâ: No such file or directory
mv: cannot stat â/etc/vmware/vsphere-client/ds.propertiesâ: No such file or dire ctory
mv: cannot stat â/etc/vmware/vsphere-client/vsphereFeatures.cfgâ: No such file o r directory
root@server password:
/usr/lib/vmware-vsphere-client/scripts/register_sso.sh: line 45: Unknown: comman d not found
Configuration process was not successful.
vSphere Client Web Server is not configured, please use the '/etc/init.d/vsphere -client configure' to configure:

Mar 29, 2016

you need to change the shell on the vCenter server

Mar 29, 2016

Did you follow the instructions correctly???? On the vCenter Appliance you have to first login as root, enable bash AND change the default shell for root to bash.
Had the same issue.

Mar 29, 2016

Hi Joe,

Can you SSH into your VCSA and see if you get the Bash shell or the appliancesh shell?

Mar 29, 2016

Very good initiative, love it. Installed it against vCenter 6 Appliance and works great. It is very fast, which is one of the most important aspects I think.

Two questions:
- Would it hurt my vCenter 5.5 install if i would try to get it to work? I know the requirement is vCenter 6 but I don't know if you're using vC6 specific functions or just hadn't had time to test it against vC 5.5?
- For small screen sizes, it would be great if you could easily hide and unhide the tasks pane. It is a big plus however compared to old Web Client that you by default show all users tasks.

Mar 29, 2016

It won't hurt your VC5.5. The APIs have not changed that much, so it might work, but we haven't investigated.

The first configure steps involve generating some keys or such, which is done differently for VC6.0 vs VC5.5.

If you get it work though we'd be very interested in hearing your results.

Regarding hiding/unhiding tasks, you can double click on the border above the Recent Tasks and it should minimize.

Mar 29, 2016

Though a warning: The appliance itself will try to become localhost.example.com on bootup w/DHCP enabled; this is pucker-inducing with Windows DNS and DHCP where all of a sudden you get a localhost.example.com registered in your DNS. (Where example.com = your local DNS domain name your DHCP server hands out.)

Maybe deploying the OVA in the Web Client gives you an option to customize that, but it didn't in the Windows client.
Had to set 'hostname' manually and edit /etc/sysconfig/network/dhcp:
DHCLIENT_SET_HOSTNAME="no"
DHCLIENT_HOSTNAME_OPTION="html5iscool.example.com"
(and then reboot)

You may want to boot the appliance with its NIC disconnected the first time, and then go do this.

Mar 29, 2016

Heard from somebody else that other VMware appliances have had this problem in the path. It probably should get addressed at an overall level (first-boot configuration, or allowing for guest customization, or something) since it's sort of a boobytrap if you've got a Windowd DHCP+DNS environment.