Voted Best Answer
Jan 11, 2016 - 11:09 AM
Do you have the same question? Follow this Question
Jan 11, 2016 - 11:09 AM
Jan 09, 2016 - 03:07 AM
Jan 10, 2016 - 07:51 AM
Jan 11, 2016 - 05:44 AM
I will assume your question is referring to Microsoft for the moment as the process/tools differ by vendor.
You start off with a list of devices and using one of the many tools out there (SCCM, MAP, SAM Tool Agent) you collect the “Add/Remove Programmes” data and this is what you want to normalise/optimize.
If you are using SCCM and MS MAP, all of the major SAM tool providers will support these data sources. The AssetLabs Streamline solution for Microsoft and Adobe is excellent as you can just rent it by the project or year. It also imports the MLS which saves you a serious amout of effort getting to that ELP. You can also export the cleaned up data to a CMDB or Helpdesk.
If you are deal with multiple vendors and don’t have a SAM tool Aspera is my suggestion as it’s works with most inventory tools already out there and the optimization module adds another layer of cleanup.
On a general point, if your estate is reasonably large (>10,000 desktops or > 100 servers) you will easily pay back your investment in any of the services with the time saved doing the task and the number of double counting removed. If the service is Saas you can usually try it out first and see the result before paying.
Jan 11, 2016 - 07:25 AM
Jan 11, 2016 - 10:56 AM
Jan 11, 2016 - 11:08 AM
Jan 11, 2016 - 11:41 AM
Jan 12, 2016 - 12:32 AM
Jan 12, 2016 - 01:21 AM
Jan 12, 2016 - 08:57 AM
A couple responses... before this thread goes too-off topic.
1) there 'sorta' is an industry standard for software recognition: ISO-19770-2. It's a framework where an application comes with a 'normalization & recognition tag ' (and also includes neat stuff lice ProductLine and LicenseType that allows an integration into Entitlement data). AssetLabs represents Canada in the ISO effort to have this standard adopted. That being said, I'll be the first to say that there is an inherent problem that the 'tag' has to come with the 'install'; so only NEW products come with the tag. But -tag or no tag - the recognition & normalization 'framework' is a standard ( and AssetLabs is able to apply this framework to non-tag software titles ... which happen to represent 99.9999999% of the population
2) A couple cool things happen when you start to overlap each companies software 'signature' of titles. Yes, each company experiences a pareto curve/long tail but - like a bunch of peacock feathers - the high portion ( the large quantities of Microsoft, Adobe, IBM, etc) are extremely overlapped... but each 'long tail' becomes less overlapping - and more distinct - as you go down the curve. Something else happens along each curve; the 'issue' for recognition/normalization transforms from Licensing to support to security.. We see all this stuff because the AssetLabs software library - all recongized and normalized - is acting as a wiki; though private to our clients only.
Where am I going with this? The efforts to create a public wiki of software titles will become quickly 'effectively complete' with less than 100 clients when it comes to recognizing licensing attributes of the small number of shared titles, but each of those 100 clients will soon discover that a vast majority of their 'longtail' titles are unique to them.... and they will have to do most of the work themselves! .. and that means less wiki-confirmation to create the confidence level expected.
And to support my fellow (and competitive) SAM 'tool' manufacturers, many of us have built libraries that actually work specifically for licensing reconciliation. But to get SW roecognition in a commodity price range, a SAM vendor would need to 'de-couple' the library from both their inventory tool as well as their licensing calculations in order to deliver 'just the data' at a commodity price expectation..