Entitlements for Production and Non-Production Installs (Not using differing Software Models)

Stephen42 · 3 weeks ago

Hi all

I have read a few posts and solutions re separating Production from Non-Production software installations, however, they all suggest different Software Models and creating appropriate conditions for each. So you might end up with perhaps four models, one for each Development, Test, Pre-Production & Production.

In a case I am investigating, this is not an option as the Software Model is the Blueprint for the Entire Enterprise. Entitlements (Licences) are bought at a more regional or divisional level. Modifying or creating additional Software Models would impact everyone, when perhaps the detail is specific to one region/division and not ALL entitlements across the Enterprise

I have tried with Entitlement Consumption Rules and Allocations, but none of these types of configurations have yielded the correct results, as it appears at the Entitlement Level it's not possible to utilise an environment variable to yield the correct results, and thus compliance

Does anyone know how to accomplish something like this without 'duplicating' the Software Model ? I'm sure I'm not the first to experience this

Thanks in advance

dreinhardt · 3 weeks ago

Hi @Stephen42,

we‘ve accepted the situation and invest more into training, governance etc. to ensure a stable operating model.

As the software model is the leading object for the reconciliation, I don‘t see any other option for this at the moment.

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

Stephen42 · 3 weeks ago

Thanks for the reply Dennis. I was starting to think about how Regionally, with different SAM_ADMIN teams something like this could be coordinated from a Governance perspective. I'll keep trying to see what I can come up with given the Installation data created by Flexera, and hopefully might stumble on something.

Thanks

dreinhardt · 3 weeks ago

Hi @Stephen42,

looking forward to your update about this. If possible, you should think about a restriction for regional models tight to the local sam_admin teams. Maybe a custom field for responsibility or any other unique attribute + BR could help to avoid changes made by other teams. Same I would recommend for global managed models, to avoid local teams can change critical attributes of these models.

as long your foundation data for CI and users is in a good shape, you should be able to restrict based on this data.

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.