As we all know, the majority of headaches which occur while managing SCCM involve problems on the client side and rarely have much to do with SCCM itself. Inevitably, many help desk personnel assume that since whatever it was occurred during an SCCM deployment, it MUST be an SCCM problem. I will be spending some time, dedicating posts to problems which occur because of client-side problems, but are typically reported as SCCM issues.
On occasion, an advertisment will fail to install on the client workstation. The example I give here results in recording a warning in the Windows Application Event Log of type Event ID: 1015. (seen below)
This occurred both on a regular advertisement and on a security update deployment. Within the execmgr.log, the regular application advertisement registered the following error:
Failed to advertise product, error code 1601 execmgr 8/28/2009 8:00:33 PM 2980 (0x0BA4)
Lowright users might fail to install this application if it requires higher privileges execmgr 8/28/2009 8:00:33 PM 2980 (0x0BA4)
For the security updates, the following errors were registered. (log files posted above each error)
WUAHandler.log
Installation job encountered some failures. Error = 0x80240022. WUAHandler 9/9/2009 8:29:16 AM 2792 (0x0AE8)
UpdatesHandler.log
Update execution failed. UpdatesHandler 9/9/2009 8:43:26 AM 2364 (0x093C)
The resolution for both of these problems was to perform a WMI repair and reboot. We've done this across multiple machines having the same issue and it works with or without a reboot, but we like to practice rebooting after such practices. Hopefully, this can help others who may be experiencing the same issues.
As always, I welcome alternative solutions to be posted as comments here. Thanks!