Hello everyone,

Over the course of the last couple of months we have been able to identify some typical problems that you might see when you deploy applications in ConfigMgr 2012. If you experience any of the following problems, check these recommended troubleshooting steps and information.

Problem 1 – application download failures:

• Client stuck downloading an application
• Client failed to download application
• Client stuck at 0% while downloading software

Possible solutions and troubleshooting information:

1)      Missing or misconfigured boundaries and boundary groups:

If the client is on the intranet and is not configured for Internet-only client management, the client’s network location must be in a configured boundary and there must be a boundary group assigned to this boundary for the client to be able to download content. For more information about boundaries and boundary group, see the following TechNet information:

Planning for Boundaries and Boundary Groups: http://technet.microsoft.com/en-us/library/gg712679.aspx
Configuring Boundaries and Boundary Groups: http://technet.microsoft.com/en-us/library/hh427326.aspx

2)      Content might not be distributed to the distribution points yet, which is why it is not available for clients to download. Use the in-console monitoring facilities to monitor content distribution to the distribution points. For more information about monitoring content, see the following blog post: http://blogs.technet.com/b/inside_osd/archive/2011/04/06/configuration-manager-2012-content-monitoring-and-validation.aspx

3)      If you cannot configure a boundary for the client or if specific boundary groups cannot be a member of other boundary groups, you can configure the Deployment Type properties, Content tab, Deployment options for the option “Download content from distribution point and run locally”.

Problem 2 - application deployment compliance stuck at 0%

Possible solution and troubleshooting information:

1)      When compliance is 0%, check for the following deployment status for the application in the Monitoring workspace, Deployments node:

• “In progress”: The client could be stuck downloading content. Check problem 1, above.
• “Error”:  For more information about this status, see the following blog post: http://blogs.technet.com/b/configmgrteam/archive/2012/03/23/tips-and-tricks-how-to-take-action-on-assets-that-report-a-failed-deployment-in-system-center-2012-configuration-manager.aspx
• “Unknown”: This implies that the client has not received policy. Try manually initiating client policy and if this does not work, use client status to help verify client functionality.  For more information, see the following TechNet information: Initiate Policy Retrieval for a Configuration Manager Client: http://technet.microsoft.com/en-us/library/gg712288.aspx#BKMK_PolicyRetrieval Monitoring the Status of Client Computers in Configuration Manager: http://technet.microsoft.com/en-us/library/gg682132.aspx#BKMK_ClientHealth