ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/Application_6e4c5a44-5b99-46ed-92b1-5d195a3d1108/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, ConfigureState = NotNeeded, Title = Mozilla Firefox 17.0. ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, ConfigureState = NotNeeded, Title = Mozilla Firefox 17.0.1 (x86 en-US) - Windows Installer (*.msi file) AppIntentEval 07:34:56 5068 (0x13CC) Step 18: AppIntentEval.log Evaluating and checking for Dependencies I have highlighted the deployment id of my collection and could see the initialization for download of policy.Ĭompiling policy ' ): ReportMethodInvocation :: Obtained lantern reports CIAgent 07:34:56 5068 (0x13CC) Step 1: PolicyAgent.log As an initial step, verify the policy agent log for the deployment id, you have targeted. Before you can track a deployment, you must first find the Deployment Unique ID of the deployment by adding the Deployment Unique ID column in the console. Let us start Analyzing the logs from the Policy download to Appenforce in sequential order. I have highlighted the Deployment id and CI Unique ID for the example that we are going to follow. As per our example, we are going to verify the flow of client that is targeted to get Mozilla Firefox Application. identifiers are needed the unique ID of the applications Deployment Type, and the ContentID. In order to troubleshoot the application deployment, it is advised to note the deployment id and CI Unique ID for the deployment and application. Deploying the SCCM Console for Configuration Manager 2012. Lets take a sample Application and Deployment targeted for a collection.

Before proceeding with this Application deployment Troubleshooting it is advised to understand the data flow of Configuration Manager Client architecture.

Sccm application deployment log