Microsoft MECM - Deploy Package to Devices

Article summary

Did you find this summary helpful?

Thank you for your feedback

Microsoft MECM - Deploy Package to Devices deploys packages for:

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.

Note:

Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.

Required Fields

These fields must be configured to run the Enforcement Set.

Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
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.

Host - A host that has Configuration Manager Cmdlets available to run via PowerShell.
Username - The username used to run the PowerShell commands.
Password - The username's password.
Site - The Configuration Manager Site in which the Enforcement Action will run.
Package ID - The ID of the deployed package.
Program Name - The name of the deployed program, which is a part of the package.
Collection Name - The name of the Axonius collection where all devices receiving the deployment will be stored. You first need to create such collection in Configuration Manager and make it exclusive for each Enforcement Action. For example, if you create two Deploy Package to Devices Enforcement Actions, each one of them requires a different collection name. To learn more, see Creating Collections.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

These fields are optional.

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

Axonius must be able to communicate via the following ports:

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

For more details about other Enforcement Actions available, see Action Library.

Was this article helpful?

Table of contents