Horizon View 5.2 Administrator

[IntegraRoger]

I am attempting to setup another Horizon View 5.2 administrator.  In this case, I am using an Active Directory group instead of a specific AD account.

The new administrator I am working with is able to make changes to View, but as soon as he attempts to spin out a new Linked Clone Pool, he gets an error: "Provisioning error occurred on Pool <Pool-Name-Here> because available frree disk space is reserved for linked clones."

When I do the exact same function with the exact same settings, the pool is created.

Question: Other than the (obvious) account setup in the View GUI (he is setup as an Administrator at the Root level), what permissions are required in both AD and in vCenter to allow this new person to administer View fully?  (If you come bback with RTFM, I'm going to find you and hunt you down... I've been doing this for 2 days now and not finding anything in the manuals except for the settings for the service accounts required for View to talk to vCenter, Connection and Security servers (which are all fine thankyouverymuch) )

Exasperated

[lanalyzer · Accepted solution]

Quick question ...

What option did you select when adding the new administrator in the UI?

- Select one or more folders and click Next.

- Select the root folder and click Next.

The new user should not be given any other permissions outside the View Administrator UI as View interacts with vCenter using the vCenter admin and Composer interacts with vCenter with the Composer user. These are the users that require permissions.

Cheers,

JesusM

[IntegraRoger]

I've tried 2 methodologies... selecting the checkbox above all the folders (which includes, / and a number of other defined folders within View) and just selecting Root (/).  In both cases, he got the same error.

I know right??!!  that's what I've been reading as well... I tried using the account we have setup to log into the vCenter server, reset the password just in case and its still not working for him.

I can't use myself as a model as I have Domain Admin rights in AD, and Administrator level rights in vCenter...

[lanalyzer]

As a quick test, do you mind adding the problem admin as a vCenter administrator at the Datacenter or vCenter level in the permissions tab?

[IntegraRoger]

I added him as a Domain Admin AND as an Administrator in vCenter... no change.

As it turns out, we MUST be very close on space... we both had problems creating a single system pool... if we didn't use the Aggressive overcommit method...  Meh...

I couldn't create one and I had been able to earlier...  I'll let you know how it turns out... I'm going to get him to create a single system Agressive overcommitj pool, then delete it, start stripping his priviledges and see where it breaks...

Thanks for the "extra set of eyes"

[IntegraRoger]

as it turns out, the "required" permissions outside of View are nil, nada, nothing... the problem (unbeknownst to me) was the actual lack of space to house desktop images... we have to use the Agressive overprovisioning setting (which is what every other linked clone is using) in the datastore or it runs out of room...

Thank you...

Roger

[lanalyzer]

I guess this statement threw me off path ..

"When I do the exact same function with the exact same settings, the pool is created."

Running out space would definitely explain the issue if "both" get the message

Cheers!

JesusM