Cristian Satnic

Software Compliance, Tags and Versions (revisited)

Discussion created by Cristian Satnic on Oct 3, 2017
Latest reply on Oct 9, 2017 by Cristian Satnic

Samanage tracks installed software using a combination of the application's name and its exact version. This particular combination then needs to be tagged by the user and then software licenses and contracts are created based on tags.

 

The problem that comes up is that when a particular piece of software is updated its version changes and to Samanage that looks like a brand new software installation. The previous version's link to a particular tag is broken and the software application needs to be re-tagged. This causes a problem if you try to keep up with software compliance because at any point tags can fall out of sync due to new versions being detected which must be manually re-tagged.

 

This issue is well described in this discussion from a year ago:

 

Software Compliance, Tags and Versions 

 

I have 2 questions:

 

1 - For the community: is anybody really using Samanage to track installed licenses and keep track of license compliance? How do you deal with this re-tagging need due to new software versions for applications such as Office 365 that update on their own and quite often?

 

2 - For Samanage support: is this something that you might address somehow? This need for re-tagging is by far the most time consuming operation we have to engage in during our normal Samanage use. One approach might be to enable some sort of tagging rules engine - a way for us to say something along the lines of 'if you see new software that has this name then tag it with this value regardless of the version number'. The Samanage application should be able to help with this instead of requiring users to redo this tagging work each time application updates are detected.

 

 

Thank you.

Outcomes