Entitlements are "bound" (for lack of a better word) to a Business Group. So if your users are added to an AD group, that is a member of only one Business Group then you will get the exact behaviour that you are describing, using a single Entitlement per Business Group.
Hi, thanks for your reply.
Yes, this will entitle the users but will it fix the issue of having to make a separate blueprint for each reservation?
What I'd like to do is:
- User who is a member of the AD group "POC1 Users" gets entitled to use the W2K12 blueprint which gets provisioned on the "POC1 Reservation"
- User who is a member of the AD group "POC2 Users" gets entitled to use the same W2K12 blueprint which gets provisioned on the "POC2 Reservation"
- do the above without having a drop down to choose the reservation at request time
If I created a separate reservation and reservation policy for each placement option, I could still have a single blueprint if I could somehow dynamically change the reservation policy binding of the blueprint during the request time (based on business group).
Does this sound like a workable approach? Does anyone know how to do this?
Right, now I understand your question.
Blueprints aren't bound to a Reservation. You can constrain them to a given Reservation Policy if you so desire, but the default behaviour is that they can provision to any Reservation that would have access to the underlying template.