Instant Clone Provisioning Issue Horizon 7.12

[sjpage]

Using Horizon 7.12, Windows 10 as the desktop and getting the following error while provisioning. Same happens on 2 different pools with 2 different VMs.

Error during Provisioning Initial publish failed: Fault type is AD_FAULT_FATAL - com.vmware.daas.cloneprep.ldap.LdapException: createComputerAccount: Fail to create computer account it1542402259, entryDn: CN=it1542402259,CN=Computers,DC=local,DC=net, description: Internal Template account. Can be deleted if vm cp-template-827759b6-daca-41df-93c2-bc431c62b5d1 does not exist in the VC. - constraint violation: unable to create entry, resultCode=19 (constraint violation), errorMessage=0000207C: AtrErr: DSID-031530E5, #1:0: 0000207C: DSID-031530E5, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 90001 (name)

[sjesse · Accepted solution]

The error message is complaining it can't create the computer account, can you logon as the account you created for the instant clone domain account and make one?

https://docs.vmware.com/en/VMware-Horizon-7/7.0/com.vmware.horizon-view.installation.doc/GUID-E91881...

[sjpage]

Have cloned the VM and joined the clone and removed the clone from AD. Have confirmed with the customer that the AD account they provided has the permission as per Horizon docs for instant clones

[Shreyskar]

Hi sjpage

(constraint violation) denotes the instant clone domain administrator (added in horizon view admin UI) does not have the privilege to create and delete computer accounts in Active Directory. Please verify the account permission again.

[sjpage]

Had the customer create a new OU and delegate permissions as per Horizon documentation. Works as expected.

[sjpage]

Had the customer create a new OU and delegate permissions as per Horizon documentation. Works as expected.

[sjpage]

Thanks for both responses, the customer had confirmed several times that the permissions had been applied. But after creating a new OU and delegating the permissions as per Horizon documentation; it was evident that the permissions hadn’t been applied as first informed in the original OU. This is the issue when you have no visibility of the customers AD. Thanks again.