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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Sort Order and Filter

    Need the ability to sort the list of computers alphabetically when adding to a scheduled deployment. The current list is random and makes it really hard to select specific machines. Also, having a filter options would be nice when the list is very long.

    7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Wrong values in System Update Assessment solution dashboard

    System Update Assessment solution dashboard is displaying wrong values.
    If i try to make a query directly in search it returns the right values

    7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    The circled field is number of computers missing any critical updates, e.g. there are six computers which haven’t been patched.
    The underlined fields are the numbers of patches missing on those computers. So computer one is missing a total of 47 critical patches, computer two is missing a total of 9 critical patches, etc.

    Leaving this as “needs feedback” until we can confirm it’s by design.

  3. System Update Assessment and SCCM upto date

    I understand that OMS SUA will display a computer being upto date if managed via SCCM and all approved updates in SCCM are installed. This is great for compliance to approved update. What also is needed is to know what updates that are not approved via SCCM, yet are available to be installed for this server. This is how it used to report when using the old system update advisor management pack that you imported into SCOM

    7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add a export option in the Update Management view

    It would be nice to be able to export the list that you have filtered out in the Update Management view. As it is right now, you can't take the information to another step.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Assessments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Systems that get an error when scanning via WSUS should be reported as 'not assessed' instead of 'compliant' if scan fails for x days

    When the app pool for a WSUS server is stopped or not running, and a client computer scans against it, it fails with an error. This error does not get surfaced in the AUM dashboard. Systems experiencing this error are listed as 'compliant', they should be listed as 'not assessed'.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Assessments  ·  Flag idea as inappropriate…  ·  Admin →
  6. retry option for failed server

    when a deployment fails because of one or few servers failed,, please provide an option to retry them later again. We can fix the underlying issue with the servers (like connectivity, server hang, access etc) first and then patch those individual servers to make the report success.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    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.

  7. export

    Every report that is run on AZURE portal should have an EXPORT function.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  8. Update Management Cli

    Update Management needs to be added to Azure Cli and Powershell Modules.
    This way new Azure and Non-Azure can be added automatically and updates managed. Also in order to export reports in various formats.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  9. Update of on premises Hyper-V and or S2D Cluster

    An Hyper-V / S2D Cluster needs an tailored mechanism for patching. Otherwise you will disrupt your on premises workload with a scheduled update management deployment.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Reboot notification to end users

    Add a customized time for notifications of pending reboots if a reboot is needed after patches is done if a user is detected logged onto a server.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  11. All fail when 1 doesn't aplpy

    I had a full deployment failure because "You have requested to create an update configuration on a machine that is not registered for Update Management." The one mentioned in the error was connected to update management and showed in the OMS logs. I'll contact support, BUT....

    It would make more sense if the deployment would work for everything that it can and just fail on those 1 or 2 that it cannot apply on. None of the deployment happened because of this 1 failure.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  12. It is nice to have option to export list of servers which are scheduled for update management

    After scheduling update management, there is no way we can export list of servers that are part of the update management. While we create groups ahead of scheduling patching but at the time of creating the schedule, there is no way to compare that with the groups created.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Scheduling  ·  Flag idea as inappropriate…  ·  Admin →
  13. disable schedule updates

    There needs to be an option to temporarily disable a scheduled deployment and/or the ability to disable a computer from participating in the next scheduled update.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Scheduling  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow enabling of Update Management (Preview) when OMS is already enabled

    Error message when attempting to enable Update Management (Preview) when OMS is already onfigured:
    {"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "DeploymentFailed",\r\n "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",\r\n "details": [\r\n {\r\n "code": "BadRequest",\r\n "message": "{\r\n \"error\": {\r\n \"code\": \"BadRequest\",\r\n \"message\": \"Multiple VMExtensions per handler not supported for OS type 'Windows'. VMExtension 'MMAExtension' with handler…

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  15. System Update Assessment looks for Manual windows update setting

    The query in the Common Update Queries section labelled "Critical or security updates needed by machines where updates are manually applied" queries machines where Type=UpdateSummary and WindowsUpdateSetting=Manual. The problem is, I dont see any windows machines where WindowsUpdateSetting is Manual. I see Scheduled installation, Notify before installation, Notify before download and Disabled. Where can you configure a windows server to Manual?

    And just wondering if this could be modifed as I'd consider the servers set to Notify are "manual"

    Maybe this?
    Type=Update OSType!=Linux UpdateState=Needed Optional=false (Classification="Security Updates" OR Classification="Critical Updates") Computer IN {Type=UpdateSummary WindowsUpdateSetting=Notify | Distinct Computer}

    Thanks

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  16. Ability to run scripts throughout patching

    We can run pre/post scripts, but that is not useful when patching a web farm, cluster, or complex application that needs careful handling. It would be great to have the ability to run scripts throughout patching; pre patching a node, pre/post reboot, post patching a node... this way I can start/restart services, validate functionality after patching a node, or even manage cluster nodes myself throughout a patch cycle.

    With pre/post scripts I cannot suspend/resume cluster nodes as I patch through them in a group, nor can I ensure my services are stopped/started as required by my app owners. There is…

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    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.

  17. Support SharePoint updates or don't attempt to apply them

    The service currently detects missing SharePoint updates and will attempt to apply them, however, this reliably fails with error code 0x80240020. This appears to be a known issue in general when installing SharePoint updates remotely, with the best practice being to install SharePoint updates manually due to the requirement to run PSConfig after installation. Further, when the updates fail, the service attempts to install the failed updates again around 40 times. These all fail, and result in a "bloated" Windows Update history of install failures.

    SharePoint updates should either be supported by this service or explicitly blacklisted so that updates…

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Azure CLI for Azure Automation

    Like to automate the Onboarding VM into Azure Automation using CLI or Terraform module while provisioning the VM ..

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Virtual machines can be in up to 3 resource groups.

    Increase the resource group limitations for Update Management.
    It's a big problem for me, because in my company we have one resource group for each Virtual Machine.
    Currently, we have 30 VMs.

    In this case, do I need to create 10 automation accounts to solve this problem?

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add ability to remove previous Update Deployments stuck in "In Progress" state

    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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Update Management

Categories

Feedback and Knowledge Base