- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2023 08:01 AM
My question is that in looking at my SW Install table, I have 50 install records of a particular software each related to a unique CI record for 'Installed On', yet 7 are Active Install = TRUE and 43 are Active Install = FALSE. How can it be that I have 43 unique SW Install records with 43 unique CI in Installed on but Active Intall = FALSE. No duplicate SW Install records. Checked installs against CCM and they appear to be legitimate.
I understand the function of 'Active Install' field to help with deduplication and reconciliation in cases where multiple discovery sources create SW Install records related to the same CI.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-13-2024 08:34 AM
Possibly, I have not done a deep dive, but I suspect what was happening in my case was freshly created SW Install records default to Active Install = FALSE (which could lead to singular installs showing Active Install = FALSE)
There is a scheduled job SAM - Deduplicate Install Table which runs weekly that works to update the Active Install flag by identifying multiple matching installs and setting only one to TRUE.
Today I ran a search and found a computer that had SW Installs that appeared to generally align with my OP, those install records were created yesterday and today for the target computer CI. I then manually executed SAM - Deduplicate Install Table and waited. After some time the SW Install records updated to Active Install = TRUE (where there were only singular installs)
So I suspect, at least for the majority case, that what appear to be incorrect Active Install = FALSE are a result of a timing issue where install records are created nightly (which is appropriate) but the SAM - Deduplicate Install Table runs weekly.
Realistically this is likely not a real issue as long as SAM - Deduplicate Install Table runs before weekly reconciliation type jobs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-13-2024 06:30 AM
Hi @Brigham
Did you get the answer for this query. Please let me know why this is happening as we are facing the same issue.
Regards,
Praneeth S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-13-2024 08:34 AM
Possibly, I have not done a deep dive, but I suspect what was happening in my case was freshly created SW Install records default to Active Install = FALSE (which could lead to singular installs showing Active Install = FALSE)
There is a scheduled job SAM - Deduplicate Install Table which runs weekly that works to update the Active Install flag by identifying multiple matching installs and setting only one to TRUE.
Today I ran a search and found a computer that had SW Installs that appeared to generally align with my OP, those install records were created yesterday and today for the target computer CI. I then manually executed SAM - Deduplicate Install Table and waited. After some time the SW Install records updated to Active Install = TRUE (where there were only singular installs)
So I suspect, at least for the majority case, that what appear to be incorrect Active Install = FALSE are a result of a timing issue where install records are created nightly (which is appropriate) but the SAM - Deduplicate Install Table runs weekly.
Realistically this is likely not a real issue as long as SAM - Deduplicate Install Table runs before weekly reconciliation type jobs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-13-2024 09:49 AM
This information will help. Thank you for that.