Scheduled imports bring pertinent SCCM data from a SQL Server database into the ServiceNow instance and map it to tables in the CMDB. You have the option of configuring a full or incremental data import. The import is done using the MID Server utilizing a JDBC connection. The integration maintains synchronization between the ServiceNow CMDB and the SCCM SQLServer database, ensuring that only relevant data is imported from the SCCM database to the CMDB. The SCCM database is regarded as authoritative, and it is not updated. Refer to this sccm tutorial to quickly understand the concepts like working, components of the architecture, SCCM features, installation, etc.
The Microsoft SCCM integration imports SCCM data into ServiceNow’s CMDB in one direction.
Integration – Microsoft SCCM 2007 Integration – Microsoft SCCM 2012 v2 Integration – Microsoft SCCM 2016 Microsoft SCCM Spoke for IntegrationHub
Apply the below steps for installing the plugin:
- To begin, go to System Definition -> Plugins.
- Locate the plugin with the use of filter criteria and search bar.
- Activate the plugin.
Installation of MID Server
For the ServiceNow MID Server, create a User Account. Incorporate a ServiceNow MID Server into your business. Validate the ServiceNow MID Server and ServiceNow’s communication.
Create an Account to an SQL Server for a Data Source of ServiceNow
A SQL Server user account is required for connecting the MID Server to the SCCM database so that ServiceNow data sources can be used. The MID Server would be unable to access the SCCM database without this account.
- SSMS is launched.
- Login to SQL Server Management Studio as an SCCM administrator.
- Type of Server: Database Engine
- Name of Server: Your SCCM SQL Server
- Navigate for Security -> Logins.
- Select “New Login” from the context menu when you right-click “Logins”.
- General Page
- SQL Server Authentication: true
- Login name: select login name
- Password: select password
- Enforce password policy: true
- Default Database: select your sccm database
6 A page for User Mapping
- Select SCCM Database
- Add Database Role: db_datareader
- Click Ok.
Setup for Integration
- Go to “Integration – Microsoft SCCM(version)”.
- Click on the Setup.
- Fill in all the corresponding details.
- For testing the connection to the SCCM database, click Test data source connections.
Data Imports on a Schedule
- Go to “Integration – Microsoft SCCM” -> “Scheduled Import”.
- In a Run field, choose a calendar interval like Day, Week, etc., and the time of the day the import must run.
- For a data import, choose the “Run as” user.
- Click “Save”.
- After completion, run the below-mentioned imports.
Setup Imports for Child Schedule: There are child imports that execute after the parent “SCCM 2016 Computer Identity” import has been completed. Imports can be deactivated or activated as needed.
Operating System for SCCM 2016: This is an add-on import that adds OS information to the cmdb_ci_computer database.
Processor for SCCM 2016: This is an add-on import that adds Operating System information to the cmdb_ci_computer database.
SCCM 2016 Disk: The cmdb_ci_disk table is updated by this additional import. This is sometimes turned off owing to the size of huge SCCM databases.
SCCM 2016 Network: The cmdb_ci_network_adapter table is updated by this additional import. This is sometimes turned off owing to the size of huge SCCM databases.
INTELLIGENCE ON ASSETS: SCCM’s Asset Intelligence capability filters, normalizes and cleans up software records. It populates a separate table within the SCCM database with normalized software data when enabled. You can use this table instead of the raw software data table to target. You obtain a cleaner collection of software data when you import software records into the CMDB with this functionality enabled.
You’ll need to enable some Scheduled Imports and disable others if you’re using AI for SCCM.
- Software of SCCM 2016: It is for scheduled imports that aren’t AI. By default, it is activated, and while using AI deactivate it.
- Removed Software of SCCM 2016: It’s used for non-AI scheduled imports. By default, it is activated, and while using AI deactivate it.
- Software (with Artificial Intelligence) of SCCM 2016: It is for AI imports that are scheduled. By default, it is deactivated, and while using AI activate it.
- Removed Software (with Artificial Intelligence) of SCCM 2016: It is for AI imports that are scheduled. By default, it is deactivated, and while using AI activate it.
Use SCCM or Discovery to acquire software data
If both Discovery and SCCM are enabled on a machine, the software records found by both programs may overlap.
- Go to “Discovery Definition” -> Properties.
- Set the Windows software managed by SCCM property (glide.discovery.software_sccm_managed) to the appropriate value. If this parameter is set to Yes, SCCM will populate the CMDB with software for computer CIs.Discovery doesn’t populate the software records for Windows software data until an internal mechanism decides that the computer is managed by SCCM. In the Discovery log file, the following information level message is written. Because the CI is maintained by SCCM, the software population is skipped. If the checkbox is unchecked, the property is set to No, and the system uses Windows to manage software data.
- Click on “Save”.
Note: Discovery excludes the population of software for any CIs that are also imported via SCCM when SCCM Integration is set before Discovery is enabled and the property is permitted. Software installation data from both sources will likely be intermingled if Discovery is activated before the SCCM Integration.
The Transform Maps
In ServiceNow, you can find the transform maps listed below.
In this blog, we have explored the plugins available for integration, steps to install MID server, configuring the integration steps, scheduling the data imports, and the transform maps. Further, you have to get certified with this online sccm training course to upskill the SCCM concepts like deployment scenarios in the configuration manager, Configuration for role-based administration, monitoring configuration of the system center, etc.