One of the most annoying problems on the SCCM client is when several applications stuck in ‘Waiting for install…’ state for days. Sometimes the reason for that is that one application is not distributed to the Distribution Point and for some reasons in SCCM build 1710 and older it blocks entire queue and does not allow other applications to install even though they are downloaded.
Here are 3 simple steps which would allow to identify the problem.
1. Identify that at least one application cannot be downloaded. For that go to SCCM client cache folder. There should be outdated .BDRTEMP folder:
2. Go to ContentTransferManager.log Look for the suspended job. Trace the log to find the corresponding ContentID
3. GoTo AppDiscovery.log and identify the application name by ContentID
Check if that application was correctly distributed.