Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

Hunterkll

My feedback

  1. 22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Ideas » Software Center  ·  Flag idea as inappropriate…  ·  Admin →
    Hunterkll supported this idea  · 
    Hunterkll commented  · 

    I too also still have this problem.

  2. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    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?

    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  · 
    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