I was going through my Baselines this morning, just to get them Sync in case any of them had components with the “Source Fixlet Differs” label.
To my sorprise ALL Components now have this label, even the really old ones (MS03, MS04, etc)… has the download location changed for all of them??
I have noticed in the past that when we have an active Baseline with “Source Fixlet Differs” in one of its components, this can cause relevant clients to have a very large CPU Usage.
We needed to change the “parent relevance” in the “Enterprise Security” Fixlet site to properly detect 64-bit Windows Vista. This causes all the 32-bit Fixlets to change slightly to add this check. Even though we made the change to the underlying Fixlet, you need to authorize the change in the baselines because the baseline version is “your version” and we can’t automatically change it. You can edit the baseline and click the “sync to source Fixlet” to use the new relevance (and then you need to re-issue the actions from the baselines if you want to use the updated baseline relevance).
This change only affects Windows Vista computers and if you don’t change your baselines, there will be a possibility that the Fixlets for Windows Vista 32-bit might accidentally run on Windows Vista 64-bit computers. This likely will not cause most customers a problem in the short term (because 64-bit Vista is not widely deployed right now), but it is a change we need to make for the long term.
This should have absolutely no effect on the CPU usage on the BES Clients. I am not sure what you saw in the past, but this is all a BES Console side change and the BES Clients don’t even care about the differences (they just evaluate whatever is in the baseline).
There should be an announcement on the BES Admin list about this in a few minutes.
A couple people already asked this question and I thought I would answer it here for everyone:
We do not have a tool that automatically re-syncs all the Baselines so you have to go through and click the sync button manually. The reason we can’t easily make a tool to do this is because the information is digitally signed in the database as a security precaution to prevent people from taking over all the computers in your company by taking over the BES database. Because of these digital signatures, it makes it hard to change things automatically directly in the database and if a tool that changed the database made a small mistake, it would probably cause your whole database to become corrupted, which is not so easy to fix.
Note that in BES 7.0, there is a button to “Re-sync all” for the Fixlets inside a baseline rather than clicking each of them.