Troubleshooting tips for application deployments
Applies to: Configuration Manager (current branch)
Typical problems with application deployments fall into one of the following categories:
Application download failures
Application deployment compliance stuck at 0%
If you experience either of these issues, this article provides some steps you can use to troubleshoot. For more in-depth troubleshooting, see Troubleshooting application deployment technical reference.
Application download failures include the following problems:
The client is stuck downloading an application
The client fails to download the application content
The client gets stuck at 0% while downloading the application
The first thing to check when you experience application download failures is for missing or misconfigured boundaries and boundary groups. For example, if the client is on the intranet and not configured for internet-only client management, its network location must be in a configured boundary. There must also be a boundary group assigned to this boundary for the client to download content. For more information, see Define site boundaries and boundary groups.
If you can't configure a boundary for a client, or if a specific boundary group can't be a member of another boundary group:
In the Configuration Manager console, open the properties of the Deployment Type.
Switch to the Content tab.
In the section for using a distribution point from a neighbor boundary group or the default site boundary group, change the Deployment options to Download content from distribution point and run locally. (By default this setting is Do not download content.)
If the client can't download the application content, make sure it's distributed to a distribution point. To verify this configuration, use the in-console features to monitor content distribution to the distribution points. For more information, see Monitor content you have distributed.
Compliance stuck at 0%
When the application's deployment compliance is 0%, check the deployment status for the application in the Monitoring workspace under the Deployments node.
In Progress: The client could be stuck downloading content
Error: For more information on how to troubleshoot this problem, see the following blog post: Tips and Tricks: How to Take Action on Assets That Report a Failed Deployment
Unknown: This status usually means that the client hasn't received policy. Manually refresh client policy to see if the client receives it. For more information, see Initiate policy retrieval for a Configuration Manager client.
If these actions don't resolve the issue, check the client status. There may be a deeper underlying problem with the client. For more information, see How to monitor clients.