False relevance on Superseded patches

D.Dean 2023-10-31 16:00:22 UTC #1

When did HCL move away from adding a false relevance to superseded patches?

I have moved away from day to day patching but my team pointed this out to me today.

I am not sure about others but I would prefer the false relevance and if I need to deploy something that is superseded, make a copy of it.

JasonWalker 2023-10-31 16:24:36 UTC #2

Can you give an example?

I think generally we do put a False on superseded Fixlets but I think there is an edge case that challenges the rules recently.

I think the approach has been that a Security Update fixlet would not be superseded by a Non-Security update - as some customers want to apply only the security updates and don’t care to deploy bug-fix or feature updates; but I think I heard about some recent complications on that approach so I want to check whether this is the same issue before diving in to the details

orbiton 2023-10-31 17:51:55 UTC #3

@D.Dean from 2017 - Supersedence handling change for Windows Patches

D.Dean 2023-10-31 18:10:55 UTC #4

Completely missed that. If I had actually looked at the relevance of patches I would have noticed.
Thanks for the help.

Jeff 2023-10-31 21:08:24 UTC #5

I believe the setting is also added to the fixlets in Updates for Windows Applications now.
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0107658