"Cloud License Type" is not getting populated for installed software by Discovery.

Hrishabh Kumar
Giga Guru

‎05-06-2024 12:37 AM

I'll explain the issue with an example, Please go through it and let me know how to remediate this.

I have a Window Server "BXAZEUWAPWTMI33" and there are few software running/installed on the machine.

Once we run discovery on "BXAZEUWAPWTMI33", all the information about the software's are populated/updated in "cmdb_sam_sw_install" table. 

 

If I run Discovery on "BXAZEUWAPWTMI33", Discovery is getting completed successfully, and Related softwares are getting updated in "cmdb_sam_sw_table", but "Cloud License Type" field is not getting populated.

I'm not sure weather Discovery is bringing this data or not.

 

here is the screenshot attached where we can see that discovery is updating the software data, but not populating the "Cloud License Type" field.

CLT not updated.PNG

 

I will need answers to the following questions:

1) Do Discovery brings "Cloud License Type" data, or how can I check if discovery is bringing this data?

2) How can I remediate this issue, where to check for the logs, or other information. 

  • 1,017 Views
3 REPLIES 3

SalvatoreS
Tera Contributor

‎01-24-2025 02:50 AM

did you find a solution for this issue?

 

0 Helpfuls

LFS
Tera Expert
In response to SalvatoreS

a week ago

Hello all! It seems like there are still no more details shared regarding this question. I would also appreciate more input from the Community for this one, as I'm looking for the same resolution for Red Hat related systems. Here's a KB that can help, though: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1635251. Besides, ellaborating further in this KB would be amazing. This area is critical for accurate compliance reporting for virtualized systems. Thanks so much in advance!!

0 Helpfuls

LFS
Tera Expert

a week ago

More on this topic: This article is very useful - https://www.servicenow.com/community/sam-blog/review-software-inventory/ba-p/3304249, more specifically the section on "Review Installs of supported software missing cloud license type (only for server software)":

 

 

  • Review Installs of supported software missing cloud license type (only for server software) 
  • Server software like Microsoft Windows Server, SQL Server, Oracle DB, RHEL can be deployed on cloud providers like AWS, Azure, Google Cloud with Bring your own license. Hence, it is important to discover the License type as BYOL, or license included for these software installs discovered. 
  • Details about discovery: https://www.youtube.com/watch?v=7-G-HCKV0zI 
  • Details about BYOL license support on SAM Pro: https://www.servicenow.com/community/sam-blog/bring-your-own-license-support-on-servicenow/ba-p/2284... 
  • Where to find this issue: 
  • This would show up on the License usage analysis- unlicensed entities- Installs with action- Installs without a software entitlement 
  •  
  • Recommended Actions for SAM Managers/Analysts: 
  • If using ServiceNow discovery:  
  • ServiceNow discovery support cloud license type determination for 
  • Microsoft Windows Server on AWS, Azure and GCP 
  • Microsoft SQL Server on Azure only (AWS when integrated with cloud cost management) 
  • Oracle DB Server on AWS and Azure 
  • RHEL on AWS, Azure and GCP 
  • If using other discovery sources:  
  • In case discovery is not possible for some reason, you can create tags on the cloud VM and those will be discovered. The tags must be created on the cloud providers using a particular format: 
  • <software-product>_License_Type_automatic and a Value of either License Included, BYOL, or BYOS. 
0 Helpfuls