- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2025 02:44 AM
We have an Adobe ETLA and SAMP is calculating the subscriptions correctly. However we are seeing the installed software from that subscriptions and SAMP is also counting these as separate installs so I have DC2024 and DC 2025 showing as Not Compliant as it is adding a lot of confusion for management.
What do I need to do to resolve this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2025 04:54 AM
Hi @andynewey,
this is true, for Adobe and Microsoft SAMP includes the software installation next to the subscription data into the reconciliation result.
At this point, SAM Pro expects that an assigned user has been maintained for each computer. Once an Adobe installation has been found, it is then compared with the user subscriptions (email) based on the assigned user. If the user of the computer does not have a valid subscription, this device/installation is displayed as non-compliant.
Please check whether all reported devices have a valid assigned user and that this is also assigned in the portal.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2025 04:54 AM
Hi @andynewey,
this is true, for Adobe and Microsoft SAMP includes the software installation next to the subscription data into the reconciliation result.
At this point, SAM Pro expects that an assigned user has been maintained for each computer. Once an Adobe installation has been found, it is then compared with the user subscriptions (email) based on the assigned user. If the user of the computer does not have a valid subscription, this device/installation is displayed as non-compliant.
Please check whether all reported devices have a valid assigned user and that this is also assigned in the portal.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-25-2025 03:10 AM
This process does show how difficult SAM Pro is to work with. This could easily be some sealed off functionality within the SAM workspace that allows the SAM_Admin role to run. How do I get this into the improvement suggestions box?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-25-2025 03:42 AM
Hi @andynewey ,
please check the following KB
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1156757
Best, Dennis