Hi All,
Not sure if this is a feature or a bug but we are currently testing out vCenter 8 and have discovered that when a user accesses the console using the Web Console option it throws up an error if they have been given only permissions to the VM folder only (rather than at the highest VC level and propagate the settings down.
The error received is
"An error occurred while retrieving the web console URL."
If I add Read-Only to the host that the VM is sitting on it starts working on.
Anyone else had this issue? It was working OK prior to the upgrade.
Hello,
I've the same error.
Could you explain better what you've done to solve?
Thanks
I have the same issue.
If I assign Virtual Machine console user role on a VM folder level - Web Console is not working.
If I additionally assign Read-Only role to the hosts - Web Console is working but user sees more than needed.
As ISTAustria explained, adding the read-only role for the user on the host where the server currently resides, they are then able to get web console access (if you have set Console interaction privilege at a VM folder level). But as mentioned they then can see more than they should.
Hope that helps. I'm hoping that VMware will fix this in the next release or have a better workaround
Any prevision for a fix for this issue??
I have this problem in my Work place and i dont want that some users see more than they need
I have the same issue. By assigning permission folder level will trigger this bug. It can still access by using VRC, but it just need extra step. Hope fixing soon.
version: 8.0.0.10000
Also I check the 8.0a release note. Not being mentioned though.
But would be better to install already 8.0a to confirm that problem exists or is solved.
Theres already been launched an update to VCenter but has not yet fixed this problem
Does anyone know if this issue has been fixed? I'm having the same issue.
Hello there
I had been having the same issue with Center 8.0.
However, there is a workaround for now that I got around with.
The user should now be able to access the web console of the VMS on the resource pool/folder.
Note: There may be other workarounds, that may follow the principle of least privilege. Please test this workaround before deploying it to all the users/groups.
