Manually Matching software Discovery Models

[Michael Morgado]

Hi All,

Recently to work on some of the Health Check issues I have updated existing software discovery models from being automatically matched to a Software Model to one of my choosing.  In doing so I am see mixed results where the Software Model result field on the actual installed software is not always mapping to the new software model.  I have seen three unique cases:

1. All the installs in the discovery model point to the new software model as identified in the discovery model

2. A subset of the installs that are bundled in the discovery model map to the manually selected software model, the remainder remain with the original model and seem to remain to use the old automated matching

3. All the installs remain with the old software model even though the discovery model points to the new software model

I have been working with a support case but keep getting bounced around and going in circles pointing to the same generic documentation that does not explain this situation.

If anyone has seen this before and resolved it any insight is appreciated.

[dreinhardt]

Hi @Michael Morgado,

the last answer I got from support about the discovery model field "Software Model" was that the field is deprecated and not used during any reconciliation process action. Based on your findings, it seems to be confirmed, right? I didn't use/trust this field anymore.

In your case, you have to check all software models and their notes regarding “Installs requiring actions” and “Unlicensed Install”. These details already give a very good indication of why an installation was assigned to the respective software model.

Best, Dennis

[Michael Morgado]

Thanks for the insight i will have to investigate further but just seems odd that the items are not flipping over.