Target release	New York
Platform Owner	Deanna Burns (Unlicensed)
Document status	WORK IN PROGRESS
Discovery SME Lead	Allena Kendrick (Unlicensed)
PM	David Swanson (Unlicensed)
CMDB Lead	Christopher Abbott (Unlicensed)
Business Analyst	Vandana Bansal
SN CMDB Lead	Vimalpriya Kothandapani (Unlicensed)

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

This table shows the SCCM source tables, the corresponding import set staging tables in theServiceNow®instance, and the target tables in the CMDB.

SCCM table	Staging table	CMDB table
v_GS_Computer_System v_GS_Workstation_Status v_GS_System v_GS_PC_Bios v_GS_Operating_System v_GS_Computer_System_Product v_GS_System_Enclosure v_GS_Baseboard	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]
v_GS_Add_Remove_Programs v_GS_Add_Remove_Programs_64	SCCM <version> Software [imp_sccm<version>_software]	Software [cmdb_ci_spkg] Software Installation [cmdb_sam_sw_install] (when Software Asset Management is enabled*)
SCCM_Ext.Add_Remove_Programs_DATA_DD	SCCM <version> Removed Software [imp_sccm<version>_removed_sw]	Software [cmdb_ci_spkg] Software Installation [cmdb_sam_sw_install] (when Software Asset Management is enabled*)
SCCM_Ext.Add_Remove_Programs_64_DATA_DD	SCCM <version> Removed Software [imp_sccm<version>_removed_sw]	Software [cmdb_ci_spkg] Software Installation [cmdb_sam_sw_install] (when Software Asset Management is enabled*)

*For more information about Software Asset Management and how to enable it, seeRequest Software Asset Management.

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.

The SCCM integration provides two transform maps for incremental software imports. Only one transform map can be enabled (Active) at a time.

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

Note:To force a one-time full import of all software data from the SCCM database, clear the value in theLast run datetimefield. This operation can take a long time to execute, so the most efficient method is to use an incremental transform after the first full import.

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

TheMicrosoftSCCM integration 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. For a full software import, the transform populates the Software [cmdb_ci_spkg] and Software Instance [cmdb_software_instance] tables. If the Software Asset Management plugin is enabled, the transform populates the Software Installation [cmdb_sam_sw_install] table.

Caution:The table data imported from SCCM must contain complete data for the CI. The instance 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.

Procedure

Navigate to Integration - Microsoft SCCM <version> > Setup.
Complete the required fields to configure connection to the SCCM SQL database. Make sure to include a valid MID Server that has access to the SQL database server.
SCCM data import setup
Under Related Links, click Test data source connections to test the connection to the SCCM database.
If the data source connects to the SCCM database, navigate to Integration - Microsoft SCCM > Scheduled Import.
The Scheduled Data Import form appears for your version of the SCCM integration. The Computer Identity data source runs first. The other data sources listed on the form run in sequence, based on their default order.
Select a calendar interval (Day, Week, etc.) in the Run field and specify the time of day the import should run.
Your selection displays additional fields required to complete the schedule.
Click Update to schedule the import or click Execute Now to perform the import immediately.
After the instance imports data using the SCCM <version> Computer Identity data source, the other data sources run in the order configured to retrieve the remainder of the SCCM data.

Browser not supported