Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Create a 'fake' update for update scan/path troubleshooting

Create a 'fake' but officially signed MS update that is applicable to all OSes and fails with a predictable error code, to help with software update scan troubleshooting issues. This will let us see if our software update scan is actually working, and if the entire path all the way down to the machine is functional or not.

6 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Hunterkll shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Hunterkll commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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 commented  ·   ·  Flag as inappropriate

        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