Software discovery

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Software Discovery

    Software discovery in ServiceNow enables you to identify and manage software installations in your environment by utilizing ServiceNow Discovery or Microsoft SCCM. This process involves importing entitlements and transferring software data into the ServiceNow AI Platform, enhancing your Software Asset Management capabilities.

    Show full answer Show less

    Key Features

    • Integration Options: You can use ServiceNow Discovery for data centers and Microsoft SCCM for desktop environments, along with the option to integrate third-party discovery solutions.
    • Automatic Population: ServiceNow Discovery automatically fills the Software Installations table, allowing for normalization and reconciliation of software data.
    • Pattern Customization: Use customizable patterns for software detection; base patterns are included for various applications like Citrix and Microsoft SQL Server.
    • SCCM Compatibility: Microsoft SCCM 2012 v2 and 2016 plugins are available for integration, with specific plugins required for software usage tracking.
    • Migration Readiness: Transition from older SCCM plugins to the Service Graph connector for improved integration in future releases.

    Key Outcomes

    By effectively using software discovery, you can ensure accurate software inventory management, maintain compliance, and improve cost management regarding software licenses. Integrating with ServiceNow enhances your ability to track software installations and their usage, providing clearer insights into your software landscape.

    After you've imported your entitlements, use ServiceNow Discovery or Microsoft SCCM to discover software installations in your environment and transfer that data into the ServiceNow AI Platform.

    Figure 1. Infographic showing setting up of ServiceNow Discovery or Microsoft SCCM
    This graphic provides an overview of how to setup either ServiceNow Discovery or Microsoft SCCM.

    While you may use Discovery Home for datacenters and Microsoft SCCM for desktop environments, you can integrate other third-party discovery solutions with CMDB to support Software Asset Management. To integrate a different discovery solution, add it manually, or you can download an application, from the ServiceNow Store. For more information about integrating a discovery source manually, see the Customer Success Center.

    To learn more about collecting data after you've integrated with both Discovery and SCCM, see Collect software data with either SCCM or Discovery.

    Discovery integration

    ServiceNow Discovery is used to automatically populate the Software Installations table so the software can be normalized and reconciled.

    Note:
    To use Discovery, the Discovery plugin must be activated.
    Discovery uses patterns in the discovery process that can be created or customized. The base system contains a wide range of patterns that cover most industry standard network devices and applications. The following are some of the base system patterns used by Software Asset Management.
    • Citrix XenApp
    • Citrix XenDesktop,
    • VMware vCenter
    • Microsoft SQL Server
    • Microsoft Exchange Server
    • Oracle Database Server

    You can also customize other patterns for Software Asset Management. For more information, see Create or modify patterns.

    Discovered software is stored in the Software Installations [cmdb_sam_sw_install] table.

    When software install records are written to the Software Installations table, a business rule verifies whether the unique combination of the discovered publisher, discovered product, and discovered version exist in the Discovery Model table.
    • If so, the reference to the discovery model is set in the Software Installations table.
    • If not, a new record is created in the Discovery Model table, and that discovery model reference is set in the Software Installations table.

    After discovery, normalization is run.

    For more information on Discovery, see Discovery with Software Asset Management.

    SCCM integration

    You can use SCCM by itself or with Discovery Home to identify software on your devices.

    Note:
    While you may use Microsoft SCCM for discovering software installations in your desktop environments, you can integrate other third-party tools.

    Both Microsoft SCCM 2012 v2 and 2016 plugins are certified with Software Asset Management. The corresponding Microsoft SCCM Integration plugin must be installed to integrate Microsoft SCCM with Software Asset Management.

    Microsoft SCCM Integration plugins:
    • Integration — Microsoft SCCM 2012 v2 (com.snc.integration.sccm2012v2) plugin
    • Integration — Microsoft SCCM 2016 (com.snc.integration.sccm2016) plugin
    Microsoft SCCM Software Usage plugins:
    • Integration — Microsoft SCCM 2012 v2 Software Usage (com.snc.samp_usage_sccm) plugin
    • Integration — Microsoft SCCM 2016 Software Usage (com.snc.samp.usage_sccm_2016) plugin

    The Integration — Microsoft SCCM 2016 plugin is compatible with SCCM versions 1606, 1906, 1910, and 2002.

    Important:
    These Microsoft SCCM plugins will be deprecated in the Tokyo release. If you are integrating with SCCM for the first time, request and install the Service Graph connector for Microsoft SCCM application from the ServiceNow Store instead. If you have already activated one of the Microsoft SCCM plugins on your ServiceNow instance, use the Migration Readiness Tool for Service Graph Connector for SCCM store application to prepare your instance for migration from the Microsoft SCCM plugin to the Service Graph connector. See Service Graph connector for Microsoft SCCM for more information on the Service Graph connector.

    For more information on SCCM and how to import your data into your instance, see Microsoft SCCM software usage.