When we take a look at the typical problems with application deployment, they tend to fall into one of two categories: Application download failures and problems where application deployment compliance gets stuck at 0%. If you happen to run into either of these issues, here are some things you can try:
Application download failures
Application download failures includes problems where the client is stuck downloading an application, the client’s attempt to download the application failed, or 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 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 documentation:
If you can’t 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 and click the Content tab, then under Deployment options enable Download content from distribution point and run locally.
The other problem you may encounter with application download failures is that the content might not be distributed to the distribution points yet, which is why it 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 additional information on monitoring content please see the following:
Application deployment compliance is stuck at 0%
When compliance is 0%, check the deployment status for the application in the Monitoring workspace under the Deployments node.
- If the deployment status is In Progress, the client could be stuck downloading content. See the section above regarding application download failures.
- If the deployment status is Error, see the following article for more information on how to troubleshoot the problem:
- If the deployment status is Unknown, this usually means that the client has not received policy. Try to manually initiate client policy to see if the client now receives policy. For more information on this please see the following:
If this does not resolve the issue, check the client status for help in identifying the cause of the problem. For more information on this please see the following TechNet documentation:
J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division
System Center All Up: http://blogs.technet.com/b/systemcenter/
Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog: http://blogs.technet.com/dpm/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
System Center 2012 Configuration Manager System Center 2012 R2 Configuration Manager ConfigMgr 2012 R2