Hi,
this is an issue i am facing and is hurting me badly!
i created Resource pools on my esxi node with viclient
then i created a user and added Administrator permission to that user for that resource pool!
but here is the issue :
when the user clicks on New Virtual Machine button in viclient , it will go not responding and viclient will crash!
i upgraded my ESXi to ESXi 4 Update 2 but no luck!
i attack the core file that viclient file creates!
i will be very thankful;l if any body can help me!
I guess you will to have to sort out a few things:
Are you using just one esxi server or do you have an environment under vCenter administration
Are you able to create a new vm outside the resource pool
Are you able to create a new vm with another user account
Have you used vSphere Client on another workstation?
Paul Grevink
If you find this information useful, please award points for "correct" or "helpful".
Hello Paul,
thanks you for your answer ,
here is my answeres to your questions :
Are you using just one esxi server or do you have an environment under vCenter administration
Just one ESXi server
Are you able to create a new vm outside the resource pool
Yes with root user
Are you able to create a new vm with another user account
Nope
Have you used vSphere Client on another workstation?
Yes and same issues comes up
I have tried to reproduce on a ESXi 3.5 (build 283373) environment. Everything works fine
Later this day, I can try on a ESXi 4 environment
Paul Grevink
If you find this information useful, please award points for "correct" or "helpful".
any body else knows any thing?
On a ESXi 4.1.0 build 260247, I can reproduce your problem, my vSphere Client also crashed.
Gonna try e few things.
Paul Grevink
If you find this information useful, please award points for "correct" or "helpful".
The default roles without vCenter are pretty limited: No Access, Read-Only and Administrator. But you can add Custom roles with less rights than Administrator role.
It seems that Administrator roles only works on the top level.
With one server I would not define to many resource pools.
A possible workaround:
- create VMs with a account with Administrator role assigned
- place VMs in the Resource Pool
- Create a custom roles with rights like power on/off a VM, edit settings etc.
- When VMs are fighting over resources, another approach is Resource Management using the Shares mechanism.
Good Luck
Paul Grevink
If you find this information useful, please award points for "correct" or "helpful".
Hi,
dude i want another account creates VM under their own resource poool!
because of some ecurity!
thanks!
Hi,
Thanks to this thread http://communities.vmware.com/thread/286918;jsessionid=FDD2B2F3D588F00F39DD86745017F672?tstart=0, I have found a solution.
Here are the steps on a standalone ESXi server 4.1.0. build 260247. Perform all steps as user root with Full Administrator rights.
1. On the host level, tab Local Users & Groups
Add a new user, UID 501, Group membership: users
2. Go to Roles, clone the Read-only role and give it a new name like: Custom read-only
3. Do a Edit Role on the new Custom read-only role
Tick Datastore, Alocate space
Tick Virtual machine, Inventory, Create new
Tick virtual machine, Configuration, Add or remove device
Tick virtual machine, Configuration, Add new disk
And save the changes
4. On the host level, tab permissions
Add the newly created user with new Custom read-only role
5. On the host level, create 2 resource pools: RP1 and RP2
6. On the RP1 level, tab Permissions
Add the newly created user with Administrator role
7. It is now time to test.
8. Log on with the new user, you can do everything within RP1 and have no rights on the host level or RP2
9. Repeat steps for the user of the second resource pool.
Good luck.
Paul Grevink
If you find this information useful, please award points for "correct" or "helpful".