SAM

Asmita7
Tera Expert

Hi friends,

When it comes to alm_license table, the software asset data is by default not synchronized with CMDB class. Any specific reason for this ????

Is it a good approach to synch SAM table to Software package table on CMDB side ???

Please guide.

 

Thank you

1 REPLY 1

Fabian Kunzke
Kilo Sage
Kilo Sage

Hey,

In short: you should not synch it.

 

These tables have two different uses and reasons. The alm_license table is your asset of licenses. It is the volume you have bought. These records should match whatever licenses your company has ordered for software (e.g. the license volume you have for using office products).


The software package table contains software installed on a machine. It is the "what you use" table. This contains which office products are installed where.


The main goal with using SAM (Software Asset Management) is to find gaps between what you have licensed vs. what you have installed somewhere. If there is a gap, you will need to buy more licenses or uninstall those software packages.

 

ServiceNow SAM Pro is using different mechanics to link the licenses (alm_license) with the installed software (software packages). These records are called entitlements. Depending on the type of license, a different kind of entitlement is needed (e.g. Office 365 is based on the user, not the device; Adobe is based on the device, not the user).

 

Your proposed synch goes against this functionality. You don't want to automatically generate a license asset for a software that is installed somewhere, because:

1) You may not need it (open source software)

2) You may not have licensed it

3) You may have underlicensed it


If this helps/answers your question, please mark it as helpful/answer. This enables other to find answers more quickly.

 

Regards

Fabian