question Re: ITAM Licensing Resource Counts seem to be incorrect in SAM forum

ITAM Licensing Resource Counts seem to be incorrect

CharlieDW — Fri, 19 Aug 2022 06:42:10 GMT

Hi all,

I'm looking at the itam_licensing_resource_counts table and found that we have 10k servers in our system. Diving deeper into it, I found that handheld devices and some VMs are considered a server. Any idea on how or why this is happening?

Many thanks in advance!

-Charlie

Re: ITAM Licensing Resource Counts seem to be incorrect

Community Alums — Fri, 19 Aug 2022 06:56:59 GMT

Hi @CharlieDW,

I think this answer is best answered by the Servicenow account executive who has been assigned to your company instance can help you.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

Re: ITAM Licensing Resource Counts seem to be incorrect

CharlieDW — Mon, 22 Aug 2022 07:26:42 GMT

Hi Sandeep,

Thanks for your reply. I opened a HI case for this and the team came back that this is a know issue in the SAMP product. There's currently no workaround, but the issue should be fixed in San Diego patch 5.

- Charlie

Re: ITAM Licensing Resource Counts seem to be incorrect

Community Alums — Mon, 22 Aug 2022 12:47:50 GMT

Hi @CharlieDW ,

Thanks for coming back!!

Kindly mark the applicable answer as Correct & Helpful both such that others can get help.

Thanks,
Sandeep

Re: ITAM Licensing Resource Counts seem to be incorrect

julianf — Mon, 22 Aug 2022 15:23:49 GMT

Hi Charlie,

Virtual Servers are considered servers for Subscription Unit licensing for SAM. We recently had customers reporting that handheld devices were being counted as servers. So this is a known issue, and recent patches to Rome and San Diego have corrected this. Once you upgrade to the latest patch and the nightly licensing job runs, you should see them captured as end user devices.

I suggest submitting a case, and support can confirm as well.

Re: ITAM Licensing Resource Counts seem to be incorrect

CharlieDW — Tue, 30 Aug 2022 09:39:59 GMT

Hi @julianf ,

Thanks for your reply to my question. It was indeed confirmed by ServiceNow once I opened the case for the issue. San Diego patch 5 should fix this 🙂

-Charlie