Duplicate software models

[Shivani]

Hello All,

I have seen my production instance, it has duplicate software models with same publisher, product, version(anything),edition(anything). There is no DMAP attached to it. They were created by the system property whenever the reconciliation run. It check whether there is already a discovery model available in the system with same publisher, product, version, edition and then it attached update that software model by attaching the DMAP.- but there is no discovery model available for those records. hence every time, when reconciliation runs, system creates a new software model. It is creating confusion. how to avoid the creation of software models automatically. Please help!

Thanks,

Shivani

[MikeW_SAMBeast]

You need to switch off the property that auto-creates software models.

[Shivani]

Hello Mike,

Those are OOB system properties. ServiceNow does not recommend doing any modification on OOB properties.

 Also, if i disabled those properties it will impact other records.

When reconciliation runs, the system searches if any software model exists for the software installation. The search for an existing software model is based on attributes such as version, edition, language, platform, and install condition. If all conditions for the attributes in an existing software model match, then a software model is not created hence avoiding the creation of duplicate software models.

If the system properties are enabled and a discovery model match exists, even if the match is generic, a software model will not be created. If the system properties are not enabled, the software model is just matched to a discovery model; no software models are created.

Thanks,

Shivani

[MikeW_SAMBeast]

Hi Shavani,

There are a couple of comments here that aren't strictly true. 

OOTB, the "Automatically create software models" system property is defaulted to false, so someone has actually changed this property in your instance because it seems like software models are getting auto-created during reconciliation.

The main reason why I never change this property to 'true' is because if there is a software model already exists with the same publisher, product, version and edition AND an install condition, then a separate/duplicate software model will be created. I had this issue with a customer and it caused us no end of problems when reconciling products such as SQL Server and Windows Server where there is an obvious need for install conditions. From  my own perspective, I only want software model records for licenses that I'm actively managing so I don't want thousands of sw models creating for products that I'm not interested in.

[shivani42]

Hello Mike,

Thanks for explanation.

But if I disabled the property and we don't have an existing software model to a normalized discovery model. then system will not create a software model automatically. SAM team will have to create it manually by using the DMAP available in list.

For e.g.- if the discovery installed a Microsoft Visual 7.3 model, and we don't have normalized discovery model, then system will create a new discovery model named as Microsoft visual 7.3. When normalization run and it normalized the discovery model as Microsoft Visual 7(as per content library). Would the software model also have created automatically or not.

Any suggestions on this??

Thanks,

Shivani