.png?sv=2019-07-07&sig=i91%2FGcCVhhgTUXb2n8dEjT6nAt1Pw8kSld6hqj79EO8%3D&spr=https%2Chttp&st=2023-09-24T01%3A37%3A48Z&se=2023-09-24T01%3A47%3A48Z&srt=o&ss=b&sp=r){kind=logo}
Microsoft System Center Configuration Manager (SCCM) - Add or Remove Assets to Collection
- 08 Jan 2023
- 3 Minutes to read
- Print
- DarkLight
- PDF
Microsoft System Center Configuration Manager (SCCM) - Add or Remove Assets to Collection
- Updated on 08 Jan 2023
- 3 Minutes to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
The Microsoft System Center Configuration Manager (SCCM) - Add or Remove Assets to Collection connects to the SQL server defines and adds the devices to the collection, or removes the devices from the collection, depending on the settings in this action. This is performed for each entity retrieved from the saved query supplied as a trigger (or from the entities selected in the asset table).
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
- Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapter Fetch History and Asset Investigation Modules
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
- Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
- Use stored credentials from the Microsoft System Center Configuration Manager (SCCM) Adapter - Select this option to use the first connected Microsoft System Center Configuration Manager (SCCM) adapter credentials.
Note:
To use this option, you must successfully configure a Microsoft System Center Configuration Manager (SCCM) adapter connection.
Required Fields
These fields must be configured to run the Enforcement Set.
- EC Action - Select the EC Action to perform, either Add To Collection or Remove From Collection.
- SCCM collection name - The name of the SCCM collection to which the assets will be added or from which they will be removed.
- Instance Name - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
SCCM/MSSQL Server - The DNS/IP Address of the Microsoft SQL Server your SCCM instance is using.
- To use a specific named instance, the value supplied should be in the following format: {server_host}\{instance_name}.
- If no instance is supplied, the default instance will be used.
Port (default 1433) - The port use for the connection
Database - The name of the database inside the SQL Server (Usually starts with "CM_").
User Name - A user name with the required permissions.
Note:
* The best practice is to create a dedicated SQL local user for Axonius usage. For details, see Creating a Local Read-Only User for Microsoft SQL Server.
* If you are using a domain user, specify the domain and the user name in the following format: domain\username.
- Password - The user's password. The password must not include ";"
Note:
If Use stored credentials from the SCCM adapter is not enabled, the fields above are required.
- Tunnel Name - For Axonius-hosted (SaaS) deployments. Select the tunnel through which to connect to perform the action.
Required Ports
Axonius must be able to communicate with the MSSQL Server via one of the following ports:
- Microsoft SQL Server discovery port - 1433 (default for non SA users) 1434 (default for SA - SuperAdmin - users).
- The specific port for the supplied named instance, if relevant.
- Note that the port appended into the adapter configuration needs to match the global listening port of the SCCM database.
Note:
The ports listed above are the standard default SCCM ports. However, these ports might be different if SCCM is deployed and configured with custom ports specified by the customer.
Permissions
The User for this action needs DB write permissions
For more details about other Enforcement Actions available, see Action Library.