Software Installs not listed in the CMDB?

[amber_martin]

We are implementing our CMDB. We are having problems with the software showing where it was installed on the CMDB.

If you go to Configuration/Base Items/Software it doesn't list where the Software is Installed on.

To see where the items are installed on you have to go to Software Asset/Discovery/Software Installations and click on Display name.

According to the Wiki…these tables are related.

So is this an issue with Related Lists? Was there something we are missed when turning on the SAM plug in? Any help would be greatly appreciated.

[jake_mckenna]

To fix this you need to update the forms to show the related list Software Installs on the CI record instead of utilizing the older tables you are referencing here.

[Community Alums · Accepted solution]

Amber,

Because Configuration > Base Items > Software is more of a legacy table with SAM activated, here is my suggestion:

Remove this module and replace it with a module that points to Software Models.

Because Software Models also do not related directly to installations, you still need to make a custom related list to see installations directly on the Software Model record. Here's how:

• Navigate to System Definition > Relationships.
• Create a new Relationship (which defines the related list you can then add to the Software Model record).
• Here is what mine looked like. The name you provide here is the name displayed on the related list.
• 
• What this does is it queries the Software Installation table for installations that point to discovery models that point to the Software model. The query dot walks to the discovery model to get the referenced model and compares against the sys_id for the "parent" (which is the Applies to table).
• Then you can add this related list to the Software Model and see all your installations under the Software Model.

So you might be thinking, why not create a custom related list to view the installations from Software [cmdb_ci_spkg]?

The wiki article states that the Discovery Model writes to the old table, but it does not state that a relationship is created between the Software Discovery Model and the old software table. I was going to provide some direction to make a related list here, but I do not see any actual connection between these tables to support this.

As Jake stated, on the hardware CIs, you need to adjust the related list that displays from Installed Software to Software Installation, but for this old Software table, I think the best bet is to look to phase it out.

I hope this helps,

Ben

[sabell2012]

Ben:

Great answer, and you appear to be the only one to have figured this out.   It is exactly what I was looking for to solve a client issue I am having.  

You need to write this up as a ITOM: Disco blog article!

Steven.

[PoornachandarA]

We need help on similar thing as below:

"Regular IT (ITIL) agents are unable to view the **Software Installation** table in ServiceNow. It appears that the current visibility is restricted to users with the **SAM Pro** (sam_user) role. However, regular CMDB or IT agents should have access to see software installed on the devices they manage, especially for network administrators who need to monitor the software installed on their servers. The question is whether the SAM Pro role is the only option to grant this visibility, and if not, what configuration changes or access rights need to be adjusted to allow regular IT agents to access the Software Installation table."

Steps to Reproduce:

1. Log into ServiceNow as a regular ITIL agent (without SAM Pro role).

2. Navigate to the **Software Installation** table.

3. Observe that the table is not visible or accessible to the regular ITIL agent.

4. Log into ServiceNow as a user with the **SAM Pro** (sam_user) role.

5. Navigate to the **Software Installation** table and observe that it is visible and accessible.

6. Compare the access rights between regular ITIL agents and SAM Pro role users.