Version 2012 Overview

Version 2012 is designed to work with SCCM 2012 release 1.

It comes with default table views and related column names from SCCM 2012. Version 2012 can work with SCCM 2007, but it will require configurations on the table name and column names for certain data source imports.

A major difference between version 3.0 and SCCM 2012 is that a flat table is no longer needed for the import. Instead, data is imported from the Computer Identity data source table within SCCM. The table can be easily extended and configured to include additional information.

SCCM 2012 also provides three transform maps for a software import. Only one transform map can be enabled at a time.
  1. SCCM 2012 Software - Full Import
  2. Incremental Import
  3. Incremental Import (SAM enabled)

The first transform map performs a full import of the software data. This transform map automatically populates into the cmdb_ci_spkg and cmdb_software_instance tables or the cmdb_sam_sw_install table depending on if the Software Asset Management plugin is enabled. If the plugin is not enabled, the former tables are populated; if the plugin is enabled, the latter table is populated.

The second and third transform maps perform an incremental import and should be enabled or disabled depending on whether the Software Asset Management plugin was enabled. If the plugin is not enabled, use "Incremental import"; otherwise, use "Incremental import (SAM enabled)". By default, the incremental import transform map is enabled.
Note: ServiceNow SCCM Integration version 2012 supports Microsoft SCCM 2012.


The Microsoft SCCM integration uses CI identification to update CIs created from data imported from SCCM with a resource ID. A Discovery Identifier called SCCM ID & Class Name returns the resource ID of a computer from SCCM and stores it in a table called Source [sys_object_source]. When resource IDs are first imported, either from SCCM or Discovery, ServiceNow populates the Source table with IDs for each CI it identifies. In subsequent imports, if an incoming ID matches that of an existing CI, ServiceNow updates the information for that CI in the CMDB. If the incoming resource ID does not match that of an existing CI, ServiceNow creates a new CI and populates it with the resource ID.


Data population scripts added with the Integration - Microsoft SCCM plugin populate the related data in the CMDB for each target CI discovered by the SCCM ID & Class Name identifier.


The Microsoft SCCM Integration version 2012 reconciles the software package count in the records for a CI and removes a software instance from the Software Instance [cmdb_software_instance] table if the software package is uninstalled from the CI.
Note: The table data imported from SCCM in MicrosoftSCCM Integration version 2012 must contain complete data for the CI. ServiceNow assumes that the import represents all relationships that exist and adjusts the CMDB accordingly. Partial data received from SCCM tables can cause the deletion of active relationships.
For a full import, the resulting relationship looks like this:
Figure 1. SCCM 2012 Full Diagram
For an incremental import, the resulting relationship looks like this:
Figure 2. SCCM 2012 Incremental Diagram