Axonius Documentation
  1. Enforcement Action Library
  2. Manage CMDB Assets

Microsoft MECM - Deploy Application to Devices

Microsoft MECM - Deploy Application to Devices deploys a named SCCM application to the devices returned by the selected query or selected on the relevant asset page. The action replaces the target collection's device membership with the selected SCCM device hostnames, then creates the application deployment.

  • Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

When accessing an enforcement action using the API, you must use the backend form of field names.

Use the Syntax Helper to find the correct name. In the enforcement action, enable Configure Dynamic Values and select Syntax Helper.

📘

Note

Required Fields

These fields must be configured to run the Enforcement Action.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values (optional) - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
  • Host - Host for the WinRM connection to SCCM.
  • Username - Username for the WinRM connection.
  • Password - Password for the WinRM connection.
  • Port - Port for the WinRM session. Default: 5986.
  • Site Code - SCCM site code.
  • Application Name - Name of the SCCM application to deploy.
  • Collection Name - Name of the SCCM collection whose devices receive the deployment.

Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Additional Fields

These fields are optional.

  • Site Server - SCCM site server. The default is empty.
  • Deploy Action - Select Install or Uninstall. The default is Install.
  • Deploy Purpose - Select Required or Available. The default is Available.
💡

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

  • Host - Host for the WinRM connection to SCCM.
  • Username - Username for the WinRM connection.
  • Password - Password for the WinRM connection.
  • Port - Port for the WinRM session. Default: 5986.
  • Use SSL for WinRM Connection - Uses SSL for the WinRM connection. Default: enabled.

  • Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses SCCM PowerShell cmdlets to create the application deployment and manage the specified collection.

Required Ports

Axonius must be able to communicate via the following port:

  • TCP port 5986 for the WinRM session by default.

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

The following permissions and requirements are needed:

  • The configured SCCM account must be able to manage membership of the specified collection.
  • The configured SCCM account must be able to create the application deployment for the selected application and collection.

The implementation does not specify the exact SCCM permission names. Confirm the required permissions with your SCCM administrator or Microsoft documentation.

To learn more about Enforcement Actions, see Enforcement Actions.

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

VersionSupportedNotes
[To Verify][To Verify]The supplied implementation does not identify tested SCCM versions.

For more details about other enforcement actions available, see Action Library.

Updated 3 days ago

Did this page help you?