Computers not rebooting after non-relevant Action Group applied

Usage and Config Patch
1

(imported topic written by arpotu91)

Hi All,

I’m seeing some unexpected behavior with regards to rebooting after patching.

A patching method being used by some folk here is to take a set of patch fixlets and target a set of computers as a “Multiple Action Group”. The folk choose the option to reboot 1 minute after the Actions complete. However, some of the computers evaluate as Not Relevant to the whole patch fixlet set, and they don’t reboot after evaluation. Is that because the actions were not relevant?

I ask because we have SLA’s with customers to reboot their computers monthly, regardless if patches need to be applied, and we were hoping to “kill two birds with one stone” by first applying any patches, then rebooting all targeted computers regardless if they were patched.

If this can’t be done, then we’ll need to schedule a separate action to reboot non-relevant computers during the same window.

Thanks,

Arpotu.

2

(imported comment written by chenbr91)

arpotu-

So you have answered your own question, as yes, if there are no fixlets that are relevant, the baseline will not be true and hence will not reboot that you checked off in the ‘Post-Action’ tab.

To work around this, you can create a reboot fixlet, and set the relevance to True and then in the action script just put restart.

For Example:

Relevance:

True

Action Script

Restart

Hope this helps.

Brian

3

(imported comment written by SystemAdmin)

when we try to update the pattern files (trend micro) it gives action is non relevant for the given computers