How Active install field set on Software Installation table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2024 05:23 AM
Hello,
I need to know that how the active install field set on the installation table. We have set up service graph connector when we run the import and software data is getting fetch from SCCM. Some records have active false and some are active true. What does that mean? Is these stating the install status on the specific machine. If it is active install means, the software is running on specific machine. when it is active false that means it is now uninstalled from that specific machine.
I read that this field is getting updated by a schedule job SAM - Adjust installs for excluded CIs but i checked in my instance we did not set up the property com.snc.samp.exclude_device_flag but still we have records with active false in software installation table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2024 01:32 PM
I have questions about this field as well. We currently have an integration with SCCM using the SCCM Service Graph, and we're running Discovery. We have a total of ~2.7 million software installation records. 75% of the software installations come from the SCCM Service Graph connector. Of the 2.7m installation records, 233k are listed as active install = false. I cannot find any commonality or explanation for why these records are active false. Looking at one software specifically, there are 27k records and ALL of them are active = false.
I understand that if there are multiple installations from difference sources, only one will be active = true. But that doesn't explain the data that I'm seeing.
Is there any other information available regarding this field and how we can ensure that the data is accurate?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2024 03:05 PM
Hi @Patrick Quinlan,
I would recommend the following steps to test before raising a support case. We had a similar issue with the attributes and a full reset solved the problem for us.
1. Set Software Asset Management Properties "Enable scheduled jobs when using third party Datasource Integration Framework" to TRUE (you're using Discovery and SCCM)
2. Reset the attributes "Active" to TRUE and "Deduplicated" to False in the [cmdb_sam_sw_install] table.
3. Execute the SAM job "SAM - Deduplicate Install Table"
4. Compare the results and raise a support case if necessary
ChatGTP snipped
// Initialize a GlideRecord for the cmdb_sam_sw_install table
var gr = new GlideRecord('cmdb_sam_sw_install');
// Add a query if you want to limit the scope of updates (optional)
// For example: gr.addQuery('active', false);
gr.query();
if (gr.hasNext()) {
// Set the fields to be updated
gr.initialize(); // Prepare for a bulk update
gr.setValue('active', true);
gr.setValue('deduplicated', false);
// Perform the bulk update
gr.updateMultiple();
gs.print('Bulk update completed: Set "active" to TRUE and "deduplicated" to FALSE for all records.');
} else {
gs.print('No records found to update.');
}
Best, Dennis