- Print
- DarkLight
Microsoft System Center Configuration Manager (SCCM) is a systems management product for managing large groups of computers providing remote control, patch management, software distribution, operating system deployment, and hardware and software inventory management.
Integration
Microsoft SCCM is a on premises product. To get at the data within SCCM, a script running a query will run and post results to an Azure blob. From there, DataBee can pull data from the Azure Blob.
Integration Method: Azure Blob
Tables: Device Inventory, Application Lifecycle
Events: Software Information, General Events
Azure Blob Setup
Data is ingested via an Azure Blob.
The steps needed to set up Azure Blob are detailed at https://docs.databee.buzz/docs/azure-blob-ingest
Microsoft SCCM Configuration
Configure Query in SCCM
Create a query using the provided details below,
Query:
SELECT SMS_R_System.Name, SMS_R_System.ResourceId, SMS_R_System.IsVirtualMachine, SMS_R_System.IPAddresses, SMS_R_System.IPv6Addresses, SMS_R_System.IPSubnets, SMS_R_System.AgentName, SMS_R_System.CPUType, SMS_R_System.NetbiosName, SMS_R_System.CreationDate, SMS_R_System.LastLogonTimestamp, SMS_R_System.FullDomainName, SMS_R_System.MACAddresses, SMS_R_System.VirtualMachineHostName, SMS_R_System.Build, SMS_R_System.BuildExt, SMS_R_System.OperatingSystemNameandVersion, SMS_R_System.OperatingSystemNameandVersion, SMS_R_System.SystemOUName, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.HardwareID, SMS_R_System.SerialNumber, SMS_G_System_ADD_REMOVE_PROGRAMS.TimeStamp, SMS_G_System_ADD_REMOVE_PROGRAMS.InstallDate, SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName, SMS_G_System_ADD_REMOVE_PROGRAMS.ProdID, SMS_G_System_ADD_REMOVE_PROGRAMS.Publisher, SMS_G_System_ADD_REMOVE_PROGRAMS.Version FROM SMS_R_System INNER JOIN SMS_G_System_ADD_REMOVE_PROGRAMS ON SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceID ORDER BY SMS_R_System.Name |
Download the Script
Script File: upload_sccm_data.ps1
Script Parameters:
- Query Name: Name of the created query in SCCM
- Storage Account Name: The name of your Azure Storage account.
- Blob Container Name: The name of the container within the storage account.
- SAS Token: Requires write access permission for shared access signatures. Generate SAS Token
Command to execute from scheduler:
.\upload_sccm_data.ps1 “Query Name” "<Storage Account Name>" "<Blob Container Name>" "<SAS Token>"
Note: If a value contains spaces, enclose it in double quotes.
Schedule the Script with required parameters
Configure the task in the Task Scheduler with Administrator account.
Steps are provided below.
DataBee Configuration
Detailed steps for configuring Azure Blob can be found at https://docs.databee.buzz/docs/azure-blob-ingest
- Log into the DataBee console, navigate to Data and click on Add New Data Source.
- Search for Microsoft SCCM and click it
- Select Azure Blob
- Enter basic data source details
- Data Source Name: a user-friendly name for the data source
- Owner Name: the name of the point of contact for the data source
- Owner E-mail: email address of the owner
- Enter Azure authentication details
- Client ID: the Client ID created for your Azure Enterprise application
- Client Secret: the generated Enterprise application client secret
- Tenant ID: the tenant ID created for your Azure Enterprise application
- Complete Azure Blob details
- Blob Account Name: the name of your Azure Blob Storage account
- Blob Container Name: the Azure Blob container where the blob file is located
- Prefix: full or partial blob path to match the files you want to ingest. The root container path is selected by default.
- Delete object in Azure blob ingest on read: enable the checkbox if you want to automatically remove objects from the Azure blob storage after they have been read
- Ingest Codec: an advanced setting that allows you to override how the incoming data is parsed. By default, it is set to ‘auto‘
- Azure Queue Name: enter the Azure queue name of the event grid which receives the blob event messages