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.
With version 4.2 I'm unable to deploy OVFs, the error raised is:
Failed to deploy OVF package. ThrowableProxy.cause A general system error occurred: Transfer failed: The OVF descriptor is not available.
When using the HTML5 client from vCenter it works fine.
We are working on addressing the issue and providing fix in the next Fling releases.
I just took a look at the new Perspectives functionality as I though it might help in a use case I was asked about several weeks ago. I was asked if it was possible to allow certain users access to vCenter to view information, but not change it.
Perspectives should be able to help with this, but in my brief experiment with it has some flaws which could catch admins out if they're not careful and inadvertently allow more privileges to users than intended.
Say for example you want certain users to see Clusters, Hosts and VMs, but not change them.
If you go as far allowing Summary and Monitor for Clusters, Hosts and VMs. That's a good start. OK now lets extend it so the same users can see a list of VMs in the clusters or hosts. Uh! Oh! Although they can't do anything to a VM in the VM view, if they right click a VM in a cluster or host view now, they can do more or less whatever they like.
I think I would much prefer the restrictions set in the VM part of the Perspective Tree to be transferred also to wherever "VMs" can be listed below other parts of the Perspective Tree, like "Host" and "Cluster".
I know much of this could be covered off by creating a custom Role, but I think it would be nice to see closer integration between Perspectives and Roles. In my opinion they go hand-in-hand.
Hello, I've tried deploying a fresh OVA of version 4.2 and followed the instructions to get the relevant files from my Windows VC and Windows External PSC and copied them to the right place. However, when I attempt to start the client I get the following:
-bash: /etc/init.d/vsphere-client: No such file or directory
I checked the contents of /etc/init.d/ and there doesn't seem to be a vsphere-client!
What am I missing?
I have a Windows VC with an external Windows PSC
I followed the instructions to create and copy the required files.
ran ls -l /etc/init.d/ but cannot see a vsphere-client symlink
Attempting to run the installer-4.2.0.bsx returns "Please reload the UI and configure the fling again!"
Check the instructions posted below:
from Kaloyan Iliev on Mar 20, 2019
The directories have changed but the documentation not. Very sad.
Also you have to use the trailing /ui for the url. It does not redirect automatically.
Still those issues in 4.2 :-(
I'd really like to only show hosts and clusters in the Hosts and Clusters tree. An option to hide everything else would be appreciated.
Fling v4.1 has this feature, please refer to changelog section for the details.