SAM Teams sometimes perform a wrong configuration on SAM Pro on some of the data objects like Software Models, entitlements which lead to incorrect license compliance. In some cases, the quality of data on the CMDB coming from discovery sources may also be the reason for the non-determination of license compliance on ServiceNow. It is important to differentiate between data issues and configuration issues for solving the problem Some common examples are listed here
Some more examples:
Example 1:
SAM Managers Query: Why is zero consumption seen for Windows Server DC- I have the installs and the entitlements correctly setup?
What was causing the issue?: The SAM Team had forgotten to create product install conditions to restrict Windows Server deployment in development environment to be licensed by Microsoft Visual Studio and deployments in production environment to be licensed by Microsoft Windows Server. To view Visual Studio setup correctly check Microsoft Visual Studio Setup on SAM Pro
Due to this mis configuration all Windows Server installs were getting licensed under Microsoft Visual Studio as Visual Studio is a suite of products offering almost all major Microsoft software products
Example 2:
SAM Managers Query:License required for Adobe Creative Cloud are showing grossly inaccurate numbers from their subscriptions.
What was causing the issue?: The SAM Team had incorrectly added allocation to entitlement for Adobe creative cloud subscriptions. For SaaS Subscriptions allocations are not required as assignment of license happens directly on the SaaS Portal.
In many cases, allocations are added as part of the software request process. This is a kind of 'soft' allocation wherein the SAM analyst/manager must work with the SaaS Portal admin and actually assign the license in the SaaS Portal and thereby remove the allocation.
List of common issues per SAM data object:
We will understand these issues and their resolution steps in the coming blog articles.
