I am performing research for a potential SAM use. I understand that there are many different types of software license types (ie: enterprise, volume licenses, by cpu, by person, etc.).
I also understand that in using a SAM, the primary source of license "verification" would come from purchasing records (PO's, payment receipts, etc.) that would need to be integrated into the SAM system.
Lastly, I understand that, the most likely way to do a license compliance check is to basically match up the purchasing data collected and normalized against the discovery data that was collected and normalized. Hopefully, everthing matches up close and that's great.
I have a couple of scenarios below that an experienced SAM (admin/manager) should be able to answer, either from direct experience or accepted practices. I'm posting this with a high award because the accepted answer must be thorough, well expressed and should show true evidence of experience this this area. You're going to have to take some time to write up some detail so there is minimal ambiguity or mis-understanding. If you are going to just point me to a SAM website resource, then please don't bother.
1) The original purchase data shows ABC software, version 2.1 and is correctly matched against discovery data but the software was later updated by the user to version 2.5 so what used to match now does not. How is this reconciled and/or fixed?
2) An original software purchase for ABC software, version 3.1 is in the SAM system and matches up in a compliance check against discovery data. The software is later replaced by a competitive purchase of DEF software version 4.5 at a significant lower than retail cost. Do any SAM systems allow for a way to indicate a competitive purchases replacing an existing software asset? Otherwise, you end up with 2 purchasing records for both sw assets, 2 discovery sw assets, yet only one should be installed and licensed.