(imported topic written by SystemAdmin)
I wrote these two session relevance queries and figured they might come in handy. (I find it interesting that when I initially looked into these issues I thought the resulting relevance might be quite long and awkward, but in fact they are fairly straightforward.)
Now, I know there are a few other threads in regards to these issuse dotted around, but I figured it would be helpful (just for myself, if not anyone else) to have them listed here for future use. (If these problems have already been solved elsewhere, then apologies for the redundancy and wasting two minutes of your valuable surfing time.)
The first check creates a list of fixlets in baselines and then compares the source fixlet name against the current name. In the majority of cases (from what Iâve seen), the name of the fixlet changes in some form when it gets updated, such as being applicable to both SP1/SP2 but then a later patch makes the SP2 portion unecessary. The other common change is when a patch is no longer needed and the name is appended with (Superseded).
If you wanted to have even better coverage, you could compare the relevance and/or action as well, to ensure youâd be notified for any reason that you might want to update your baseline.
Note: You will probably need to modify the filter piece in the relevance to ensure you block any test (or known duplicate/out of sync) baselines.
-
- Fixlets in Baselines that are out of sync - -
unique values of (item 0 of it) of (name of it, name of source fixlet of it) of it whose (name of source fixlet of it != name of it) of (components of component groups of bes fixlets whose (baseline flag of it AND name of it starts with âBase OS patchesâ))
Now, I can imagine that a comment will spring to mind almost immediately for some of you, in that youâd like to know what Baseline they are in. I may come up with that one later, but if someone else wants to do that, thatâs fine. (Something along the lines of what Iâm doing below might point you in the right direction.)
The next statement handles checking for fixlets that have been used in more than once, either in the same or different baselines. This doesnât happen too often, but itâs nice to be aware of it. Obviously, if you use duplicate fixlets on purpose (to manage the actions of a baseline), then you will want to filter the names of those out. Or make your filter more specific to which fixlets you want to look for.
-
- Duplicate fixlets in Baselines - -
unique values of (item 1 of it &" - "& name of item 2 of it) of it whose(item 0 of it contains item 1 of it) of (( set of ((item 0 of it) of it whose (item 1 of it > 1) of (it, multiplicity of it) of unique values of (names of (components of component groups of bes fixlets whose (baseline flag of it AND name of it starts with âBase OS patchesâ)))) ), names of components of component groups of it,it) of (bes fixlets whose (baseline flag of it AND name of it starts with âBase OS patchesâ))
I hope you find this useful.
-Jim