Software Models with deactivated discovery maps

[Jain3]

Hi All,

Why discovery maps related to software models get deactivated and what are the key things to keep in mind when we are associating Software Model with a new discovery map/ customized DMAP?

[Bill Girard1]

For everyone who has located the Software models with de-activated discovery maps report in the Software Asset Workspace and come across the couple questions where folks like Neha have asked but not received many responses regarding this, perhaps these details might shed some light.

After trying to wrap my head around this one I was able to work this part out.

If someone makes a change to the product detail in a Software model, perhaps updating/modifying the product name to match how it is now being discovered in your environment, this will trigger the deactivation of the existing Discovery map because it is now looking for detail that doesn't match with the Software Model.

You will need to update the Discovery map with the details you have confirmed your discovery tools are populating in the tables, so that your Software model and Discovery Map match and they will now work together correctly and come off that report.

[Jain3]

Thank you, Bill.

[dreinhardt · Accepted solution]

Hi @Jain3, Hi @Bill Girard1,

ServiceNow SAMP provides a OOTB report to show software models linked to disabled DMAPS. The content team is responsible to disable DMAPs in case of any update/change for this specific product (Version, Edition, ...)

The report is named: Software models with de-activated discovery maps

The report definition is: "This report gives you a list of all software models which have a discovery map that is de-activated by the content service. You can review these software models and map the active (more accurate) discovery map."

Best, Dennis

[Jain3]

Thank you!