A “False Negative” in this case denotes a status result of “Failed” when all indications are that the installation (or uninstallation) was completed successfully. In most respects, this is “better” than the alternative (false positives), but can become annoying and even time-consuming to deal with, if you’re trying to maintain “clean” logs and status reports.
- How to deploy a scripted application installation with SCCM 2012 - Mon, Sep 23 2013
- How to deploy an MSI package with SCCM 2012 - Mon, Aug 19 2013
- SCCM 2007 – General client troubleshooting tips - Tue, Aug 6 2013
- Clients report “Failed” status on packages which are in fact installed properly. Many times it involves a result code of "3010".
- Clients report “Failed” status on packages which uninstall a product, when it turns out the product was not installed to begin with. This usually references result code "1605"
- Incorrect handling of exit code values within package script
- Incorrect exit codes produced by vendor installer packages
- Final step in installation process hangs, but after vital tasks have completed
- Test! Test! Test! Before going to the production environment.
- Run package (program) manually using the same account/context as used by the Configuration Manager Software Distribution agent.
The most common cause is inadequate testing. Test! Test! Test! Before going to production. Even when “some” testing has been performed, it can create problems when you test for fewer scenarios than exist in the production environment. For example, you might test with Windows XP SP3, and Windows 7 SP1, 32-bit platforms only, and then you start seeing errors on Windows Vista or Windows 7 (RTM) or Windows 7 64-bit clients. Test on every platform type that you have in the production environment!
Get familiar with Windows Installer Exit codes and what they mean. The two most common codes that frustrate and confuse administrators (in my humble opinion) are 3010 and 1605. 3010 is close to the same meaning as zero (0), which is "succeeded", except that it requires a restart (reboot) to complete the job properly. 1605 is related to using the /u (uninstall) option, and indicates that the requested product was not installed so it couldn't be uninstalled.
Subscribe to 4sysops newsletter!
- List of Log Files in Configuration Manager 2007
- Troubleshooting Configuration Manager Client Issues
- Troubleshooting Software Distribution Issues
- Configuration Manager 2007 General Supported Configurations
- Configuration Manager 2007 SP2 Supported Configurations