Install Software

Deploy software to specific devices by providing a download link and targeting filtered devices. This is a flexible way to deliver software without uploading packages manually.

Use the Install Software feature in the Custom Remediation app when you have a publicly accessible or internal URL for a software installer, you want to deploy that software to a subset of devices filtered by OS, name, group, or other criteria, and you need a lightweight, quick remediation workflow.

Install software

From the Custom Remediation app, select Install Software to open the Install Software wizard. The wizard guides you through five steps: Software, Devices, Behavior, Schedule, and Summary. A footer link, Install software package to N applicable devices, shows the current count of applicable devices.

  1. On the Software step (Where is the software package? (Supported formats: exe, deb, msi, pkg, rpm)), provide the software details, and then select Next:
    • In URL, enter the direct link to the software package hosted online. Supported file extensions are .deb, .exe, .msi, .pkg, and .rpm.
    • In SHA-256, enter the secure hash used to verify the integrity of the downloaded file.
    • In Size in bytes, enter the exact file size to validate the download.
    • Installation instructions as Local Administrator: This field is optional. Optionally enter Installation arguments (ex. /qn, -v, etc). BigFix generates the base installation command from the file type in the URL, so you only need to enter optional arguments, such as silent-install flags.

      Example: If you're installing an MSI and want a silent install, just enter /qn.

      BigFix will generate the full command automatically, e.g., msiexec.exe /i myApp.msi /qn.
      If you leave the field blank, BigFix will still send the appropriate base command, such as 
      msiexec.exe /i
        myApp.msi
    Note: The installation instruction is placed in the same directory as the software package. On the device, the download folder contains the software package and the generated installation command.
    Table 1. Example configuration
    Field Example value
    URL https://example.com/software/app.msi
    SHA-256 3a1f34e... (64-character hash)
    Size in bytes 10485760
    Software command app.msi
    Installation command msiexec.exe /i app.msi /qn
  2. On the Devices step (Filter the devices below), select the target devices, and then select Next. For Filter By, choose one of the following methods:
    • Query - Create dynamic filters based on device properties.
      • Apply filters using Single condition or Multiple condition (Criteria: AND/OR) options. For more information, see Filter by query
      • For each condition, select a Property, Operator, and Value.
      • Select Reset Filters to clear the filters.

      • (Optional) Turn on Dynamic targeting device toggle button to continuously re-evaluate the targeted devices so that devices matching the criteria are included as they report in.

      • Select Apply to evaluate the filters, and then review the Select the devices to remediate table to verify which devices match the criteria. The table shows the Device Name, ID, DNS Name, IP Address, and Last Report Time for each device.
    • Device group - Target an existing device group.
      • In Type to find groups, search for a group.
      • Select one or more groups under Add new groups.
      • Select Apply. Select Reset to clear the selection.
    • Device list - Select devices manually from the list. This option allows to input a fixed list of devices where the deployment will be applied. Devices can be identified using their name, DNS, and IP address.
      • Identified by name, DNS, or IP address, with each device on a separate row.
      • A maximum of 1,000 devices can be added in a single device list. If you intend to target more than 1,000 devices using device lists for filtering, create separate deployments.
      • Select Verify List to confirm the entries, and review the preview of the device list to be targeted.
      - Enter a fixed list of devices, identified by name, DNS, or IP address, with each device on a separate row. A single device list supports a maximum of 1,000 devices; to target more, create separate deployments. Select Verify List to confirm the entries, and review the preview of the static list to be targeted.
  3. On the Behavior step, configure how the deployment is delivered, how users are informed, and how failures are handled, and then select Next. The options under Order of Events (from top to bottom) are processed sequentially:

    • Offer to user - Turn on this toggle to deploy the action as a BigFix Offer.
      Note: An Offer lets end users choose and install software, patches, or other actions themselves through a self-service application, instead of having them deployed automatically by an administrator.

      When you turn on this toggle, set the following options:

      • Notify device owner of offer availability - Select this checkbox to alert the device owner when the offer becomes available.
      • Title - Enter the title that identifies the offer to the user.
      • Category - Enter the category that groups the offer in the self-service application.
      • Description - Enter the text that explains what the offer does.
    • Start downloading immediately - When on, targeted endpoints begin downloading the required payloads as soon as the action is deployed.

    • Before running message - When on, the configured message appears to the end user before the action starts, to provide context, warnings, or a request for confirmation. Enter the message text, and then set the following options:

      • In Notify user for, select how long to show the message (for example, 10 minutes), and in the and then list, select the follow-up action, such as Run action immediately.
      • Allow user to save work - Select this checkbox to let users save open work before the action runs.
      • Allow user to cancel - Select this checkbox to let users cancel the action.
      • Show confirmation message before running action - Select this checkbox to prompt users to confirm before the action runs. In Confirmation message, keep the default text or enter your own, for example Are you sure you want to run this action now?
    • While running message - When on and a message is configured, the message appears during execution to show that the remediation is in progress. Enter the message text to display to the user.

    • Post deployment behavior - When on, controls what happens on the device after the action completes. Select one of the following:

      • Do nothing after action completes - The device stays in its current state.
      • Restart computer after action completes - The device restarts when the action finishes.
      • Shutdown computer after action completes - The device shuts down when the action finishes.

      If you select Restart computer after action completes or Shutdown computer after action completes, configure the message shown to the user:

      • In Message title (required), enter a short title, for example Shutdown now.
      • In Message text (required), enter the message body that asks users to save any unsaved work.
      • In Notify user for, select how long to show the message, and in the and then list, select what happens when that time ends, such as Shutdown automatically or Restart automatically.
      • Allow user to cancel shutdown or Allow user to cancel restart - Select this checkbox to let users cancel the shutdown or restart.

    • On failure, retry - When on, BigFix reattempts a failed action. Enter the number of retries, and then select one of the following options:

      • and wait - Select this option and set the interval (for example, 1 hour) that BigFix waits between attempts.
      • Wait until computer has rebooted - Select this option to retry the action only after the device restarts.
    • Reapply whenever it becomes relevant again - When on, BigFix reapplies the action automatically if it becomes relevant again after the initial deployment. Select with a to set the wait time between attempts, and up to to set the maximum number of times.
      Tip: Reapplying increases the success rate by accounting for temporary issues such as device disconnection or network latency.
  4. On the Schedule step, define the window during which the deployment remains in effect, and then select Next. For the settings, see the Schedule settings table. Select Reset changes to clear all scheduling fields and restore the defaults.

    Table 2. Schedule settings
    Settings Description
    Time zone Select the time zone that applies to the start and end times: Client uses each endpoint's local time; UTC uses Coordinated Universal Time.
    Start Turn on Start to set when the deployment begins, and then select the Start Date and Start Time. If Start is off, the deployment can begin immediately.
    End Turn on End to set when the deployment window closes, and then select the End Date and End Time.
    Run during Agent's configured maintenance window Restrict the deployment to devices that have a configured maintenance window. The deployment runs only within those windows. The wizard notes how many currently targeted devices don't have a configured maintenance window; those devices are excluded.
    Run on all devices, regardless of their configured maintenance window Override maintenance window restrictions. The deployment runs on all targeted devices, whether or not they have a maintenance window configured.
    Custom constraints Control when a deployment can run by defining specific times and days.
    • Turn on Time constraints to specify a Start time and End time when the deployment is allowed to run.
    • Turn on Day constraints to limit the deployment to one or more days of the week.
  5. On the Summary step, review a consolidated, read-only view of every option you selected - URL, installation instruction, device criteria, start and end time, before-deployment settings, and behavior. This is the final checkpoint before deployment.

    • The Behavior section confirms the message and notification options that you set on the Behavior step, for example:
      • A message will be displayed before deployment begins.
      • Notify user for 10 minute(s), and then run action immediately.
      • A confirmation message will be displayed before deployment begins.
      • No message will be displayed while deployment is running.
    • In Action name, enter a unique, meaningful name that describes the purpose of the action. This name appears in action history, logs, and dashboards, which helps you and your team identify and differentiate actions. Use descriptive terms, such as "Critical patch - May 2026 - Windows devices", for clarity and traceability.
    • In Assign tags, add one or more tags:
      • To add an existing tag, type to search for it, select it from the list, and then select Add.
      • To create a new tag, type the tag name, and then select Add.
      Assigned tags appear as chips below the field. To remove a tag, select the X on its chip. Tags are saved with the deployment and appear in the Deployment Manager; you can't change them after you deploy. For more information, see Managing Tags.
  6. Select Install to install the software. The message Deployment submitted successfully confirms that the deployment was submitted.