Scripts are very commonly used to “wrap” vendor installation packages and perform additional tasks to achieve a comprehensive desired installation result. For example, script code can perform preparation tasks before running the vendor installation, as well as post-installation tasks. There are hundreds of possible reasons for using scripts to assist with the automation of a deployment through Configuration Manager.
Weblog of David Stein
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. [...]
This is admittedly a particularly small sub-category within Client Advertisement problems. However, it does occur and it can be very confusing to administrators, even though many times it’s not serious or catastrophic. Note: If the Advertisement refers to a Package which runs a script to perform actions, refer to my article "Part 13: Advertisement Issues Involving Packages that use Scripts".
This is probably the most common type of problem for any Configuration Manager Site admin to wrestle with. For some reason, clients just stop running Advertisements for Application and Update installations. This is not about Advertisements which report “Succeeded” (yet don’t install), or “Failed”. This is really about those which show “No Status”, “Accepted” or “Waiting”, yet never seem to get moving.
Configuration Manager 2007 R3 introduced new Power Management features for gaining greater control over device power consumption. While Group Policy provides a fairly robust range of power management options, the additional capabilities 2007 R3 provided add more granularity and flexibility with respect to scheduling and dynamic level control than Group Policy settings alone.