This is a bit of a strange one. We have two applications we will call them App1 and App2. We have a bunch of clients that are sitting in a departmental collection all of these clients have app1 installed from a previous deployment solution. App1 has never been deployed from SCCM 2012 to these machines or any machines for that matter.
App2 is a dependency for App1. Now this dependency was never installed with the previous deployment of App1 so none of the machines in the departmental collection have it, its no big deal it the software will still partially function. The only deployment to the departmental collection on SCCM 2012 is a Operating System Deployment Task Sequence. In this task sequence we have included a section that installs App1 (and therefore the App2 dependency too). What we noticed was that machines that were in this collection started installing App2. We saw this in the AppIntentEval.Log file at the following sections.
<![LOG[ScopeId_405997B8-D50C-429C-84D6-012DDAF9BDB5/DeploymentType_fe3a2cc0-eb26-47fb-a9a8-356d8a635ae4/2 :- Title = App1 - Windows Installer (*.msi file), Direct seleted dependencies = ScopeId_405997B8-D50C-429C-84D6-012DDAF9BDB5/DeploymentType_125b11d5-9e46-4a88-8c13-ed1c6314672a/1 title=App2, ]LOG]!><time="10:46:44.414+00" date="01-19-2015" component="AppIntentEval" context="" type="1" thread="48836" file="appconstructs.cpp:2696">
I removed the task sequence deployment to this departmental collection. Added a test machine to the collection and manually installed App1 on the test machine. I did a machine policy retrieval and application evaluation refresh and waited. App2 did not install. I then re-advertised the OSD task sequence as available to media and pxe. Machine policy retrieval and application evaluation refresh and hey presto App2 is detected as a dependency in much the same way as the above log segment shows and installs (clear in AppEnforce.log).
Is this a bug in SCCM? Should software in an OSD task sequence be flagged as required even though these OSD task sequences are sometimes deployed as available to boot media and pxe to collections where the task sequence has never ran but where in some cases the software in the task sequence may be partially compliant on said clients? Since when did the task sequence dictate what happened outside of its self? This has caused us a little bit of a problem here as the App2 dependency package we missed off /norestart. Be careful guys!