Managing Same Applications for Production and Non Production Entitlements

[shspann]

How do you handle entitlements which cover Production versus Non-Production, the entitlements cost significantly different but cover the same applications? Leveraging a manual allocations / exemption is too cumbersome as the weekly inventory and volume would not be manageable.

If you create two license records (Production and Non-production), leverage the Use rights & rules < Exemptions (Exemption by device role) function, would you not have an issue if the Non-Production endpoint (server) is Exempted in the Nonproduction License Record, would the system automatically consume under the Production?  The same applications are assigned to both license - the entitlement Use Rights vary due the endpoint environment (Prod vs. Non-Prod)

Do you have use cases for delineating between Production and Nonproduction entitlements?

Does FNMS manage it automatically?

[spierce]

Hi,

There is no standard automatic way for a device to consume a license based on its role (Prod, Non-prod etc) at the moment.  The Exemption by Role Use Right does not do the trick in this scenario because it does not prevent consumption of the license, but ensures that the consumption is 0.  In this way the exempted device will not consume any other license.

So allocation is really the most robust approach and the manual effort can be reduced through the use of the License Compliance/Apply Allocations & Exemptions view; Here you can define a list of all installations of the product in question, filter by role and allocate to the appropriate license all in a few clicks.  This could be done weekly/monthly and you can further reduce time by saving the pre-filtered view as a management view (click on Save View As in the top right).  This pre-filtered list is then available as a management view and you can run, select all and allocate to the chosen license in a minute or two.

Of course, this process depends on the device role in FNMS being populated, through an integration with your CMDB for example.

Automation of consumption through standard configuration is only possible in the following circumstances:

• Where production and non-production installations have different evidence and can be recognized as different applications
• Where Production and Non-Production devices below to different Enterprise Groups (Locations, Cost Centers Corporate Units) and license restriction can be used