We're looking at propping up a Composer test instance in our environment. We have a standalone Composer server, with SQL express on it today for testing, everything seems to be good, but no matter what when I create this initial test pool, immediately when it starts provisioning I get the error in View:
View Composer Fault: Unexpected VC fault from View Composer (Unknown) - Unknown - <NoPermissionFault xmlns="urn:internalvim25" xsi:type="NoPermission" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><object type="VirtualMachine" serverGuid="8A4690DB-3E74-4902-8A5F-08C86FF1138D">vm-65769</object><privilegeId>VirtualMachine.Provisioning.Clone</privilegeId></NoPermissionFault>
I have Googled this type of error and found results. All have pointed to a fault in the permissions of my Composer service account I'm using. I have double and triple checked the Role in VCenter I created for the Composer service account, and it has everything checked off that VMware's documentation states. The Composer service account has local admin rights to the VCenter and Composer server. Obviously I'm missing something but it seems like the clues don't add up (or I'm just overlooking something).
We have a View service account as well for our View provisioning today obviously. Is THAT the account that's the missing "VirtualMachine.Provisioning.Clone" privilege the error is referring to? The Composer service account role definitely has that. I didn't see anything in the documentation that stated an already existing/new View service account needed that right. I could try adding it and testing.
Any help is greatly appreciated. Thanks in advance.