New baselines are not relevant

Usage and Config
1

We recently had a problem with the SQL Server and database being used for BigFix, which prevented the console from starting. That issue was resolved with restoring the SQL database from over a week ago, from before the SQL problems started.

The BES console is working now and relevant patches are shown for the Windows computers. Existing baselines from earlier are also shown with relevant computers. However, if I create a new baseline in the Master site, relevant to all computers and with Microsoft patches that are needed on computers, the baseline is not relevant to any computers. “Baseline will be relevant on applicable computers where this component is relevant” is checked on the patches.

I am not sure where to start on determining why the baselines are not working?

Jeff

Update - I have also found that any new custom fixlets I add to BigFix are not relevant on computers, so it is not just baselines that are an issue.

2

You might check the client logs and see if they are producing errors when downloading new content.

3

I do not see any errors in a couple of the clients logs that I have checked. I also checked on the root server the BESRelay log file and do not see any errors there.

In the Deployment Health Checks section, all of the items listed have Passed except for a failure that the applicability is too large for one of our baselines, and for ‘Wake-on-lan forwarders deployed’.

4

If you make a change in one of you tasks, are your clients receiving the ping to download the new content?

5

You should file a severity 1 or severity 2 PMR with IBM and work with their support to resolve this.

The community will have a hard time dealing with errors related to a bigfix environment in an inconsistent state

6

Yes, the PMR is the right call. Support will help you. There are procedures you need to do when rolling back a database as your endpoints are not seeing new content from your actionsites due to versioning.