Baseline is not relevant

Dear Team,

generally MS15-078 to MS15-090 patches are relevant to my endpoints but while i create those fixlets into baseline it will not come applicable to even single endpoint. Kindly share your views to short out this issue ASAP.


  1. BES Client service running perfectly
    2.Telnet to main server from client is successful
  2. ping and all connectivity is good
  3. from native (MS15-078) fixlet can deploy independently to endpoints but baseline not get any applicable machines for same fixlet.


What is the relevance of the baseline?
What site is the baseline in?
Do the clients subscribe to the site the baseline is in?

You need to validate communications in the other direction as well.

Server to Endpoint.

The default method is a UDP/52311 message sent to ‘registered’ endpoints (Relays or Endpoints) when new content is available for evaluation.

If UDP isn’t an option, verify that you have Command Polling enabled. Without UDP or Command Polling, endpoints will only gather new content once every 24 hours by default.

1 Like

Relevance : All Computers
Site: patch management

yaaa all clients are subscribe to all sites

Thanks & Regards

Thank you

I checked all things what you mentioned , but patches we can deploy alone but in baseline its still not come under relevant


when you create a baseline, you can locate it in one of these sites (master action site, operator site or any other custom site)
you can not create it in “patches for Windows site” (but domain may be “patch manageent”)
if you dont create the baseline in the master action site, you should copy the components of baseline into the site of baseline.

1 Like

thanks for your reply

I follow your procedures now and moved compenents under my custom site and its inside of Master action site only but still i am facing same


What site do you put the baseline in that you create?

How many components are in the baseline?

I don’t understand where you are having trouble. You should not have to copy any content anywhere to make a baseline work. As you add content to the Baseline, the Relevance and Action components for each component is added directly to the Baseline file itself.

The way I manage my Monthly Microsoft baselines is as follows …

  1. Imagine I have a Custom Site named “Custom Content”
  2. All Windows Systems are also subscribed to the Patches for Windows site.
  3. In my case, All Computers are subscribed to the “Custom Content” site.
  4. Once the Monthly Microsoft patches arrive from IBM and are gathered by BigFix, I create my baselines.
  5. Example: 2015-08 : Microsoft Critical/Important Patches
  6. The Relevance in the Baseline is adjusted to “Windows of Operating System” since the site has Macintosh and Linux hosts as well as Windows systems and I don’t want them to bother evaluating the Windows only content.
  7. I add all the Critical and Important patches released that month to the Baseline.
  8. I then save the Baseline in the “Custom Content” site.

Within a few minutes I’ll start to see computers reporting relevant to the baseline.

Note: Do not add ‘hundreds’ of fixlets/tasks to a single baseline or it could take a VERY long time for each computer to evaluate the baseline and report if it is relevant to it. This is why I create two baselines each month. One for Critical/Important Patches and another for the rest. Until you can determine what is going on, I recommend adding only one or two fixlets to the Baseline to keep evaluation times as low as possible.

1 Like

Do you have both Fixlets and Tasks in the baseline? I’ve been having the same problem as you, and that seems to be the problem. If I create a baseline with only fixlets or only tasks, then every computer that is relevant for ANY of the components will show the baseline as relevant. If I mix fixlets and tasks in the same baseline, it looks like a computer has to be relevant for ALL components before any of the components will be considered relevant. I have no idea if this is expected behavior or a bug, but it’s annoying and not well documented anywhere that I was able to find.

If this is behavior you’re seeing you should file a PMR.

If a fixlet is in a baseline and a computer is relevant for the fixlet, the computer is relevant for the baseline.

Tasks only factor into Baseline relevance if, “Baseline will be relevant on applicable computers where this component is relevant” is checked on the component. If this is checked then a computer that is relevant for the task, is relevant for the baseline. If it is not checked then only the relevance of other components in the baseline are considered.

Mixing Tasks and Fixlets should have no effect on how baseline relevance is calculated


Where is the option to check “Baseline will be relevant on applicable computers where this component is relevant?” I don’t see that option anywhere.


1 Like

That seems to be the underlying issue. For whatever reason, the fixlets are coming in with that setting checked by default. For what I’m doing, the fixlets aren’t necessarily relevant for all of the computers, but the tasks are. To get the effect I’m expecting, I needed to go to each component and make sure that option isn’t checked.

Thank you. This has been a real annoyance for us for a while.

1 Like

I think you might have that backward – you want this checked.

If you want the fixlet or task to “count” then you need this checked.

Essentially for a computer to run a baseline it needs to be relevant for one of the tasks or fixlets in that baseline that has this box checked. Generally you want this checked on every item in the baseline.

It’s checked by default for fixlets it’s not checked by default for tasks.

I have to run but I’ll edit this to explain why a little later.

You don’t want the box checked if the task or fixlet does not have relevance that goes to false, otherwise the baseline will reapply infinitely if it is set to reapply… but otherwise yes, if the item has relevance that goes to false after completing, then the box should be checked.