Instant Clone pool fails to provision: "Initial publish failed: Fault type is VC_FAULT_FATAL..."

[HPU-ADM]

Hi, i'm trying to get my first instant pool created.

Horizon View connection server 7.9

Windows 10 1903

view agent 7.9

tools 10.3.10

Vcenter/esxi 6.7U2

After creating the pool and have it provision, it fails with the error:

Error During Provisioning: Initial publish failed: Fault type is VC_FAULT_FATAL - javax.xml.ws.soap.SOAPFaultException fault was thrown by the VC server: https://x.x.x.x:443/sdk. Error: Permission to perform this operation was denied.

I performed this for the instant clone ad account in AD : Create a User Account for Instant-Clone Operations Although i could not find "reset password" permission.

and then this for the instant clone ad account in virtual center: View Composer and Instant Clone Privileges Required for the vCenter Server User

and then this for the view manager ad account in virtual center : Privileges Required for the vCenter Server User

Any suggestions on what I skipped or missed?

[colwilliamsnz]

I'm having the same issue on the same version of Horizon View. Target OS is Win10 1903.

Did you ever find a solution to this one?

[MrCheesecake · Accepted solution]

Is the domain user used for Instant Clones the same user you use to authenticate to your vCenter server?  If so, to rule out any permissions issues, try adding that (or both users if different) to the Domain Admins group.  If that works, you can either leave the permissions in place or work backwards to verify all the permissions/rights needed for the service account(s).

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

[colwilliamsnz]

I have two separate accounts for vCenter and Instant clones. Adding to "Domain Admins" didn't work. I elevated both in vCenter to the "Administrator" role and it now works as expected. I'll double check the permissions I created for each of the roles and report back.

Thanks for responding.

[HPU-ADM]

Turns out for me it was permissions. I had an account for vcenter access and an account for instant clone creation.  Turns out I had them flip flopped