The possibility to "pin" a patch set for X number of days, giving you the possibility of deploying and verifying the same set of patches across individual envs. In other words: same patchset on DEV servers on Monday, Test servers on Tuesday, etc. and Production on Sunday.40 votes
We’re currently reviewing enhancements around approved and time-delayed patching.
Add the ability to rollback specific update/s40 votes
Options for supporting rollback are currently under review.
SCCM has the ability to create patch groups, which you can choose the order in which computers are patched35 votes
We’ve done some improvements around grouping, including dynamic Azure queries (tag-based) and dynamic saved searches. We’re also still investigating other higher level groupings.
I have two update deployments that are stuck in progress and won't go away. The Automation jobs finished successfully, but they still show in progress. It would be nice if there was an option to remove previous deployments. Or will these disappear with time?5 votes
We’re planning to purge stuck jobs after 30 days.
I think it would be useful to be able to configure Windows Update settings through update management, control things like automatic reboot settings, working hours, action to take if users are logged on. I believe the OMS agent could set the relevant registry keys.3 votes
Reboot control is tracked here: https://feedback.azure.com/forums/905242-update-management/suggestions/31439491-allow-suppress-reboots-as-an-option
We’re working out if that would include forced reboots or not. Same for working hours.
- Don't see your idea?