It would be really helpful if you could describe a pipleine in Update Management, and get the updates to flow through that pipeline.
e.g. You have a Dev, Test and Production Environment.
You want to keep machines up to date, but do not want to affect Production users with faulty pathes.
If you could describe an update pipleine, saying, deploy any updates to Dev, then to test then to prod, this would ensure updates can be developed and tested against before they reach production.
When patch tuesday arrives, these patches would be available for your 1st environment in the pipleine, and wouldn't be available to the second until they had passed the 1st. (And so on down the pipeline..)
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
Mark Nash commented
The idea would be that you define the pipeline as : (Dev) -> (Test) -> (Prod)
There are 3 available patches at start of Monday
Dev gets patched with all 3 successfully
2 new patches are released on patch Tuesday
Test deploys Dev's 3 successful patches but then fails 1
Prod deploys Test's 2 successful patches
Dev gets the 2 new patches deployed, and successfully completes both
No new patches released
Test successfully installs the 2 new patches and the patch it previously failed
Prod patches with the 3 patches that succeded on Test