Living Life 1 Diet Pepsi at a time

SCCM Application Installation Workflow

The most common questions I receive from our client support team is how to troubleshoot why an SCCM deployment did not work. Depending on the installation there could be any number of errors. However, to start the process, they need to review the log files. When I tell them to look at the log files, I receive this blank look on their face. Below is my attempt to document the process flow through the logs. I cannot take credit for all this work, just how it is presented. I received most of the information from Adam Pazik and Kenneth. Links to their blogs are at the end of this post.

The Log Files

AppDiscovery.log Records details about the discovery or detection of applications on client computers

Problems with Detection Methods will be logged here.

AppIntentEval.log Records details about the current and intended state of applications, their applicability, whether requirements were met, deployment types, and dependencies.
AppEnforce.log Records details about enforcement actions (install and uninstall) taken for applications on the client.

Shows the installation command lines, the context for the install, any error codes

CAS.log Records details when distribution points are found for referenced content.
ContentTransferManager.log Schedules the Background Intelligent Transfer Service (BITS) or Server Message Block (SMB) to download or access packages.
DataTransferService.log Records all BITS communication for policy or package access.
LocationServices.log Records the client activity for locating management points, software update points, and distribution points. Look here for boundary assignment.

High-Level Flow of Information

Gather application id, deployment type id’s, and content location id

Start Reviewing the log files

The above steps provided us with the information we need to mine information from the deployment logs. You will want to use the CMTrace.exe tool to review all log files. I will select the 7-zip application from Software Center to start the installation process to monitor.

References:

https://blogs.technet.microsoft.com/manageabilityguys/2013/10/01/configmgr-2012-tracking-application-model-installations-on-clients/

https://deploymentparts.wordpress.com/2015/08/14/how-to-track-an-installation-through-client-log-files/

https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/log-files