Hi and thanks for the feedback!
This is certainly not intended. We're investigating the problem.
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 02, 2020
Hi Martin,
any new insights on my issue?
Would really appreciate it :)
Thank you and stay healthy and safe.
Feb 27, 2020
Hello. Working to configure a certificate for this product, the instructions mention running /etc/init.d/configui. This does not exist in the 15670023 version of the product. Any ideas?
Mar 06, 2020
Hi,
The link at /etc/init.d/configui was removed. It used to pint to:
/usr/lib/vmware-client-configui/scripts/configui.sh
So please use the original script and make sure you are using bash.
Sorry for this inconvenience. We will fix the documentation as soon as possible.
Best regards,
Kaloyan Iliev
Feb 27, 2020
Hello, I have an issue patching larger non-vSAN environments, as the option to remediate multiple hosts at the same time is not available in H5 client. Even according to the documentation there should be this option, but it's not there!
We have hundreds of hosts and can afford to patch 4 or even 10 at the same time, otherwise it just takes too long.
It's ok if sequential is the default (or if hosts are not in maintenance mode already), and I understand it for vSAN environments, but otherwise, HELLO?!
In the Flex client I can define the number of hosts to be patched simultaneously, but if that client is gone in the next vSphere version...?
Feb 22, 2020
I'm unable to configure the new 5.0 version. This is the output, credentials are correct.
Connecting to SSO server, you will be prompted for user's credentials
Unknown command: `mkdir'
Creating /etc/vmware/vsphere-ui/config directory
Generating keystore file and property files.
Configuration process was not successful
Configuration unsuccessful: could not connect to SSO
Feb 22, 2020
Finally got it working, I had to set bash as the default shell first on the VCA:
/usr/bin/chsh -s "/bin/bash" root
Then you can configure the appliance.
Load more
Cheers,
love the PowerAction comeback, I came across a problem/error though - I can only run the PS scripts as administrator@vsphere.local, not as an admin user from the AD/domain my vCenter joined into who holds the vCenter Administrator Role aswell. Is this intended or did I do something wrong or miss something?
Thanks in advance,
Fabian.