Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Discovery and SCCM together

Log in to subscribe to topics and get notified when content changes.

Discovery and SCCM together

Use these guidelines to avoid common issues when you use Discovery and System Center Configuration Manager (SCCM) together.

You must decided if you will use Asset Intelligence (AI) or non-AI software data sources. Because the software correlation data is tracked differently for each of these data sources, you should avoid switching back and forth between the two. If you must switch between data sources, remove all the software installation records imported by SCCM before the switch occurs. For general information about the SCCM integration, see Microsoft SCCM integration.

When Software Asset Management is not enabled, software installation records are stored in the Software Instance [cmdb_software_instance] table. When Software Asset Management is enabled, software installation records are stored in the Software Installation [cmdb_sam_sw_install] table.

Note: If records are not removed before the switch, duplicate records may exist. In the event that AI and non-AI data becomes mixed, clear the Software Installation table.

Overview of SCCM plugins

Each of the currently supported SCCM plugins supports Asset Intelligence and Incremental Software Reconciliation:
  • Microsoft SCCM 2007
  • Microsoft SCCM 2012 v2
Note: If you upgrade your instance to a version of the Now Platform that does not provide support for your version of SCCM, you can continue to use that version. However, all new instances require the use of a supported SCCM version.

Upgrading to another version

The ServiceNow SCCM integrations are self-contained and can exist independently. They each use their own import set tables, data sources and transform maps. However, all SCCM integrations will transform data into the same tables within the ServiceNow CMDB. To avoid the data being overwritten by another source:
  • Use one SCCM integration and disable all other SCCM scheduled imports.
  • Perform a full import to clear the cmdb_software_instance table, the cmdb_sam_sw_install table, and other tables of old SCCM data.
Note: It is possible to configure each plugin to integrate with SCCM 2007 or 2012 because the mechanism of the integration is actually the same, which is to leverage Java Database Connectivity (JDBC) imports. However, the data sources will need to be modified if a plugin is to be used for an SCCM version they’re not written for. Starting with Fuji, it is recommended to use the plugin version that corresponds to the SCCM version it is designed to integrate with.
To change the SCCM integration:
  • Disable the current integration by deactivating the SCCM import schedule.
  • Activate the new SCCM plugin.
  • Reimport all the software records when you are switching to an integration that supports incremental imports of removed software.

For instructions on disabling the current SCCM import schedule, see Upgrade the SCCM integration versionUpgrade the SCCM integration version