Microsoft SCCM (MECM) Microsoft SCCM (MECM)

Import your hardware/software inventory and patch compliance from SCCM

The Microsoft SCCM connector allows you to import your hardware and software inventory, patch deployments and policy compliance from Microsoft System Center Configuration Manager.

Objective

The SCCM connector allows you to import the following information:

  • Client hardware and software inventory
  • Applied deployments and patches
  • Policy deployment compliance

Prerequisites

  • Access to Microsoft SCCM with export rights
  • Active SCCM environment
  • Read permissions on SCCM database

Import modes

This connector works in file import mode. OverView accepts the following formats:

  • CSV: tabular export from SCCM
  • JSON: structured export from SCCM

Procedure

Export data from SCCM

  1. Log in to the SCCM (Configuration Manager) console.
  2. Go to Assets and Compliance > Devices for inventory.
  3. Select collections or devices to export.
  4. Click Export and choose the CSV or JSON format.
  5. For software updates, go to Software Library > Software Updates.
  6. Download the export file.

Import into OverView

  1. In OverView, go to Data Sources Settings > Sources.
  2. Select Microsoft SCCM and click Configure.
  3. Choose the CSV Import or JSON Import mode according to your export format.
  4. Import your export file.
  5. Click Save Configuration.

Synchronization frequency

Exports can be scheduled regularly via:

  • Manual weekly export
  • Integration with Windows scheduler for automation
  • Periodic PowerShell export script

Uploading files through DropPoint

Files for the Microsoft SCCM connector are stored in a dedicated S3 bucket named sccm. Drop your CSV (or JSON) files at the root of s3://sccm/: OverView automatically detects new files and imports them on the next synchronization.

Where do the files go?

Bucket : s3://sccm/

Example : s3://sccm/export.csv

Several ways to send your files

You can populate your bucket in several ways:

  • OverView web interface — import your files, configure the mapping, then click “Replace” to refresh the data without redoing the mapping.
  • AWS CLI — for a one-off or scripted upload.
  • S3 SDK (boto3, etc.) — to fully automate recurring imports.

Using the AWS CLI

# Upload a file to the sccm bucket
aws s3 cp export.csv s3://sccm/export.csv --profile ovs_your_org

# Or sync a whole local folder
aws s3 sync ./exports/ s3://sccm/ --profile ovs_your_org

Automating the import via S3

import boto3

s3 = boto3.client(
    "s3",
    endpoint_url="https://s3.oversoc.com",
    region_name="fr-par",
    aws_access_key_id="YOUR_ACCESS_KEY",
    aws_secret_access_key="YOUR_SECRET_KEY",
)

# Push the export into the sccm bucket
s3.upload_file("export.csv", "sccm", "export.csv")

Pair this script with a scheduled task (cron on Linux, Task Scheduler on Windows) to push your exports automatically at a regular interval. Each upload triggers a new import on the OverView side.

Prerequisite: generate your S3 credentials and configure your client (endpoint, profile) as described in the OverView DropPoint guide. The profile and endpoint used here are explained there.

← PreviousIvanti Patch ManagementNext →WAPT