The CreatorCon Call for Content is officially open! Get started here.

Non Licensable products being reported as non-compliant in SAM Workspace & License Compliance Report

Karen54
Mega Guru

Hi All, we have several products that are non licensable - Microsoft (eg Access Patch, OneNote Patch, WordPatch) that have appeared as non-compliant in the SAM Workspace and also the License Compliance Position Report. The entries have a symbol - a square with a diagonal line through it. How do we remove them from reporting as they are showing as non-compliant. Xanadu.

thanks

 

1 ACCEPTED SOLUTION

Karen54
Mega Guru

Hi Dennis

We raised a HI ticket and the initial response was to run a reconcilition. As this had been done many times I knew wouldn't resolve the issue. We resolved it internally by amending the Discovery Model manually. We reverted the Normalisation and deleted the SW Model entry in the Discovery Model that had been pointing to the SW Model which had been auto created for the Products with a license type patch and this resolved the issue. See below:

Karen54_0-1735041485632.png

 

View solution in original post

14 REPLIES 14

Karen54
Mega Guru

Karen54_1-1733236852745.png

 

Karen54
Mega Guru

Most recent Discovery Model.

dreinhardt
Kilo Patron
Kilo Patron

Hi @Karen54, I would recommend to raise a support case. Looks like the recon engine is unable to ignore your not-licensable products/software models. Please keep us posted about the result.

 

Best, Dennis

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

Agreed, will do and will post the resolution when I have it. Thanks

Karen54
Mega Guru

Hi Dennis

We raised a HI ticket and the initial response was to run a reconcilition. As this had been done many times I knew wouldn't resolve the issue. We resolved it internally by amending the Discovery Model manually. We reverted the Normalisation and deleted the SW Model entry in the Discovery Model that had been pointing to the SW Model which had been auto created for the Products with a license type patch and this resolved the issue. See below:

Karen54_0-1735041485632.png