What marks or sets software installations (cmdb_sam_sw_install) 'active_install' attribute to false?

Churchie
Tera Guru

‎03-31-2022 05:23 AM

I am trying to understand what process marks software installations in the software installations table as not active, where the attribute 'active_install' is set to false. What job/business rule handles this, does anyone know?

0 Helpfuls
  • 2,222 Views
9 REPLIES 9

Ken Neikirk2
Giga Contributor

‎03-31-2022 07:29 AM

There is a scheduled job: SAM - Adjust installs for excluded CIs that deactivates the Software Install record if the CI is set to be excluded.  This would need to be configured.  You would first check the SAM Properties (Software Asset > Administration Properties> Enter the name of the true/false field added to cmdb_ci_hardware table to exclude software installed on selected devices from Software Asset Management).  If there is a field entered in that property, then you would check the CI table for the field and see if any CIs are set to be excluded.  If so, then the scheduled job would update the associated software install records so that Active Install is set to false.  The job runs once a week on Mondays by default.

 

Another scheduled job that updates the Active Install field is SAM - Deduplicate Install Table.  This job runs daily by default.

0 Helpfuls

David Waldner
Kilo Guru
In response to Ken Neikirk2

‎03-31-2022 08:01 AM

Is there a job which checks the CI Status e.g "retired" and set the corresponding Software to inactive ?

0 Helpfuls

Churchie
Tera Guru
In response to David Waldner

‎03-31-2022 08:28 AM

exactly. i think excluding software installs with the exclude from sam property is something different.
what i am trying to understand is why i have active software installs on servers that are retired and haven't been discovered or updated in months. there has to be a job that addresses retired computers and changes the active_install field to false.

0 Helpfuls

Joe Ryder
Tera Expert

‎03-31-2022 08:35 AM

Hi. The most common scenario where Active Install = False is during installation de-duplication. There is not an automatic job that invalidates stale installs. We actually had installs sitting in our ServiceNow instance since 2020 that were not being deleted because of the existing issue with SCCM not deleting installs without the Microsoft Graph service connected to SN. You can also manually set this field to false.

If you see other installs active but some inactive, likely they were de-duplicated at some point.