Application download in Configuration Manager
Applies to: Configuration Manager (current branch)
Before you continue, review Application deployment client components to understand DCM and CI Agent job processing.
Download initiation
Application content download is started by the CI Agent component on the client during the StateDownloadingContents phase. This process is the same, regardless of whether the application is deployed to a Device Collection or a User collection.
- For Available deployments, application content is downloaded when the user starts the application installation from Software Center.
- For Required deployments, application content is downloaded when the assignment is activated and the application is found Applicable after evaluation. To understand when the assignment is activated, see the Application Deployment to Device Collections or Application Deployment to User Collections articles.
When CI Agent starts the content download, it creates a task that is handled by the CI Task Manager component. CI Task Manager then starts the content download. This activity can be tracked in the CITaskMgr.log by using the Deployment Type Unique ID.
Initiating task ContentDownload for CI ScopeId_B63CEBE7-8A69-4FBE-994F-5AD0A8488D27/DeploymentType_1d49ef88-cf3b-42fa-b198-388d220ccb44.2 (ConfigMgr Toolkit - Windows Installer (*.msi file)) for target: , consumer: {53EA65C2-D596-4215-83E4-F7007B78E18C}
Distribution Point Location
All download tasks are handled by Content Access component, which is responsible for managing the client cache. After the download task is created, Content Access component checks if the content is already available in the client cache. If the content isn't available, it creates a location request to get a list of Distribution Points from where the content can be obtained. This activity can be tracked in CAS.log and LocationServices.log on the client using the Content Unique ID.
Requesting locations synchronously for content Content_00a8f9e6-8e44-42f5-a0ef-9b5c86a88498.1 with priority Foreground
ContentLocationRequest : <Request XML Body>
Reply Message Body : <Reply XML Body>
Important
Although Location Services component handles the location requests, it doesn't directly request locations from the Management Point. All requests to the Management Point typically go through CCM Messaging component, which logs to CcmMessaging.log.
Location reply XML contains the list of distribution points based on the client's boundary group. This list is parsed and persisted in WMI on the client according to the Content Source Priority. This activity can be seen in ContentTransferManager.log, by using the Content Unique ID and looking for Persisted location.
If the location reply XML doesn't contain any distribution points, ContentTransferManager.log would show Received empty location update and the client may get stuck at 0% while downloading the application. This reply can typically occur because of boundary group configuration issues. For more information, see Download failures.
Content Download
Once the Distribution Point locations are obtained, Content Access component creates a Content Transfer job. This activity can be tracked in CAS.log using the Content Unique ID.
Submitted CTM job {6D0EA720-EB4E-4893-8395-8B27470A6CFB} to download Content Content_00a8f9e6-8e44-42f5-a0ef-9b5c86a88498.1 under context System
Content Transfer Manager then creates a Data Transfer Service job to do the content download. This activity can be tracked in ContentTransferManager.log on the client using the Content Unique ID.
CTM job {6D0EA720-EB4E-4893-8395-8B27470A6CFB} (corresponding DTS job {708C7F21-8898-49AB-900E-BA6E5F1A39BC}) started download from '<Distribution Point URL>/Content_00a8f9e6-8e44-42f5-a0ef-9b5c86a88498.1' for full content download.
Note
This log entry can be used to identify the CTM and DTS job ID's, which can be used to track the progress of the Content Transfer in ContentTransferManager.log and DataTransferService.log respectively.
Data Transfer Service downloads the application content by creating a Background Intelligent Transfer Service (BITS) job and waiting for the download to complete. This activity can be tracked in DataTransferService.log on the client using the DTS Job ID obtained from ContentTransferManager.log.
Starting BITS job '{40263E01-2EDD-462F-ABBA-A5E892CB9229}' for DTS job '{708C7F21-8898-49AB-900E-BA6E5F1A39BC}' under user 'S-1-5-18'.
DTSJob {708C7F21-8898-49AB-900E-BA6E5F1A39BC} in state 'DownloadingData'.
DTS job {708C7F21-8898-49AB-900E-BA6E5F1A39BC} has completed
After the download is complete, Content Access component is notified. Content Access component then verifies the downloaded content to ensure that the content wasn't altered during download. This activity can be tracked in CAS.log using the Content Unique ID.
Hash verification succeeded for content Content_00a8f9e6-8e44-42f5-a0ef-9b5c86a88498.1 downloaded under context System
Finally, after content is verified, CI Agent receives the task complete notification and the CI Agent job moves to the next phase.
CIAgentJob({2BF84225-C9E8-49A6-A308-A160C4B799D3}): CAgentJob::HandleEvent(Event=CITaskComplete, CurrentState=StateDownloadingContents)