System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Add grace period to delay detection method for installers that exit too quickly

Many application installers spawn child processed and then exit before actually finishing, causing Detection Method to fail. The solution widely used right now is to wrap the installer in a script and use some kind of "sleep" function. It would useful to have an optional parameter on the "detection method" tab to delay the detection check for up to 'x' seconds/minutes after the installer exits.

Note: we can sort of do this now by forcing a reboot after the installer exits; the computer will restart and run detection check afterwards, but this just leads to a lot of longer installs and unnecessary reboots.

28 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Edward Grimaudo shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Vladimir Zelenov commented  ·   ·  Flag as inappropriate

    I don't have voices yet but I agree to have in detection types an option as delay between install/uninstall actions and detection.

  • Martin Arserius commented  ·   ·  Flag as inappropriate

    Same, having problems with installation/uninstallation failures due to evaluation is run to quickly.
    Solutions now are scripts that delay the end of installation witch is a uggly solution :)

Feedback and Knowledge Base