Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

Max

My feedback

  1. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  Ideas » Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
  2. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
    Max shared this idea  · 
  3. 52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    Max commented  · 

    I also think that this is an important feature that is missing today. Let's say we want to run an ADR and then deploy the created SUG to different rings of servers, like wave #1=Dev, wave #2=Pilot, wave #3=Infra, wave #4=Prod, etc..

    Currently the deployment properties in ADR only allow to set deadlines to specific offsets of hours/days since ADR completion time. This allows us to deploy the SUG to different rings in concrete intervals of time between the rings, but not on concrete dates or days.

    It would be useful if ADR properties would allow to automatically create deployment schedule times like "2-nd Sunday after ADR has run", or like "the 20-th day of the month after ADR has run" and so on and allow different types of schedule in single ADR. Currently it is not possible to achieve this mode of operation because some months are shorter then others.

    Max supported this idea  · 
  4. 35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    Max supported this idea  · 
  5. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    Max supported this idea  · 
  6. 39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    Max supported this idea  · 
  7. 1,486 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  31 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    Max commented  · 

    This is the most important/missing feature today. This is right not only for servicing stack updates but also for regular updates. Currently there is no simple/builtin way to get (some) systems fully patched using a single deployment schedule within a single window, if some updates fail during the deployment, or if some updates cause WU client to detect new updates in next scan cycle.

    The problem is that a deployment may show as compliant, let's say in the morning after patching, but later it the same deployment shows as non-compliant. This is because the re-scan or re-evaluation cycle occurs after the maintenance window ends. According to the documentation the interval between 2 scan cycles or 2 deployment re-evaluations cycles cannot be set to less than 1 day. The documentation states that if the interval is set to less than 1 day it is reset automatically to 1 day.

    There a lot of workarounds to get deployment re-scheduled again or creating multiple deployments or multiple cycles, but this get complicated and causes a an administrative overhead, instead of packing multiple cycles into a single step.

    Max supported this idea  · 

Feedback and Knowledge Base