Baseline Not Showing Relevant for Relevant Components

BES Agent 9.5.5.196 Windows 7 Enterprise

We have a Baseline that has its own relevance that the endpoint needs more than 4GB of free space. We have a component which by itself is relevant to the endpoint. However, when this same component is in the baseline, the baseline is not relevant to the endpoint.

The baseline is just a bunch of Office Uninstalls. All relevance shows as True on the endpoint when using the QnA. This is happening on several endpoints, which all seem to be working fine.

I’ve even used the troubleshooting client repair fixlet on one and no luck.

I’ve sent a blank action as MO to these few systems (entering the host name as the target) and no luck as well as a refresh.

1 Like

Is the baseline in a site that the computer is subscribed to?

Does the computer successfully receive the UDP messages from the server/relay telling it that there is new content?

Can you see anything in the client logs about it evaluating the baseline and being relevant to it?

You may be running into an issue that had me pulling my hair out for a while because I had no idea…apologies if you know all this already.

By default “Task” components do not cause endpoints to be relevant to the baseline. Only Fixlets do. I understand the reasoning behind this when all tasks used to be little one off things that you didn’t care about outgoing relevance checks, but I think making Software Distribution packages “tasks” has really muddied the waters. Because we almost always end up “changing” the SWD tasks to fixlets by making them succeed only if they pass the outgoing relevance check like fixlets do.

Anyway, here’s how you can check if that’s the issue. Edit your baseline then expand the component that should make the baseline relevant, and see if this box is not checked:

5 Likes

That’s what is driving me crazy. It’s more endpoints than it should be. Both the endpoints and the baseline are in the same site (subscribe to the site).

Regarding receiving UDP, if I perform a refresh via the Console on the endpoint, I almost immediately see it do its thing in the agent log. So is that a yes?

I don’t see the ID of the baseline in the logs.

I’ve completely removed the agent and reinstalled on one system and still no luck.

May I assume it should be? I read this in another post but they didn’t include the picture and I didn’t know what they were talking about. But you are correct, the tasks items that I have, the box is clear; while the fixlet items I have, it is checked.

I never would have even thought to expand those! So I should check them all, huh?

That was it, Sean! I owe you a Coke! Thank you very much!!! :kissing_heart:

1 Like

Great! Well, basically if you need the baseline to be relevant for any of your given “task” components, then check that box for each one that you want to affect applicability. Sometimes for example I have a “reboot” task that has relevance of “true”, so I would go ahead and leave that one unchecked. So you have to decide.

Thanks a lot Sean!!! for the information,It was very helpful to me as was facing the issues after recent version up-grade activity.

1 Like

@Sean thanks bro! saved a lot of my time muddling through this issue.

2 Likes