from what information is available:
- there are no more individual patches.
- each rollup contains a number of 'fixes'
- you cannot install/uninstall the fixes individually.
- each rollup is two KBs - one for the security only, the other for security+other fixes
- each rollup is cumulative - may's rollup has all the fixes from april.
in bsa you should just see two KBs for the month - and be able to analyze for each and then deploy. if you deploy only the security path, the security+other will show as missing.
Thanks for the link Bill. I had searched but didn't come across it. Good to know. It's going to be quite the culture shift not being able to "exclude" a certain patch (from our customer end) - but good to know we shouldn't have to worry about getting the patches available for use.
You can still exclude a patch, it just means you won’t get the entire rollup ☺
And that also means you can’t apply and future rollups until whatever problem is fixed. for home users it won’t matter, but this seems like a huge issue for the enterprise environment. i’ve seen various threads on microsoft’s community voicing concerns about this and the lack of clarity around the details like skipping certain fixes, etc.
Cody I'm hoping to speak with MS rep this week to get additional details on the patching process for next month. Also, have on-going conversations with Shavlik to make sure there is no impact to our customers using BSA for windows patching. I'll update the thread once I get more info.
Bill, from the sounds of it, if you exclude patch X, the next month, patch Z will include patch X so it won't matter (so fix your incompatible apps!)