Exclude Installs from Reconciliation - Two discovery models for sepa versions - One install
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2025 07:35 PM
Hello,
I have a scenario where two discovery models have been created for the same edition due to slight minor version differences:
Two install records have been created for the same machine, but I want to be able to exclude one of them for license reconciliation purposes.
I could try to exclude one of the installs using the software install condition on the software model, but this does not seem to be a very good way to achieve the desired outcome.
Is it a matter of reverting the normalization for one of the discovery models?
Seems like this would be a common occurrence but not sure the best way to resolve this issue.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2025 12:47 AM
Hi @Richo1
I can't recommend your approach. If these are really two different versions, then I would rather work on the software deployment process to ensure that only one version is installed. To me, it looks more like the two installations come from different sources (SCCM, ServiceNow Discovery) – is that possible?
If you are using two sources, then please take a look at the topic “Deduplication”. This ensures that only one record is marked as active. Resolve duplicate software installations in the Software Installation table
Please check your software model metric attributes to check if multiple installs are covered and do not consume additional licenses.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2025 12:52 PM
Hi @dreinhardt we are only using one discovery source so it's not a deduplication issue. We may need to look at the software deployment as you mentioned to ensure clients are on the same version.
Just thought there might be away to resolve the issue within the discovery/software models.
Thanks,
Richo