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.
agree with this one, SCCM support of exe's (main offenders for premature detection) needs more work with the main issue being detection methods for exe wrappers. Standard exe's we routinely repack to msi to simplify deployment, but when they are wrappers extracting and running other installers, the detection method is nearly always problematic with detection happening before the installations have run. As the majority of installers released by Microsoft in general are exe's of one form or another rather than msi, shouldn't exe deployment be config mgr's priority?
Vladimir Zelenov commented
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
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 :)
Jacob Pitcher commented
Would love to see this for uninstall as well.