Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

Anonymous

My feedback

  1. 26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Software Center  ·  Flag idea as inappropriate…  ·  Admin →
  2. 131 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  12 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    Further to this, if the apps are part of a dependency it gives some very counterintuitive results.

    If App B has a dependency on App A, and App A has a powershell detection criteria that must be run with privilege (e.g. Get-WindowsOptionalFeature which can't be done as a user) then:

    If you deploy app A to a user collection, it will fail with "software not applicable to this device"
    if you deploy app A to a machine collection, it will work
    If you deploy app B with the dependency of app A to a user collection, it will evaluate app A detection as the user and fail with "software not applicable to this device". This is true even if app A is already on the machine and correctly detected via a machine deployment.

    In this situation, you must also deploy app B to a machine collection.

  3. 45 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 →
    An error occurred while saving the comment
    Anonymous commented  · 

    This is even more of an issue because every time a new update is reissued (has happened twice with 1809 now), the new update has the default of 60 minutes timeout set again. So we constantly have to keep an eye on the new releases of the same feature updates and increase the timeouts manually on each one.

    With more of the install moving into the pre and post reboot phases, 60 minutes is far, far to short, even on very fast hardware and SSD.

    Anonymous supported this idea  · 
  4. 834 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  31 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base