I'm trying to create a role that will allow users to clone VM's based on existing templates but for the life of me I cannot get customization to work. What permission do I need to enable so that the user can select the "Customize using existing customization specification" option?
jd
Have you tried Virtual machine--Provisioning
There are various privileges inside Provisioning. I would think you would need at the very least "deploy template". You may also need "customize"
From waht I can tell, I need the Provisioning --> Use stored customization specifications but I don't see this permission listed under the provisioning option.
Everything seems to be working in that I can clone templates and existing VM's but I cannot use the customization wizzard.
JDLangdon wrote:
From waht I can tell, I need the Provisioning --> Use stored customization specifications but I don't see this permission listed under the provisioning option.
I don't see this privilege in either vCenter4 or vCenter5 roles. Where did you find documentation stating the above?
Everything seems to be working in that I can clone templates and existing VM's but I cannot use the customization wizzard
Meaning by creating a custom role, or by using any role? Can you use the customization specification if you are logged in with with a user that is part of the Administrator role?
I'm seeing that permission mentioned in the vSphere datacenter administration guide on page 261 which I downloaded from the VMware documentation website.
I'm attepmting to create a custom role. If I use the pre-defined administrator role I am able to select a customization specification.
it's got to be the documentation is wrong, you think? I've gone all the way back to a vCenter 2.5 instance and that privilege is still not there. I'll keep poking around to see if I can find anything.
I'm starting to think that the documentation is wrong.
This isn't a big deal, I mean my support staff can function without this permission but I just seems strange that this is the only thing not working.
I believe that cutomization specifications are an object whose parent is the root of virtual center. So your users will need that privilege* assigned at the root, using some role with No Propagate.
*Edit: "that privilege" = "Read Customization Specifications" under VM -> Provisioning.