Default action question

Usage and Config Patch
1

(imported topic written by mynameisbear91)

This crops up whenever I’m trying to “take default action” on multiple fixlets or when I am trying to create a baseline.

Some (BigFix-supplied, from content sites) fixlets that only have one action have the single action (Action1) marked as Default, and some don’t. This means that “take default action” doesn’t work for the ones that have no default action, and it also means that I have to go in and manually set the action for certain fixlets in my baseline, despite there only being one action.

Is this intentional? If so, what’s the rationale? I’m more curious than anything, really, although it is annoying.

2

(imported comment written by jessewk)

There are a few reasons we might not set a default action:

  1. There is an important note in the Fixlet description we think you should read before deploying

  2. The action might have “destructive” behavior if it was taken accidentally (e.g. Remove all BES Clients)

  3. You need to confirm you are licensed to deploy a BigFix Extension.

There are a few other cases but those are the primary reasons.

If you think you’ve found specific content that doesn’t meet those criteria, it’s possible we made a mistake and should go back and add a default action. Let us know if you run across something like that.

-Jesse

3

(imported comment written by mynameisbear91)

jessewk

There are a few reasons we might not set a default action:

  1. There is an important note in the Fixlet description we think you should read before deploying
  2. The action might have “destructive” behavior if it was taken accidentally (e.g. Remove all BES Clients)
  3. You need to confirm you are licensed to deploy a BigFix Extension.

Good call.