Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Software Asset Management Reconciliation

Marlon12
Tera Contributor

Hi Everyone, 

Does anyone know how can we make a product non-compliant?

 

Scenario:

 

I have a software entitlement for a product with 1 purchased rights and 1 allocated device

 I used the custom license metric that returns 1 for the rightsfordevice.

 

When running a reconciliation, the product is compliant, 

Is there a way on how I make the result compliant? ex. should i add allocated device? should I return 2 on my Custom license metric?

7 REPLIES 7

dreinhardt
Kilo Patron
Kilo Patron

Hi @Marlon12, could you please share more details about the reason you need this products as "non-compliant"?

Best, Dennis

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

I have created a custom license metric and used it to an entitlement. The calculation is no. of installations for a product, so basically, I need to count how many devices where this product was installed. I want to verify how this clm is working or how can I prove that my calculation is correct, I tried to force add in Device allocation so that it will be greater than the purchased rights. Is my method or steps are correct?

Hi @MarlonD20

thanks for the clarification. An allocation is a specific decision to tie consumption to a particular device or user, even if there is no consumption (yet) through a software installation or subscription.

 

In short, allocations have no influence on your custom metric and its calculation, as they are always preferred in the reconcile and automatically generate a consumption. Custom metrics are based on the conditions you set in the script - in your example, it should be existing installations and this is based on the CMDB/CI data in the cmdb_sam_sw_install table.

 

My personal opinion - if custom metrics can be avoided and can be covered by a common or publisher metric - you should rather fall back on the OOTB possibilities - in your case it sounds almost more like a "Common / Per Device" metric.

 

Best, Dennis

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

Thanks @dreinhardt ,

 

You suggested an OOTB license metric, can you give me a clarity on how does the calculation affects the reconciliation? I want to verify if "Common / Per Device" metric had the same calculation like in our requirement since you said it is almost more like it.