Retrospectively determine why a task was not relevant

Content Authoring
1

I have a baseline, Reboot Computers, that contains 3 tasks First Reboot, Second Reboot, Third Reboot.

Relevance of the baseline is true, Relevance of the tasks is windows of operating system.

The tasks are separated into 3 groups within the baseline and when deploying I check the option for allowing reboot after the group completes.

For the most part, this works fine. For some servers, however, it (the action) shows as Not Relevant. Consequently, the server doesn’t reboot.
The reason I’m doing it this way is because the company allows patches to be deployed from 18:00-01:00 and then reboots are allowed in 1 hour windows (e.g.) 0100-0200.

The individual tasks show as applicable for the machines in question. The baseline is set to true. So why is it not relevant? The servers are Windows OS (and as mentioned, the tasks show as applicable to the servers).

2

Check the client logs on those machines.

If the time has gone past the end time of the action the status is ‘Not Relevant’

3

What specifically in the logs? They’re not the most verbose.

The action is deployed in advance of the time (usually 10 hours in advance) so wouldn’t expect it to be time related.

4

Look for the action ids in the logs - see when they were downloaded, whether they were deemed relevant, the activity in the logs during your activity window

5

Are there any other components, aside from these three Tasks, in the Baseline?

By default, when a Fixlet is added to a baseline, it is added to the baseline relevance. By default a Task is not.

image
image711×292 9.78 KB

If there are any components that are included in the Baseline Relevance, but none of those components are relevant, the Baseline as a whole will be non-relevant.

1 Like