I'm seeing "absent mindedness" for the CM client on some (but not all) computers for some application deployments, and on other computers for different application deployments.
I'm using this very informative blog post to follow the install process via logs and when I dig into the logs on a specific machine that is failing the deployment, I regularly see the CM client just drop it. It's like the SCCM equivalent of going into the other room to and then forgetting what you went in there for. For example, the last machine I looked into the logs, I saw:
- AppDiscovery.log: The application is not installed and should be.
- CAS.log: The content needs to be downloaded
- ContentTransferManager.log: The content is downloaded
- CAS.log: The content was successfully downloaded (and I can see the installer files in the ccmcache folder identified in the logs).
- AppEnforce.log: No log entries for +/- 5 days(!) around the time of discovery and content download.
The AppEnforce.log is supposed to tell me how the install progressed. It's not the logging that failed; there is no record of a log from the installer's own logging process either. Simply put, the installation was never attempted. The SCCM client just dropped the process.
As always, this deployment type works fine for many workstations. There are no Requirements. There is one dependency that is common (and already installed) for other, working deployments on this particular machine.
I've seen a very similar problem on other machines with other deployments. They don't always drop the process in the same place. I recently looked at 3 machines (of 150) reporting errors on another application package. 2 (of 3) found that the application was not installed and that it should be, and then never attempted download the content.
How do I track down what is happening to make SCCM "forget" what it is supposed to be doing? This inconsistency is maddening!
Thanks.