Works fine with vDS. Did you create an IP Pool for this? You'll need to do that and associate the vDS port group to the IP Pool.
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 04, 2016
Hello,
We have our vCenter windows install on D:\ drive.
It is apparent from the .bat file and from the /etc/vmware/vsphere-client/vsphere-client/webclient.properties files that C:\ is hardcoded.
Could we please get updates in the instructions to clarify which files need to be edited IF the vCenter server has been install on a drive other than C:\
Thanks in advance,
Justin Rowling
Apr 05, 2016
Will do! Thanks for the feedback. We'll see if we can do this in some better way.
Apr 01, 2016
I tried it, and completely satisfied. it`s so snappy
at first I faced with common error;
HTTP Status 400 – An error occurred while sending an authentication request to the vCenter Single Sign-On server – An error occurred when processing the metadata during vCenter Single Sign-On setup – java.net.UnknownHostException:
by restarting init.d nothing happened.
I filled out th DNS IP adr in web client and this issue fixed.
Load more
I deployed the OVA (Windows vCenter) but once done, I can't even ping it.
All settings are correct in Options -> vApp Options -> Advanced -> Properties.
Is it supposed to work when connected to a dVS ?