Trying to audit SAM - cannot see Reconciliation, Prescence or Normalisation

johnrob18
Giga Guru

I am auditing a customers SAM set up, been given SAM roles (sam_user & sam_admin) but cannot get any modules listed when i search for Reconciliation, Prescence or Normalisation. Is there another role required? (customer will not allow Admin)

7 REPLIES 7

Hi, 

 

the best for normalization are the discovery models for software installs and the content lookup portal for all content related stuff (PPN, etc.).

 

Tbh, not sure if your requirements for audit the recon can be fulfilled. The source are the SW installs, ci data, infrastructure, etc. Based on the license metric SAM Pro calculates and optimizes for the best result.


a small change in any of the parameters or a missing attribute (e.g., cpu core details) could end up in a different recon result.


To verify you can calculate each product result in excel … I’m sorry but I still don’t get the case behind the audit of recon etc?

 

we all know that a SAM tools is only as good as its data - as I sad before, missing data could produce results the customer is not „happy with“.

 

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

The ask is - 'we dont think SAM is working properly - we are getting duplicates, we have 3 sources (ACC, InTune and SCCM), my initial thoughts to imply that the SAM Pro had been installed but no specific configuration - it was just OOB - I am trying to understand how I can verify this - last time I had hands on SAM, there were applications for all the components - it now seems to be in the workspace but I cannot find where the parts are configured, just the results.  Any help or guidance would be appreciated

Hi @johnrob18,

 

in case of outdated knowledge about SAM Pro I’ve highly recommend the latest SAM Pro training for Zurich and the SAM Pro Ranger sessions on YouTube.

 

it’s correct, about the „duplicates“ in the sw install table. If a device is scanned by 3 sources you’ll have 3 rows per scanned software with a different discovery source - multi source cmdb. Please check the SAM properties that the multi source supports is enabled to activate the DeDuplication job - more details can be found here:

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0958768

 

Best, Dennis

 

 

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.