Most of this content also applies to Microsoft Configuration Manager, current branch.
Problems that affect application deployment typically fall into one of two categories: Application download failures and application deployment compliance sticking at 0 percent. If you encounter these problems, you can try the following troubleshooting methods.
Application download failures
Application download failures includes the following problems:
- The client fails to start downloading an application.
- The client gets stuck at some point during an application download.
If you experience an application download failure, the first thing to check is missing or misconfigured boundaries and boundary groups. For example, 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 that is 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 topics:
If you cannot configure a boundary for a client, or if a specific boundary group cannot be a member of another boundary group, go to the Deployment Type properties, click the Content tab, enable Download content from distribution point under Deployment options, and then run the process locally.
Another possible problem is that the content is not yet distributed to the distribution points and is not available for the client to download. To verify this, use the in-console monitoring facilities to monitor content distribution to the distribution points.
For more information about monitoring content, see the following Configuration Manager OSD Blog article:
Application deployment compliance is stuck at 0 percent
If compliance shows as 0 percent, check the deployment status for the application in the Monitoring workspace under the Deployments node. Follow these guidelines:
- If the deployment status is In Progress, the client could be stuck while downloading content. See the previous section regarding application download failures.
- If the deployment status is Error, see the following article for more information about how to troubleshoot the problem:
Monitor applications from the System Center Configuration Manager console
- If the deployment status is Unknown, this usually means that the client has not received policy. Try to manually initiate client policy to check whether the client now receives policy.
For more information about this problem, see the "Initiate Policy Retrieval for a Configuration Manager Client" section of the following Microsoft Docs article:
How to Manage Clients in Configuration Manager
If this method does not resolve the problem, check the client status for help to determine the cause of the problem. For more information, see the "Monitoring the Status of Client Computers in Configuration Manager" section of the following Microsoft Docs article: