Custom Baseline and Windows 7

(imported topic written by mholder91)

I have created a custom baseline with the following components: install .NET 3.5 only on XP machines, reboot after .NET install only on XP machines, uninstall an old application on both XP and Win7 machines, delete old application files on XP and Win7 machines, install new version of application on XP and Win7 machines and finally copy new files on XP and Win7 machines. I have the baseline relevance set up to apply to any and all XP and Win7 machines. By doing this I would expect the behavior of the baseline to be relevant to all XP and Win7 machines and then depending on the OS, some components would get skipped if they weren’t relevant. However, the behavior I’m seeing is that the baseline is only relevant to XP machines. I can’t get any Win7 machines to show up as relevant to this baseline. All the individual components, if applicable to a Win7 machine are showing the appropriate computers as relevant, but I just can’t get the baseline to show as relevant to Win7. I even tried changing the baseline relevance to nothing but “true” and still – Win7 machines aren’t showing as relevant. Am I missing something here? Can someone provide some insight on what I need to look for or any tricks to make this baseline relevant to Win7 machines? Any help is much appreciated.

(imported comment written by mholder91)

I think I may have already found the issue. The first component was the .NET install, which was a non-custom, direct from BigFix component. It looks like by default, the checkbox for “Baseline will be relevant on applicable computers where this component is relevant” was checked. I unchecked the box and it looks like Win7 machines are starting to report. It looks like I fixed my own issue, but thanks for reading! :slight_smile: