SAM Content Service & Software Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2024 09:35 AM
Hi,
I would like to clarify on below 2 queries with respect to SAM Pro implementation. Kindly help with answers.
1. Does the content library works in non-prod instances?
- I would like to know if we create any custom products, ppns in non-prod instances, does it passed on to ServiceNow content team? Or does it have to be in PROD?
- Hope, we will be receiving the updates to all instances including non-prod. Please correct it otherwise.
2. For the implementation, if we do not have discovery enabled to discover from all PROD hosts and computers in a non-prod instance, what is the best approach to have the software installations create discovery models and mapped using DMAP?
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2024 12:33 PM
Hi @Saran5,
A1.
ServiceNow docs does not mention any restriction to prod/non-prod, but I can image they maybe prefer prod instances. Even if all instances are included, there is no statement from the content team as to when these changes (Custom PPN, Product, ...) will be included and distributed in the official catalog. I can therefore only recommend that changes should be reported as quickly as possible via the corresponding support process, then it usually only takes ~2-3 weeks -> https://docs.servicenow.com/bundle/washingtondc-it-asset-management/page/product/software-asset-mana...
A2.
It is always best to use a regular PROD clone in such scenarios so that your Non-Prod instances receive all the latest data and test/use cases can be carried out under "productive" conditions.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2024 12:49 PM
Thank you, Dennis. Appreciate your quick answer.
With respect to the answer 2, I'm more curious that if we start with the SAM installation in a non-prod, the software will not be populated in cmdb_sam_sw_install. So, I assume the discovery models are not created. In our case, we will be migrating software entitlements from an external system. Once migrated, we rely on the discovery and sccm to provide the software installations with respect to the entitlements to calculate the rights. But, I will take your suggestion for now until I figure out the other approaches.