Report on Software Product End of Life or End of Service

Neil15 · ‎07-21-2020

Currently we have a report for "Software Model Lifecycle Report" which reports the EOL for the Softwares which have defined software model.

Is there any way to list out all products from ServiceNow software content library and show the EOL/EOS for these. Defining Software model for each of the discovered installs is a tedious job which is our next phase.

Hardik Benani · ‎01-11-2021

This is already answered in seperate post but reporting here to ensure it helps others.

So below is the solution that should work.

Create a base view with four tables as below. As the data resides in three different tables you will need to add them to the view and then add relevant conditions.

1. cmdb_sam_sw_discovery_model

2. cmdb_sam_sw_install (csam_discovery_model=samlm_sys_id)

3. samp_sw_entitlement_definition (dmap_sw_product=samlm_norm_product && dmap_version=samlm_norm_version)

4. samp_lifecycle_definition (saml_entitlement_definition=dmap_sys_id)

This should now give you a single report where you can report on softwares installed on a computer and EOL dates based on DMAP and Lifecycle.

Note: We can only match base on Product and Version. If you need the exact match you would need to write a script to put them all into a seperate table and this requires a bit of work. It would be good to create an idea on idea portal soo ServiceNow can add this to the required functionality.

View solution in original post

Scott Halverso1 · ‎08-24-2021

This is now out of box in Quebec and further enhanced in Rome. Scheduled jobs populate a table called sam_sw_product_lifecycle_report

Jeanna1 · ‎02-04-2022

I am glad this was added to the dashboard. I did notice that the software model field in the OOB report is not always populated.

Derek L · ‎11-16-2021

One other addition after using this solution on a project was discovered. Client had shown example of Microsoft Windows 10 Enterprise was bringing in lifecycle information for other Windows 10 editions. So we added an additional constraint around edition. So for the samp_sw_entitlement_definition view table where clause should be dmap_sw_product=samlm_norm_product && dmap_version=samlm_norm_version && dmap_edition=samlm_norm_edition. After adding that additional constraint on the join table where clause, the data looked much better!

MercBuilding · ‎04-21-2022

But all the installations will not be normalized at edition level and some software's will not have editions also in that case this where clause won't work to match editions on both the tables

JenniferS777 · ‎12-17-2024

I am going out on a limb here to ask if anyone knows a solution to support looking at a CI to check installed software related list and add EOL, EOS data as discovered, installed and normalized? As we work in the CSDM, it's important to identify Critical Application Services and related Infrastructure to quickly identify if any is at EOL or EOS etc. I do feel like this should be an out of the box configuration without a custom DB view but may be missing something.