Microsoft Configuration Manager
Visualize Microsoft Configuration Manager (SCCM) devices, device collections, and local users in the JupiterOne graph. Use this integration to also monitor changes to Microsoft Configuration Manager entities using JupiterOne alerts.
- Installation guide
- Microsoft Configuration Manager data model
Installation
JupiterOne uses a connection to the Microsoft SQL server that hosts data for Microsoft Configuration Manager to pull data. If you have the ability to log into the database, it is strongly recommended that a user create an account specifically for JupiterOne to use. At a minimum, login credentials for an account that includes public
and db_datareader
permissions will be needed.
Configuration in Microsoft Configuration Manager
- In the object explorer, open the "Security" folder.
- Right-click on "Logins" and select "New Login..."
- Create a user using the following steps:
- Enter the login name
j1int
. - Select "SQL Server Authentication".
- Create a password.
- Set the default database to your Microsoft Configuration Manager database
- Navigate to the "User Mapping" page.
- Check the "Map" box for the Microsoft Configuration Manager database row.
- Ensure that both
public
anddb_datareader
are checked under "Database role membership for: " the Microsoft Configuration Manager database. - Click "OK".
- Enter the login name
Configuration in JupiterOne
- From the top-bar menu, select Integrations.
- Scroll to, or search for, the Microsoft Configuration Manager (SCCM) integration tile and click it.
- Click the New Instance button and configure the settings:
- Enter the Host for the Microsoft Configuration Manager database.
- Enter the Database name.
- Enter the login name for the account to be used for SQL data retrieval. (the
suggested name is
j1int
). - Enter the password for the account to be used for SQL data retrieval.
- Enter in a name and description for the integration instance.
- Click the Create button to complete the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Account | microsoft_configuration_manager_account | Account |
Application | microsoft_configuration_manager_application | Application |
Device | microsoft_configuration_manager_device | Device |
Device Collection | microsoft_configuration_manager_device_collection | Group |
Local User | microsoft_configuration_manager_local_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
microsoft_configuration_manager_account | HAS | microsoft_configuration_manager_device |
microsoft_configuration_manager_device | INSTALLED | microsoft_configuration_manager_application |
microsoft_configuration_manager_device_collection | HAS | microsoft_configuration_manager_device |
microsoft_configuration_manager_local_user | OWNS | microsoft_configuration_manager_device |