Deploying software

Use deployments to install, update, or uninstall software on a set of target computers. Deployments can run once or be ongoing to meet requirements such as:

  • Maintain operational hygiene and system baselines.
  • Manage systems which may be online for short periods.
  • Rerun packages which become applicable as system states change.

Deployments do not run outside of a maintenance window unless the Override maintenance window option is selected in the deployment options. You must create at least one maintenance window for other deployments to run. For more information about creating a maintenance window, see Managing maintenance windows.

Before you begin

Create a deployment template

You can create a deployment template to save settings for a deployment that you can issue repeatedly. You can either create a deployment template from the Deployment Templates menu item, or you can select an option when you create a deployment to save the options as a template.

  1. From the Deploy menu, go to Deployment Templates and then click Create Deployment Template.
  2. Specify a name and optionally a description for your deployment template.
  3. Select deployment options. These options are the same as the options you can configure in an individual deployment.
  4. For self service deployments that are set for the future, use the Make Available Before Start Time option.

  5. Click Create Deployment Template.

You can use this template when you create a deployment.

Set the default deployment template

The default deployment template is applied when you create deployments. Importing Deploy with automatic configuration creates three deployment templates and sets one of them as the default. You can change the default template or remove a template as the default.

  1. From the Deploy menu, go to Deployment Templates.
  2. Select a template and click Set as Default.
  3. To remove the default designation from a template, select the default template and click Remove as Default.

Delete a deployment template

  1. From the Deploy menu, go to Deployment Templates.
  2. Select one or more templates and click Delete.

You can also click the name of your deployment template and then click Delete .

Create a software package deployment

  1. From the Deploy menu, go to Deployments and then click Create Deployment.

    You can also create a deployment from the Software page. Select a software package and click Deploy Package.

  2. Provide a name for the deployment and optionally provide a description.
  3. Select Software Package, select the package from the drop-down list, and then select the software package operation.

    You can filter packages by typing the platform, vendor name, or package title.

  4. Add targets.

    Select either of the following targeting methods and complete the fields as needed:

    • Select Computer Groups provides a drop-down list of dynamic computer groups. These groups can be added or removed from software package applicability results, as needed.
    • Set Targeting Criteria filters on all endpoints with a specific set of criteria and within the limiting groups selected from the drop-down menu of available groups. For example, you can type Operating System contains win in the Filter Bar or use the Filter Builder to target all Windows endpoints within those groups. Select individual endpoints to be included. The deployment is applied to all selected endpoints that meet the criteria.
  5. Select deployment options.
    1. Choose whether you want to use an existing deployment template. To create a new deployment template based on this template, select Do not use existing template and then select Save Deployment Options as template. For more information, see Create a deployment template.
    2. Specify a deployment frequency. You can either do a single deployment with a specific start and end time, or an ongoing deployment that does not have an end time.
    3. Designate the deployment time. You can choose from the local time on the endpoint or UTC time.
    4. Select self service options.

      For self service deployments that are set for the future, use the Make Available Before Start Time option.

    5. If you want the endpoints to download the deployment content before the installation time, select the option for Download Immediately.

      Select this option for future deployments. Files for the package are downloaded immediately only if the package is applicable.

    6. (Windows and macOS endpoints) You can enable end user notifications about the deployments. Select Notify User Before Running in the Pre-Notify User section, and then configure the following settings.

      • (Optional) Configure settings that allow the end user to postpone the start of the deployment.
      • Configure the Message Content that informs the user about the deployment.
      • (Optional) Select additional languages and provide translated title and body text for endpoints that are configured for other languages. To view the preview in additional languages, toggle the language drop-down menu in the preview.
    7. To minimize concurrent CPU utilization and disk input/output, select Enabled for the Distribute Over Time option and indicate a time.
    8. If you want to ignore deployment restrictions, select Override maintenance windows.
    9. Select whether to restart the endpoint. For more information, see Windows and macOS endpoint restarts.
    10. (Windows and macOS endpoints) You can enable end-user notifications about the completion of a deployment with or without a restart. Select Notify User After Running in the Post-Notify User section. If you enabled endpoint restarts, you can then configure the following settings that allow the user to postpone the restart:

      • Configure the Message Content that informs the user about the restart.
      • (Optional) Select additional languages and provide translated title and body text for endpoints that are configured for other languages. To view the preview in additional languages, toggle the language drop-down menu in the preview.


      The notification automatically disappears after two minutes if a user does not close it within that time.

  6. Click Deploy Software.

Windows and macOS endpoint restarts

Deploy can trigger a restart of any Windows or macOS system after updates have been installed. You can choose between the following options for the restart:

  • Restart silently and immediately after deployment. This option is typically used for servers and production machines in conjunction with maintenance windows and change control processes.
  • (Windows and macOS endpoints) Notify the system user about the pending restart and give the system user the option to defer the restart for a specified amount of time. Configure the following options:

    Final Countdown to Deadline

    Specify the amount of time in minutes, hours, or days to show the final notification before restarting the endpoint. This notification also shows a countdown until restart. If this notification is dismissed, it will reappear after one minute. Set a low value because this option is meant to signal a forced restart that cannot be postponed.

    Allow User to Postpone

    If you want to give the user an option to defer the restart for a specified amount of time, select this option. A user cannot postpone beyond the deadline.

    Duration of Notification Period

    Specify the amount of time in minutes, hours, or days before the endpoint must be restarted. The deadline is calculated by adding this value to the time the deployment completed for each endpoint.

    User Postponement Options

    Specify the amount of time in minutes, hours, or days that a user can postpone the restart.

    Message Content

    Specify the title and body of the notification message. You can use ||OPERATION||, ||PACKAGENAME||, or ||DEPLOYMENTNAME|| as variables in the title or body. If you are deploying a software bundle, the bundle name is used for the ||PACKAGENAME|| variable. Upload optional icon and body images for branding to avoid confusing users and to limit support calls. Enable additional languages and provide translated title and body text. Enabling additional languages requires End-User Notifications 1.6 or later and Deploy 1.3 or later. By default, the notification displays content in the system language on the endpoints. If you enable additional languages, the user can select other languages to display.

    Show Countdown

    Select this option if you want the notification to show the amount of time that remains.

End user notifications can be added to existing deployments by stopping, reconfiguring, and reissuing the deployment.

If no user is logged into an endpoint, the endpoint restarts immediately after a deployment completion even if the deployment is configured for a notification.

Create a software bundle deployment

A software bundle is platform-specific and each software package evaluates and installs independently, but is available only for the specified OS platform. If an individual package fails to install during a bundle deployment, you can decide if the bundle should continue and install the remaining packages, or you can choose to stop on failure and report the failure.

  1. From the Deploy menu, go to Deployments and then click Create Deployment.

    You can also create a deployment from the Software page. Select Software Bundles, select a software bundle and click Deploy Bundle.

  2. Provide a name for the deployment and optionally provide a description.
  3. Select Software Bundle and then select the bundle from the drop-down list.
  4. Add targets.

    Select either of the following targeting methods and complete the fields as needed:

    • Select Computer Groups provides a drop-down list of dynamic computer groups. These groups can be included or excluded from software package applicability results, as needed.
    • Set Targeting Criteria filters on all endpoints with a specific set of criteria and within the limiting groups selected from the drop-down menu of available groups. For example, you can type Operating System contains win in the Filter Bar or use the Filter Builder to target all Windows endpoints within those groups. Select individual endpoints to be included. The deployment is applied to all selected endpoints that meet the criteria.
  5. Select deployment options.
    1. Choose whether you want to use an existing deployment template. To create a new deployment template based on this template, select Do not use existing template and then select Save Deployment Options as template. For more information, see Create a deployment template.
    2. Specify a deployment type. You can either do a single deployment with a specific start and end time, or an ongoing deployment that does not have an end time.
    3. Designate the deployment time. You can choose from the local time on the endpoint or UTC time.
    4. Select self service options.

      For self service deployments that are set for the future, use the Make Available Before Start Time option.

    5. If you want the endpoints to download the deployment content before the installation time, select the option for Download immediately.

      Files for all packages in the bundle are downloaded immediately. Applicability for each package is not checked until the deployment start time.

    6. (Windows and macOS endpoints) You can enable end user notifications about the deployments. Select Notify User Before Running in the Pre-Notify User section, and then configure the following settings.

      • (Optional) Configure settings that allow the end user to postpone the start of the deployment.
      • Configure the Message Content that informs the user about the deployment.
      • (Optional) Select additional languages and provide translated title and body text for endpoints that are configured for other languages. To view the preview in additional languages, toggle the language drop-down menu in the preview.
    7. To minimize concurrent CPU utilization and disk input/output, select Enabled for the Distribute Over Time option and indicate a time.
    8. If you want to ignore deployment restrictions, select Override maintenance windows.
    9. (Windows and macOS endpoints) Select whether to restart the endpoint. For more information, see Windows and macOS endpoint restarts.
    10. (Windows and macOS endpoints) You can enable end-user notifications about the completion of a deployment with or without a restart. Select Notify User After Running in the Post-Notify User section. If you enabled endpoint restarts, you can then configure the following settings that allow the user to postpone the restart:

      • Configure the Message Content that informs the user about the restart.
      • (Optional) Select additional languages and provide translated title and body text for endpoints that are configured for other languages. To view the preview in additional languages, toggle the language drop-down menu in the preview.


      The notification automatically disappears after two minutes if a user does not close it within that time.

  6. Click Deploy Software.

Review deployment summary

You can get the deployment results by status, any error messages, and the deployment configuration details.

  1. From the Deploy menu, go to Deployments.
  2. Select either the Active or Inactive tab.
  3. Click the deployment name.
  4. Review the sections.
    • Deployment Details provides the deployment details, such as the package or bundle name, status, operation, OS platform, and execution information.
    • Targeting lists the targeted computer groups for the deployment.
    • Error Messages includes a brief description and the count of affected endpoints, which links to Interact if you want to drill down for more information about specific endpoints.
    • <Operation> Workflow and Notifications shows information about the deployment workflow and notifications.

Stop a deployment

You can stop a package or bundle deployment, but it does not remove packages that have already completed installation.

  1. From the Deploy menu, go to Deployments.
  2. On the Active tab, click the deployment name, and then click Stop.
  3. Go to the Inactive tab and click the deployment name to verify the status.

Reissue a deployment

You can restart a stopped deployment or reissue a one-time deployment. Reissuing a deployment creates a new deployment with the same configuration and targets.

  1. From the Deploy menu, go to Deployments.
  2. On the Inactive tab, click the deployment name, and then click Reissue.
  3. Make changes if necessary and then click Deploy Software.

Clone a deployment

You can clone an active deployment if you want to create a deployment that is similar to an existing deployment. When a deployment is cloned, the name is automatically prepended with Clone: and the targets are removed.

  1. From the Deploy menu, go to Deployments.
  2. On the Active tab, click the deployment name, and then click Clone.
  3. Make changes and then click Deploy Software.