VMware Horizon Community
cbbowyer
Contributor
Contributor

VDM Provisioning Error - Permission to perform this operation was denied

I've got VDM configured in a lab environment.

I was able to create an individual desktop in VDM and point it to an existing XP VM we had. Now I'm trying to create a persistent pool of desktops. When I go to start provisioning, I get the Permission to perform this operation was denied. The desktops are never provisioned. I never see VC doing anything. The events in VDM don't show me anything other than "Permission was denied".

I followed the VDM manual regarding permissions. I am able to log into VC with the same user and deploy a VM from the same template no problem. I've also tried logging into VDM with domain admin, which has full Administrator Role assigned in VC.

What am I missing here? Any suggestions would be appriciated.

Reply
0 Kudos
5 Replies
bradley4681
Expert
Expert

What does the virtual center logs say right around the time you experience this?

Cheers,

Bradley Sessions

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

Cheers! If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
Reply
0 Kudos
cbbowyer
Contributor
Contributor

There's really no indication that anything has taken place in Virtual Center. I guess it's trying to but gets blocked before that point because of this permission problem.

Reply
0 Kudos
TomHowarth
Leadership
Leadership

Moved to the more appropiate VDM forum

Tom Howarth

VMware Communities User Moderator

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410
Reply
0 Kudos
markbenson
VMware Employee
VMware Employee

Hi,

Almost certainly VC permissions. Check out the section in

Mark

Reply
0 Kudos
mpryor
Commander
Commander

I agree with Mark, it's very likely to be a genuine VC permissions issue. The account that you log into the admin UI with does not affect the account VDM uses for VC access, it will use the one you saved in the VC settings. If you're able to manually provision a VM from the template with the used account then it's most likely the account doesn't have permissions to create/delete folders, as a folder is created based on the pool name before the provisioning begins, this is mentioned in the admin guide linked to above.