Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice - Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more

Hunterkll

My feedback

  1. 57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Ideas » Software Center  ·  Flag idea as inappropriate…  ·  Admin →
    Hunterkll supported this idea  · 
    An error occurred while saving the comment
    Hunterkll commented  · 

    I too also still have this problem.

  2. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Hunterkll commented  · 

    It doesn't need to fail, but failure would create noisier logs. maybe both a working and succeding one, and the succeding one leaves a flag somewhere, but still reappears each scan as required?

    An error occurred while saving the comment
    Hunterkll commented  · 

    I would imagine such an update would have to be released in a super special seckrit squirrel category of the WU catalog that only comes through WSUS to really test the entire path .... perhaps put it in the 'Windows 2000' category? :)

    Hunterkll shared this idea  · 
    An error occurred while saving the comment
    Hunterkll commented  · 

    It can succeed too, but it should always re-appear on scan. So maybe a dummy install that just returns success when executed but doesn't register as an installed update?

    The key component here is that I want it to *always* be detected if it's deployed against a machine.

Feedback and Knowledge Base