
For large SCCM databases, sometimes this is turned off due to size. SCCM 2016 Disk: This is supplemental import that updates the cmdb_ci_disk table. SCCM 2016 Processor: This is supplemental import that updates the cmdb_ci_computer table with Operating System information. SCCM 2016 Operating System: This is supplemental import that updates the cmdb_ci_computer table with Operating System information. Deactivate or Activate imports as needed. Run the following imports when completeĬonfigure Child Scheduled Imports: Underneath the Parent “SCCM 2016 Computer Identity” import, there are child imports that run after completion.Select the “Run as” user for the data import.Select a calendar interval (Day, Week, etc.) in the Run field and specify the time of day the import should run.Navigate to Integration - Microsoft SCCM > Scheduled Import.Click Test data source connections to test the connection to the SCCM database.Navigate to Integration - Microsoft SCCM(version).Default Database: select your sccm database.Right Click Logins, and Select New Login.Have an SCCM administrator login into SQL Server Management Studio.Launch SQL Server Management Studio (SSMS).Without this account the MID Server will not be able to access the SCCM database. MID Server Creating a SQL Server Account for the ServiceNow Data SourceĪ SQL Server user account helps to connect the MID Server to the SCCM database for use with the ServiceNow data sources. Validate Communication Between the ServiceNow MID Server and ServiceNow. Install a ServiceNow MID Server in Your Organization. Find the plugin with the filter criteria and search bar.Ĭreate the User Account for the ServiceNow MID Server.Navigate to System Definition > Plugins.

The Microsoft SCCM integration is a one direction import of SCCM data into the ServiceNow’s Configuration Management Database (CMDB).
