Automation

Configuration Automation

Learn how to create a configuration with a target OS and command, group related configurations into a bundle, and deploy either to specific endpoints.

1 min
July 14, 2026

What You'll Learn

How to create a single configuration with a target OS, architecture, and command
How to group related configurations into a configuration bundle
How to deploy a configuration or a configuration bundle to specific endpoints
How to use the built-in command generator when authoring a configuration
How to track a configuration deployment through to completion

Frequently Asked Questions

What's the difference between a configuration and a configuration bundle?

A configuration is a single, named action bound to an OS, architecture, and command. A configuration bundle groups several related configurations together, for example a set of rules that all turn off automatic updates for one application, so they can be managed and deployed as one unit.

Can I deploy a configuration to only specific endpoints?

Yes. A configuration deployment's Scope can be set to Specific Endpoints, with the exact target device or devices selected under Endpoints.

Does deploying "What to deploy" always mean a single configuration?

No. The deployment step lets you choose between deploying an individual Configuration or an entire Configuration Bundle, depending on how the deployment's scope was intended.

Is there a way to generate the command instead of writing it by hand?

Yes. The configuration action section includes a Generate Command option alongside the manual Command Type and Command fields.

How do I know a deployment actually completed?

The Config Deployment list shows each deployment's Stage (for example, Completed), a Progress count such as 1/1, and the Deployment Policy that was used.