Application Deployment stuck on "Waiting to Install"

Question

_{Thursday, May 10, 2012 6:53 PM}

Hello, I have a strange problem that sound identical to what is laid out here: http://www.windows-noob.com/forums/index.php?/topic/5524-applications-update-package-stuck-on-waiting-to-install/.

The scenario is that I created a few applications that will eventually be part of a base OS build and deployment.  I deployed those applications to a collection that I used to originally deploy Windows XP to a desktop.  The client found the application in software center and tried to install, but it hangs at "Waiting to Install."  This happened for 4 separate packages - all would show as "Waiting to Install."

I then took the same packages and deployed them to a test collection that contained the above computer that was failing, and a different Windows XP computer that we use for testing.  The packages deployed successfully to the test computer, but we experienced the same problem on the one that was originally installed from SCCM.

For what it's worth, we are setup with a standalone primary site with the distribution point installed on that same site server.  The clients have a fast connection to the site server.

None of the logs that I have checked seem to give any indication why it will not move forward.  Any thoughts on how to troubleshoot?

Thanks!

All replies (5)

_{Monday, May 14, 2012 5:12 PM ✅Answered}

Hi Torsten,

I think I solved the problem on my own.  There were 2 instance of the device listed in SCCM - one from when it was added manually prior to OS deployment and one from after.  Once we cleared out and started over, the applications deployed successfully as part of OS deployment.

Thanks for the help.

_{Thursday, May 10, 2012 7:30 PM}

What about the setup of boundaries and boundary groups? What does the Deployment state on the monitoring node tell? What's in CAS.log on the clients?

Torsten Meringer | http://www.mssccmfaq.de

_{Thursday, May 10, 2012 9:24 PM}

Just expanding on Torsten's post. This is usually a symptom of a problem getting content, either because the content is not yet on the DP or because no DPs could be returned to the client (due to a boundary issue).

If your boundaries appear to be correct, verify through the console Monitoring area that the content has been successfully deployed to DPs, and if that all looks good you can verify MP_LocationMgr.log and MP_Framework.log on the MP to verify no communication issues from the MP to the site for resolving content locations back to the client.

_{Friday, May 11, 2012 1:31 PM}

Thanks Adam and Torsten for the responses. 

The content shows as successfully distributed to the single DP we have and another machine had the software install successfully.  Boundaries are very simple with only a single site server - and both the successful and unsuccessful machine were on the same IP subnet anyways.

_{Friday, May 11, 2012 1:49 PM}

Have you added the boundary to a boundary group at all? What do CAS.log and LocationServices.log tell (you could compare both of them to get an idea why one client is failing)? What about the content setting of the deployment type?

Torsten Meringer | http://www.mssccmfaq.de