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.
-
"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"
3 votes -
SCCM vs Update Management
Would like to understand feature difference between SCCM and update management.
3 votes -
Enable Update approval
It would be great to have a option to approve / decline updates directly in the Update Management UI
3 votes -
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.
3 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.3 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.
-
How do I stop "in progress" Update Deployment?
It's in progress for about 4 days now. The maintenance window was 30 minutes. Can see this is an ongoing issue too. Will it ever be fixed?
3 votes -
3 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.
-
Dynamic Update Deployments on premises
The Dynamic Update Deployments feature which is in preview is only able to respect Azure systems. As hybrid is the new normal, this needs to be extended to a hybrid approach. It makes no sense to offer saved searches and dynamic groups which are not respecting changes in those groups. Today deployments will fail if any changes occours in the groups with the focus on on premises machines.
3 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.
-
Show number/details of Successful updates deployed
The current update management screen for the summary of a previous update deployment only shows Failed/Not Attempted/Not Selected against the list of updates that were installed during the window.
For reporting purposes it would be useful to have another column 'Successful' which would show the amount of times the update was installed.
3 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.
-
Ability to refresh the 'Update Management' blade.
I cannot be sure that the window I'm looking at is up-to-date. A refresh button would give me confidence in this.
3 votes -
Ability to deploy Preview updates
There should be an option to install Preview updates, such as KB4338831 (July 18, 2018 Preview of Monthly Rollup) which fixes critical issues in KB4338815 (the regular July 2018 Monthly Rollup).
Right now (end of July 2018), after we update our machines using Update Management, we still need to install KB4338831 manually on each machine to keep important network services from locking up.
3 votes -
Do an immediate refresh of compliance data after update deployment (linux)
After a deployment/update job, the data for the compliance dashboard should be immediately updated - not have to wait for the next scheduled compliance check
3 votes -
Schedule immediate compliance refresh function
I'd like to be able to schedule a refresh of compliance data (outstanding patches) whenever the next heartbeat occurs. Unless I'm missing something, the data can be somewhat stale and offers no easy way of getting it updated in a more timely fashion.
3 votes -
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 -
2nd Tuesday as target while scheduling patching jobs in update management
Hi team,
Can we get feature of scheduling patching job while targeting 2nd Tuesday. like patch these servers should patched on 2nd tuesday+2 days.
by this way we will not need to change automated scripts/patch jobs when 2nd Tuesday occurs after 2nd Friday such as Jan 2019.
Thanks,
Rakesh2 votes -
Schedule updates relative to Patch Tuesday (0-30 days)
Provide the ability to schedule updates offset on days since Patch Tuesday. Add Patch Tuesday as a starting date in the scheduler and allow admins the ability to choose from 0 to 30 days from Patch Tuesday
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 -
Speed up enterprise linux (rhel/centos) updates
Hi,
currently you're applying individual updates alphabetically (or so it seems from watching ps)
/usr/bin/python /bin/yum -y install elfutils-libelf-0.176-4.el7.x8664
/usr/bin/python /bin/yum install --assumeno elfutils-libs.x8664
[,..]This creates overhead within linux that is usually not needed. You have two options in update management for linux: apply all or apply security updates.
Both have a yum command:
Update all packages: yum update
Update all security relevant updates: yum --security updateThis will reduce overhead and should apply packages faster.
I didn't find the code, so I am not sure why you use different switches for yum, my guess would be…
2 votes -
Show all VMs, even if they are powered off
Need to be able to see VMs that aren't running everyday. It should still show the status from the last time it reported. This is common when you have lab or other non-prod machines that are running every day.
2 votes
- Don't see your idea?