Microsoft SCCM integration
Summarize
Summary of Microsoft SCCM integration
The Microsoft SCCM integration enables a one-way import of Configuration Manager (SCCM) data into the ServiceNow Configuration Management Database (CMDB). It uses a JDBC connection via the MID Server to import relevant data from the SCCM SQL Server database, either fully or incrementally, keeping the CMDB synchronized. The SCCM database acts as the authoritative source and is not modified by ServiceNow.
Show less
Supported Versions and Recommendations
- The legacy Microsoft SCCM plugin is deprecated and no longer supported for new activations.
- ServiceNow recommends migrating to the Service Graph connector for Microsoft SCCM, which supports SCCM versions 2007, 2012 v2, and 2016 (including 1606, 1906, 1910, and 2002).
- New ServiceNow instances require a supported SCCM version, although upgrades allow continued use of older versions.
Service Graph Connector Benefits
- Alignment with the Common Service Data Model (CSDM).
- Use of the Identification and Reconciliation Engine (IRE) to prevent duplicate records.
- Support for removed software detection and delta detection.
- Utilizes IntegrationHub ETL (version 2.2.1) for easier data mapping and customization.
- Improved performance during data processing.
Available Modules
The integration provides modules to manage configuration and monitoring of the import process, including:
- Setup: Configure database server settings and MID Server; test connection.
- Scheduled Import: Schedule or immediately execute data imports.
- Data Sources: Manage pre-configured external CMDB database sources.
- Progress: View logs of scheduled import progress.
- Transform History: Track data transformation logs.
- CI Identification: Define identifiers for matching SCCM data with CMDB records.
- Import Set Data: View tables storing imported SCCM data.
- Web Services: Manage web services for modifying transform maps.
Asset Intelligence Feature
Asset Intelligence is an SCCM feature that cleans and normalizes software data. When enabled, it populates a separate table with normalized software records. Importing from this table results in cleaner software data in the CMDB. To use this, you must activate the SCCM Asset Intelligence scheduled imports both in ServiceNow and in the SCCM database.
Activation and Dependencies
Activating SCCM plugins requires administrator privileges and depends on the Integration - JDBC and CI Identification plugins, which are automatically activated with the SCCM plugin.
Data Import Process
Importing data involves setting up a JDBC data source connection to the SCCM database and scheduling data fetches via the MID Server. To avoid duplicate software data, activate either the Asset Intelligence or the non-Asset Intelligence scheduled imports.
Upgrading the Integration
If using an earlier SCCM plugin version, customers can upgrade to benefit from new features and improved capabilities by switching to a later version or migrating to the Service Graph connector.
The Microsoft SCCM integration is a one direction import of SCCM data into the ServiceNow Configuration Management Database (CMDB).
Scheduled imports bring relevant SCCM data into the ServiceNow instance from an SQL Server database and map it to tables in the CMDB. You can configure either a full or incremental data import. The import is achieved using a JDBC connection via the MID Server. The integration keeps the ServiceNow CMDB synchronized with the SCCM SQLServer database, so that only relevant data is imported from the SCCM database to the CMDB. The SCCM database is considered an authoritative source and is not written to.
Supported versions
The Microsoft SCCM legacy plugin is deprecated and no longer supported or available for new activation. For details, see the Deprecation Process [KB0867184] article in the Now Support knowledge base. Recommendation for all customers to migrate to the new Service Graph connector for Microsoft SCCM.
- Microsoft SCCM 2007
- Microsoft SCCM 2012 v2
- Microsoft SCCM 2016
The Integration - Microsoft SCCM 2016 (com.snc.integration.sccm2016) plugin is compatible with SCCM versions 1606, 1906, 1910, and 2002.
Service Graph connector for Microsoft SCCM
To import SCCM data into the CMDB, you can use the Service Graph connector for Microsoft SCCM instead of using the legacy SCCM connector.
- Adherence to the Common Service Data Model (CSDM) data model.
- Use of Identification and Reconciliation engine (IRE) to avoid duplicate records.
- Support for removed software detection and delta detection.
- Use of the IntegrationHub ETL (2.2.1) which allows for easy data mapping and customizations.
- Higher performance during data processing.
For information on how to update from using the Microsoft SCCM connector plugin to using the Service Graph connector for Microsoft SCCM, see Update Microsoft SCCM 2016 plugin for Service Graph connector for Microsoft SCCM.
Available modules
- Setup:
- Configure the data sources.
- Specify database server settings and the MID Server.
- Test the configuration.
- Scheduled Import: Schedule the import or execute the import immediately.
- Data Sources: A list of the pre-configured data sources defining the external CMDB database.
- Progress: The progress log for scheduled imports.
- Transform History: A log of transformations performed by scheduled imports.
- CI Identification: Identifiers used by SCCM to match import set data with the CMDB.
- Import Set Data: Tables that store imported SCCM data.
- Web Services: List of web services used to add or remove fields in the transform maps.
Asset intelligence
Asset Intelligence is an SCCM feature that can filter, normalize and clean up software records. When enabled, it populates normalized software data in a separate table within the SCCM database. You can target this separate table instead of the raw software data table. When you import software records into the CMDB with this feature enabled, you get a cleaner set of software data. To use this feature, you must Activate SCCM Asset Intelligence scheduled imports in the target ServiceNow instance, as well as in the source SCCM database.