ConnectWise Automate - Deploy Patches
  • 22 Sep 2024
  • 2 Minutes to read
  • Dark
    Light
  • PDF

ConnectWise Automate - Deploy Patches

  • Dark
    Light
  • PDF

Article summary

ConnectWise Automate - Deploy Patches action is used to deploy patches for the software that results from the saved query supplied as a trigger (or assets that were selected in the asset table).

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

Note:

General Settings

  • 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.

Note:

This enforcement action runs on Software assets.

  • Use stored credentials from ConnectWise Automate adapter - Select this option to use ConnectWise Automate adapter credentials.

    When you select this option, the Select Adapter Connection dropdown is available, and you can choose which adapter connection to use for this Enforcement Action.

Note:

To use this option, you must successfully configure a ConnectWise Automate adapter connection.

Required Fields

These fields must be configured to run the Enforcement Set.

  • Entity Type (default: 0)
  • Entity ID (default: 0)
  • Compute Node - 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.

Connection and Credentials

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

  • Host Name or IP Address - The hostname or IP address of the ConnectWise Automate server.

  • User Name and Password - The credentials for a user account that has the required-permissions to perform this action.

  • Client ID - Create the Client_id in this link.

  • Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

  • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

  • HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the  HTTPS Proxy.

  • HTTPS Proxy Password (optional) - The password to use when connecting to the server using the  HTTPS Proxy.

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

APIs

Axonius uses the ConnectWise API.


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



Was this article helpful?