Multiple versions of Software - SAMP

[Frank1975]

Hi all, 

we are on our way to implement the Software Asset Management Professional plugin in our Instance.

Right now i am facing an issue, that multiple versions are showing up on the Software Installs of a System. 
i E . for Google Chrome: 

What is a the best practice to get rid of these "old versions" and just have main lasted version being displayed ?
Also with the SAMP , the Normalization is coming on connected to the Content Library at Service Now. (auto normalized) 
I have created Software Models for Visio (2013, 2016, Prof and Standard) , (Discovery Model auto normalized from SN)
When i run a reconciliation, the produc results are showing each language as a seperate install and even worse, also each different version as a seperate install (see below)

I did the SAMP Training 2 weeks ago, but this looks all different if you have a "clean CMDB"
We are running on London Patch 2 and using SCCM for Windows Systems as being the source for Software installs and Discovery for any SSH devices. Right now i got 10million+ records in the cmdb_sam_sw_install table. 
seeking for help.

Thanks in advance

Frank

[SnowReece]

Hi Daniel,

You're correct, I'm using the SAM Plugin.

Many thanks,

Reece

[Daniel Slocum]

Reece,

For unlicensed software, like Google Chrome, what you are experiencing isn't an issue and you can ignore it.  I believe the source of the issue is older Software Installation records are not being removed when an updated version of software is installed.  This can happen when an automatic updater applies an update patch vs. doing a completely new installation.  You may want to undergo an effort like Frank is doing where you remove all of the software installation records and allow SCCM and SN Discovery to repopulate the table. 

Daniel

[markbu]

Hi Daniel I'm having the same issue but with all types of software which was all discovered using SCCM, you're right in that I believe this happens with software like office 365 applications are updated, as subscription updates happen frequently you can see how this causes a massive issue with duplicates and unlicensed installs.

[Salom_ Fonseca1]

Hi,

I believe in cases like O365 it is not an issue. It is licensed by user, not by installation, so it can be ignored.