Check out the new ADR filter in Technical Preview 1908
I was thinking about this one a bit more since it got marked at noted today and I have a stretch goal of sorts. As described this would be a global Yes/No: the update is either deployed or not. If you have multiple ADRs this could be problematic. When more than one ADR selects a particular update then only the first ADR would win since it would be marked as deployed for subsequent ADRs.
The solution I think is to make the logic specific to the ADR deployments. Which is is to say "Is this update deployed to the collections targeted by this ADR". That's a lot more complex than just a global check but I think users will run into issues without it.
@Charles: You're not wrong but keep in mind that options 2-4 are out of the ConfigMgr team's hands. So the only thing in their control is #1 which I've been told they are looking into.
I can't find this stated anywhere but I heard from the product team that the new Unified Update Platform will implement #2: Make the SSU and CU on patch. But that's not going to help for a long time.
It's worth noting that the behavior indicated by the actual UVI (install SSU before CU if both appear) would be great from a steady-state perspective. This month we're just all a tizzy because MS made them pre-reqs again which hasn't been the norm. So we really need both.
Yes please! This just bit me.