Deploying Fixlets

• All selected Fixlets are listed in a table
• You can apply filters using Single condition or Multiple condition (Criteria: AND/OR) options to refine the Fixlet list. You can click on Reset Filters to clear filters. For more information, see Filter by query.

• Fixlet Table – Review the list of Fixlets.

• Select Fixlets – Use checkboxes to choose one or more Fixlets for remediation. A counter shows how many are selected.

• Next/Cancel – Click Next to continue to Actions, or Cancel to exit.

Actions - Review or update Fixlet actions. In this tab, confirm the actions you want the Fixlets you have selected to perform. This is important because not every Fixlet has a single, default action. It is also possible to remove Fixlets that do not have any actions that can be performed on the devices selected in the prior tab.

• The Actions step lists all selected Fixlets.
• Action filter drop-down – Allows you to refine which Fixlets are shown in the list. Available filter options:
  • All Fixlets – Displays all Fixlets in the remediation set.
  • Fixlets that are not actionable – Displays Fixlets that cannot be acted upon.
  • Fixlets with no-default action – Shows Fixlets that do not have a predefined default action.
  • Action required – Filters Fixlets that require immediate attention.
• Actions step: Review and update the actions for the selected Fixlets.
  • For Fixlets requiring a choice, select the radio button for the desired action (e.g., Action1: to initiate the deployment process).
• Review the Fixlet attributes provided in the details pane to confirm accuracy.
• Each Fixlet has a toggle switch to enable or disable its deployment.
• Ensure the toggle switch next to the Fixlet is set to On.
• You can use Disable All or Reset All options as needed.
• Verify the deployment summary link at the bottom right.

• Once this information is provided, click Next to proceed to the Devices tab.

Devices - This step allows you to confirm the devices for the deployment. Choose to deploy to all applicable devices or utilize various filters to narrow down the deployment size. Since filtering is optional, it is possible to skip this step by clicking Next. you select which devices will be included in the deployment. You have three main approaches:

1. Filter by Query
   1. You can apply filters using Single condition or Multiple condition (AND/OR) options to refine the Fixlet list. You can click on Reset Filters to clear filters. For more information, see Filter by query.
   2. By default, the device table displays all devices that match the query, with details such as Device Name, ID, DNS Name, IP Address, Last Seen, OS Family, Operating System, and Device Type.
   3. Dynamic Targeting Option

      

      • Within this approach, you can enable the Dynamic Targeting Device toggle.
      • Dynamic filters define a matching criteria for devices to evaluate continuously until the deployment ends. Any device that matches this filter after the deployment has been created, will have this deployment applied.

      • New devices that match the criteria are automatically added.

      • A Preview of dynamically applicable targeted devices is shown to confirm eligibility.
2. Filter by Device group- Select a pre-defined device group to target.

   

   1. Locate and select your target groups:

      • Search: Use the search bar to type and quickly find specific groups by name.

      • Select: Check the box next to one or more groups under the Add new groups list.

      • Reset: Click Reset if you need to clear your current selections within the menu.

      • Click Apply within the dropdown menu to confirm your group selection.
3. Filter by Device 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.
   1. Regardless of how they are identified, each device must be in a separate row.
   2. 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.
   3. Use Verify List to confirm the entries before proceeding.
   4. The Preview area shows the final static list that will be targeted.
   5. Once the appropriate filters have been selected, or if no filter is needed, click Next.

Behavior - Some deployments can affect many devices simultaneously. The behavior tab provides you with control over deployment timing, display of alerts indicating Fixlet deployment availability for devices, and actions upon deployment completion. Note that selecting any of the provided options is not mandatory.

Offer to user: Enable this toggle to deploy the action as a BigFix "Offer".

When you enable 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.

The behavior tab has a number of toggle switches users can turn on or off. They are presented as an order of events from top to bottom. The sequence order is as follows:

1. Start download immediately - Some Fixlets can contain large files. This option allows users to control whether all applicable devices should begin downloading the Fixlet as soon as the deployment is created.

2. Before running message - As a device may become unresponsive while a Fixlet is being deployed, this gives users the option to display a warning for an amount of time before the Fixlet is applied. This may also be useful if a restart is required, so end users can save work.

   Enable the toggle and set the following options:

   • Enter the message text to display to the user before the action runs.
   • In Notify user for, select how long the message is displayed (for example, 10 minutes), and in and then, select what happens when that time ends (for example, Run action immediately).
   • Allow user to save work - Select this checkbox to let the user save open work before the action runs.
   • Allow user to cancel - Select this checkbox to let the user cancel the action.
   • Show confirmation message before running action - Select this checkbox to prompt the user 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?).
3. While running message - As a device may be unresponsive while a Fixlet is being deployed, this allows users to write a message that will be displayed on the screen until the deployment is complete. Enable the toggle, and then enter the message text to display to the user.

4. Post deployment behavior - Enable this toggle to control what happens on the device after the action completes. Select one of the following options:

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

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

5. On failure, retry - Occasionally, deployments fail to complete successfully on a device. Should this occur, this allows users to determine if they would like BigFix to automatically try the deployment again. Enable the toggle, 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.

6. Reapply whenever it becomes relevant again - This option automatically reapplies a Fixlet if it becomes relevant again after the initial deployment. Enable the toggle, and then set the following options:

   • with a - Select this checkbox and set the interval (for example, 1 hour) that BigFix waits between attempts.
   • up to - Select this checkbox and enter the maximum number of times (for example, 3) that BigFix reapplies the Fixlet.

After selecting the desired sequence, click Next to proceed to the schedule tab.

Schedule - not required. Determining a deployment’s start and end time gives BigFix users a tool to control their deployments. Typically, deployments do not happen immediately. Some devices may be powered down, or disconnected from the Internet, or otherwise unable to have the Fixlet applied. Scheduling allows to control how long BigFix will attempt this particular deployment.

There may be other reasons to control the end time. For example, an organization may wish to ensure that all deployments run overnight to minimize business impact.

• The schedule tab has two options: Start Time and End Time. In the first, select the calendar date and the start time when BigFix will begin attempting to apply the deployment. You may also select if you want to use client time (e.g., the time zone where the device is located) or UTC.
• In the second, select the calendar date and the start time when BigFix will stop attempting to apply the deployment. You may also select if you want to use client time (e.g., the time zone where the device is located) or UTC.
• If no scheduling option is selected, BigFix will begin the deployment immediately.
• Run during agent’s configured maintenance window: Select this option, if you want to deploy the Fixlet during the set maintenance window.
• Custom Constraints - The Time Constraint option lets you control when a deployment can run by defining specific time ranges. This ensures Fixlets are applied only during the approved hours or maintenance periods.

• Time Constraints: Specify the time range (for example, 11:00–23:00) when the deployment is allowed to execute.

• Day Constraints: Optionally, choose one or more days of the week to further limit deployment (for example, only weekends or weekdays).

• After selecting the desired schedule, click Next to proceed to the summary tab.

Summary - The summary tab shows all of the choices made related to the deployment created. This allows to review all of the things the deployment will do in one location.

1. Add deployment name (mandatory) field is auto-populated with a default name that you can edit on the Summary step. Keep the default, or enter a unique, meaningful name that describes the purpose of the action.
2. 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.
3. Review all configuration sections to ensure they match your intended scope. The Summary step lists the start and end date and time, the number of Fixlets included, the number of targeted devices, Before deployment begins, and Behavior.
4. 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.

5. (Optional) Click Back to navigate to previous steps and modify any settings.

   

6. Once satisfied with the configuration, click Deploy to initiate the remediation flow.

7. Wait for the system to process the request. Once submitted, a confirmation message appears: "deployment submitted successfully".
8. Click OK to close the deployment wizard and return to the main interface.