Update Management
Please take a few minutes to submit your idea or vote up an existing idea. All of the feedback you share in these forums will be monitored and reviewed by the Update Management engineering team.
-
Identify which server update failed.
From the Automation Account, the job did not id which servers failed.
3 votesAre you using the OMS portal or the Azure portal? This information should be present in the Azure Portal under Update Deployments. You can click a deployment and it should let you know what machines specifically failed.
-
cant remove.
can not get rid of the Upgrade Analytics Preview....
Ive clocked remove like 100000 times.
3 votes -
Provide ability to set a specific reboot sequence order
I have a cutomers who wants a few specific servers to reboot before the next few.
I could opportunistically put these in different schedules with maybe 30mins diff, but there is no guarantee that the first schedule is done before the other one is done and suddenly they reboot in the wrong order.Could we have this ability?
In ansible I use the serial option so everything is done serially, but it would be nice if update management could handle the reboots serially at least (And check for heart beat after reboot before continuing).2 votes -
Update Management has no locking mechanism
Hi,
during testing I scheduled two deployments for the same server at the same time. It seems there is no locking mechanism (EL7 linux deployment) that takes care of this. I don't think having two updates run on the same server at the same time is a really good idea :)From ps output it seems that yum locking is saving the system from getting harmed by this, but this is something that I would update management to catch.
Greetings
Klaas2 votes -
"Security Intelligence Update for Windows Defender Antivirus" listed as "Other" instead of "Security"
"Security Intelligence Update for Windows Defender Antivirus" listed as "Other" instead of "Security"
2 votes -
Export option (list) for all
Create an option to export all server in Azure Update Management as a list.
2 votes -
Add the ability to global exclude patches
Currently, the only way to exclude a patch is to exclude it on each patching schedule. Please add a way to globally exclude patches to reduce the need to change every schedule.
2 votes -
Add ability to create a new schedule and configuration (New-AzAutomationSoftwareUpdateConfiguration) using an existing computer group query.
I already have pre-existing computer groups (Azure and Non-Azure Machines) created and can manually create update scheduled in the portal to use group queries. However, I cannot do the same via the powershell New-AzAutomationSoftwareUpdateConfiguration cmdlet.
Add ability to create a new schedule and configuration (New-AzAutomationSoftwareUpdateConfiguration) using an existing computer group query.
Also, feel free to reach out to me directly.
2 votes -
billing account between money all to Mastercard 5126241000409977 card between to automait transfer changr update send
update save to Mastercard 5126241000409977 card to automait tranfer change send
2 votes -
SCCM vs Update Management
Would like to understand feature difference between SCCM and update management.
2 votes -
Ability to install updates in parallel instead of sequential
Right now Update Management uses the WUA agent to kick off installs of updates, and I understand that can only to this sequentially per update. I would be great to leverage the SCCM agent (when possible) to kick off patching in parallel (it is possible), otherwise it will take forever to just get a few updates installed and my MW's arent long enough.
2 votesThanks 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.
-
Patching Report issue.
Ability to get patching reports. Filter servers by TAG and export patching report to csv, pdf, etc.. In other word, fast way to get patching report for Organization management.
2 votesThanks 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
-
Menu/Option to offboard VM's
Removing a VM from Update Mgmt requires going to the attached Log Analytics workspace and manually removing the VMUUID from the "MicrosoftDefaultComputerGroup" saved search.
A cleaner way to achieve this would be ideal for customers with large IaaS environments.2 votesThanks 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.
-
2 votes
-
Update Management - Inject Patch Inclusions or Exclusions automatically during pre-script
In Azure Update Management, we are able to cancel a scheduled Update Deployment with a pre-script (in our case, I'd like to do that if the patches have not yet been verified to impact the software prodcut running on the machine). I would also love to be able to 'inject', in the pre-script, one or more KB ID's that must be in- or excluded from the Update Deployment.
2 votesThanks 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.
-
2 votes
thanks for bringing this to our attention. Checking internally to see if this is currently on the roadmap. In the meantime, your feedback is now open to the community to upvote which helps us prioritize this request against our existing feature backlog.
Cheers.
-
Remove restrictions of maintenance window for update deployment job
Currently, the maintenace window can't be less than 30 minutes and no more that 6 hours. Some customers would like to set the window more longer since they wonder that some update programs coundn't be deployed during the windw. It would be nice if you could remove this restriction.
2 votesThanks 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.
-
Support boolean parameters in pre/post scripts
A runbook with boolean parameters cannot be set as a pre or post script in a scheduled update deployment. The UI when configuring the script has a dropdown to specify the value, but it is passed as a string ("True", "False", or ""). Ideally, it should be possible to pass these values, but failing that the UI should not present a dropdown that implies it should work.
2 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote which 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.
-
Optimizer to automatically generate deployments
Provide a simple means to provide:
1. Maintenance Window
2. Dependency rules / chains (i.e. 48 hours after system in dynamic group named test, then perform deploy to group named production)
3. Rolling updates for clustered applications
4. Validation post-patching (could be as simple as the update agent has reported post-reboot initially) and then halt deployment of related-nodes (if it is defined as part of a cluster)Then allow for update manager to create deployments automatically by feeding this information into an optimizer.
2 votesThanks 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.
-
Options to ignore de-allocated machines while using "Dynamic Groups" feature
We selected a few "Resource Groups" to update the VM's during the schedule using dynamic groups but if any of the VM is in a de-allocated state that will be obviously failed while deployment, I feel if we have an option to "Ignore De-Allocated" machines it would be great.
This helps to see less failed deployments since we know our VM's are de-allocated. (If any)
2 votes
- Don't see your idea?