Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Configure the SCCM integration and schedule an import

Log in to subscribe to topics and get notified when content changes.

Configure the SCCM integration and schedule an import

Importing data from Microsoft SCCM requires a connection to the SCCM database via a JDBC data source and a schedule that tells the MID Server when to fetch the data.

Before you begin

Role required: admin

You must have credentials to query the SQL Server that contains the SCCM database.

About this task

The system uses the details of the database connection you create in this procedure to configure the default SCCM data sources automatically.
Note: If you want to access your SQL Server databases using Windows domain authenticated accounts, select the Use integrated authentication box on each of the existing data sources.


  1. Navigate to Integration - Microsoft SCCM <version> > Setup.
  2. 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.
    Figure 1. SCCM data import setup
  3. Under Related Links, click Test data source connections to test the connection to the SCCM database.
  4. 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.
  5. 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.
  6. 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.