Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Microsoft SCCM 3.0 Overview

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

Microsoft SCCM 3.0 Overview

Version 3.0 uses a flat transition table to gather specific data from all the SCCM tables (except the Software table).

ServiceNow maps to this flat table and to the SCCM Software table and imports the data into the CMDB.
Note: ServiceNow Microsoft SCCM Integration version 3.0 supports Microsoft SCCM 2007 R2.


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 3.0 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 Microsoft SCCM Integration version 3.0 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.
Figure 1. SCCM Many to Many 2 Diagram