SCCM Import
Data import process
- A schedule calledSCCM System <version> Importdetermines when the SCCM tables are imported into theServiceNow®instance. Imports can be executed immediately or scheduled to run at defined intervals.
- A MID Server retrieves the SCCM data and imports it into staging tables on the instance.
- Transforms run on the data in the staging tables and map the SCCM data to existing fields in the CMDB.
SCCM data imported
SCCM table | Staging table | CMDB table |
---|---|---|
| SCCM <version> Computer Identity [imp_sccm<version>_computer_id] | Computer [cmdb_ci_computer] |
v_GS_Disk | SCCM <version> Disk [imp_sccm<version>_disk] | Disk [cmdb_ci_disk] |
v_GS_Network_Adapter_Configuration | SCCM <version> Network [imp_sccm<version>_network] | Network Adapter [cmdb_ci_network_adapter] |
v_GS_Operating_System | SCCM <version> Operating System [imp_sccm<version>_os] | Computer [cmdb_ci_computer] |
v_GS_Processor | SCCM <version> Processor [imp_sccm<version>_processor] | Computer [cmdb_ci_computer] |
| SCCM <version> Software [imp_sccm<version>_software] |
|
SCCM_Ext.Add_Remove_Programs_DATA_DD | SCCM <version> Removed Software [imp_sccm<version>_removed_sw] |
|
SCCM_Ext.Add_Remove_Programs_64_DATA_DD | SCCM <version> Removed Software [imp_sccm<version>_removed_sw] |
|
SCCM data sources
TheServiceNow®SCCM integration uses JDBC data sources to import software data from the SCCM database. Each data source contains the connection specifics for the SCCM database and names the MID Server the instance will use to import the data. The transforms that map the SCCM fields to the CMDB are defined in a related list in each data source record.
Transform maps
Transform maps are accessed from theTransformsrelated list in each data source record. The source fields in SCCM and the target fields in the CMDB are listed in theField Mapsrelated list in each Table Transform Map record. The SCCM integration uses the transform map utility provided with theServiceNow®platform. For instructions on editing or creating a transform map, seeTransform maps.
- Incremental Import: Enabled by default. This map should be configured asActivewhenServiceNow®Software Asset Management is not enabled on the instance.
- Incremental Import (SAM enabled): If the Software Asset Management plugin is activated, set this transform toActive
Transforming the assigned user
The SCCM <version> Computer Identity transform script attempts to set theAssigned tofield in the CMDB record by looking up the name of the user in the SCCM source table and comparing the value with the matching field in the ServiceNow sys_user table. If a match is found, that user is assigned to the record. If no match is found, theAssigned tofield is left blank. The matching field is controlled by theglide.discovery.assigned_user_match_fieldsystem property, which is set touser_nameby default.
Identifiers
The SCCM integration uses CI identification to update CIs created from data imported from SCCM with a resource ID. The Hardware Rule identifier returns the resource ID of a computer from SCCM and stores it in the Source [sys_object_source] table. When resource IDs are first imported, either from SCCM orDiscovery, the [sys_object_source] table is populated with IDs for each CI it identifies. In subsequent imports, if an incoming ID matches that of an existing CI, IRE (Identification and Reconciliation Engine) updates the information for that CI in the CMDB. If the incoming resource ID does not match that of an existing CI, IRE creates a new CI and populates it with the resource ID.
For more information about CMDB Identification and Reconciliation and IRE, seeCMDB Identification and Reconciliation.
Scripts
Data population scripts populate the related data in the CMDB for each target CI discovered by the Hardware Rule identifier.
SCCM Integration Procedure
Procedure