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. servers with pending reboot should not show as compliant

    Don't turn a recently patched server to compliant before the server has been rebooted (after patching). the existing implementation turns a recently patched server to compliant before it's restarted and can lead a person to forget to restart the server and leaving the patches not yet applied.

    39 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 →
  2. 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 →
  3. 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 →
  4. 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
    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. 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
    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 →
  6. Compliance report in Update Management

    There is no option to Export the data in Automation account Update Management page where we see the total count of compliant and No machines, There should be option to export detailed report which has individual servers Compliance Status as the patch deployment output is nothing to do with Compliance report.

    2 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 →
  7. Possibility to see VMs being under Update Management via policy

    Possibility to distinguish VMs which are under Update Management and incorporate the results into ARM script to work as a policy.

    Policy would help to track which VMs are left over of Update Management service.

    1 vote
    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 →
  8. Add a compliance policy for update management allowing to define acceptable delay

    As soon as patches are available, VMs are automatically displayed as non-compliant. However, it often requires review, tests, ...

    It could be great to be able to create a policy that allows to define for each kind of update what delay before applying the upgrade is acceptable or not and associate this with "shortcuts" to help to plan upgrades according to policy.

    Example - A policy states that important security updates needs to be deployed during the next 12h
    * VMS are displayed as compliant during 12h (but something indicates that they require updates)
    * A button allows to plan…

    1 vote
    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 →
  9. إعادة تحديث هاتفي بنفس مرجعية الإصدار الأصلي للهاتف المحمول حتى يتم تسهيل على المستخدم من استخدام الهاتف ويبقى دوماً معجب بمنتجات الصانع

    هاتفي يطلب مني إعادة تحديث أكثر من مرة لهذا يزعجني كثيراً الأفضل أن يبقى طريقة استخدام الهاتف المحمول بنفس الطريقة التي قدمها الوكيل عند البيع لهذا انا منزعج من التحديث الجديد الذي أصبح صعب الاستعمال

    1 vote
    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 →

    شكرا على الاقتراح الصحيح. تعليقاتك مفتوحة الآن لمجتمع المستخدمين للتصويت والتعليق عليها. يتيح لنا ذلك تحديد أولويات طلبك بفعالية مقابل تراكم الميزات الحالية لدينا ويمنحنا أيضًا نظرة ثاقبة على التأثير المحتمل لتنفيذ الميزة المقترحة

  • Don't see your idea?

Update Management

Categories

Feedback and Knowledge Base