There is a Distribution Point associated with the boundary group.
4.
The content is distributed successfully to the DP.
5.
The software / update / package is deployed to the device.
6.
Enable verbose logging on the site system with the MP role and the client
We enabled Verbose logging on the cient and management point
Successful Content Lookup Flow
There are many moving parts when a content location request is sent to the management point and processes by a ConfigMgr client. Here are some key snippets of how this happens.
Log File
Log Text
CCIStateStore.log
CCIStateStore::GetCIState - Client is requesting CI ModelName ScopeId_CA3F999B-7A81-43BF-912C-56E267C1E565/RequiredApplication_4894a05f-49c0-4836-a22f-50526dba27c4, Revision 1 for User: S-1-5-21-1880864260-2612682489-34998949-6112
CIDownloader.log
CDownloadPayloadInfo::AddCI - CI with ModelName ScopeId_CA3F999B-7A81-43BF-912C-56E267C1E565/DeploymentType_677dac51-d2a2-4bbd-aeb0-4b845aa288cd, Version 1 is already available. Requested Model:VersionSpecific will be downloaded.
CAS.log
===== CacheManager: Content for Content_8ba1768d-abc6-4e42-919d-1e421fe610f0.1 was NOT found cache. =====
Starting download on action (INSTALL) for Update (9c93cbee-aabc-4daf-996a-4580daa09c87)
UpdatesHandler.log
Content Text = <Content ContentId="9c93cbee-aabc-4daf-996a-4580daa09c87" Version="1"><FileContent Name="debcf2da-e7da-4c50-b718-fc95ffe40c9d_1.cab" Hash="78A05BCA9CCA039C62C1B2D494281E72ED864BD9" HashAlgorithm="SHA1" Size="79417630"/></Content>
ContentTransferManager
Submitted CTM job {C17823B5-A8A9-48F8-8375-64CFC55869CB} to download Content 9c93cbee-aabc-4daf-996a-4580daa09c87.1 under context System - ContentTransferManager
CTM job {C17823B5-A8A9-48F8-8375-64CFC55869CB} (corresponding DTS job {C54E37D3-BFDE-4629-AC82-32E6CE733750}) started download from 'http://DEMO1.CONTOSO.LOCAL/SMS_DP_SMSPKG$/9c93cbee-aabc-4daf-996a-4580daa09c87' for full content download.
DataTransferService.log
DTSJob {C54E37D3-BFDE-4629-AC82-32E6CE733750} created to download from 'http://DEMO1.CONTOSO.LOCAL:80/SMS_DP_SMSPKG$/9c93cbee-aabc-4daf-996a-4580daa09c87' to 'C:\Windows\ccmcache\1'.
UpdateURLWithTransportSettings(): NEW URL - http://demo1.contoso.local:80/SMS_DP_SMSPKG$/9c93cbee-aabc-4daf-996a-4580daa09c87/sccm?/debcf2da-e7da-4c50-b718-fc95ffe40c9d_1.cab
DataTransferService.log
Total content size from the downloaded manifest is 79417630
DataTransferService.log
Creating root directory...
DataTransferService.log
Directory 'C:\Windows\ccmcache\1' already exists.
DataTransferService.log
Starting BITS job '{97C9975B-820F-467A-9A0D-366C70F28EEC}' for DTS job '{C54E37D3-BFDE-4629-AC82-32E6CE733750}' under user 'S-1-5-18'.
BITSHelper, remote name = http://DEMO1.CONTOSO.LOCAL:80/SMS_DP_SMSPKG$/9c93cbee-aabc-4daf-996a-4580daa09c87/sccm?/debcf2da-e7da-4c50-b718-fc95ffe40c9d_1.cab, local name = C:\Windows\ccmcache\1\debcf2da-e7da-4c50-b718-fc95ffe40c9d_1.cab
DataTransferService.log
Job: {C54E37D3-BFDE-4629-AC82-32E6CE733750}, Total Files: 1, Transferred Files: 0, Total Bytes: 79417630, Transferred Bytes: 262144
CAS.log
CContentAccessService::NotifyDownloadProgressEx - downloaded size 52480, total size 77556
CAS.log
The hash we are verifying is SDMPackage:<Content ContentId="9c93cbee-aabc-4daf-996a-4580daa09c87" Version="1"><FileContent Name="debcf2da-e7da-4c50-b718-fc95ffe40c9d_1.cab" Hash="78A05BCA9CCA039C62C1B2D494281E72ED864BD9" HashAlgorithm="SHA1" Size="79417630"/></Content>
CAS.log
Hash verification succeeded for content 9c93cbee-aabc-4daf-996a-4580daa09c87.1 downloaded under context System
DataTransferService.log
Job: {C54E37D3-BFDE-4629-AC82-32E6CE733750}, Total Files: 1, Transferred Files: 1, Total Bytes: 79417630, Transferred Bytes: 79417630
Tip: You can open all content logs at once in CMTrace.exe by adding the following files: "CAS.log" "CIAgent.log" "CIDownloader.log" "CIStateStore.log" "ClientLocation.log" "CMBITSManager.log" "ContentTransferManager.log" "DataTransferService.log" "DCMAgent.log" "LocationServices.log" "StateMessage.log" "UpdatesDeployment.log"
Merge all content logs in CMTrace.exe
Snippets of Location Request
Example of the management point MP_Location.log calling the stored procedure MP_GetContentDPInfo
A point of interest is DPLocality flag determines how the client obtains distribution points, according to distribution point locality. Possible values are:
Value
UInt32
DP_DOWNLOAD_FROM_LOCAL
4
DP_DOWNLOAD_FROM_REMOTE
6
DP_NO_FALLBACK_UNPROTECTED
17
DP_ALLOW_WUMU
18
DP_ALLOW_METERED_NETWORK
19
SMS_CIAssignmentBaseClass Class - Configuration Manager
docsmsft
Scenario 2: Failed Content Lookup Due to Boundary Misconfiguration
Pre-Conditions
1.
Healthy ConfigMgr client.
2.
The client is NOT in a boundary.
3.
There is a Distribution Point associated with the boundary group the client is NOT in.
4.
The content is distributed successfully to the DP.
5.
The software / update / package is deployed to the device.
6.
Enable verbose logging on the site system with the MP role and the client
Client is not in boundary group
Notable Ways to Identity when a Client is Not in Boundary Group
If a client is not in a boundary group here are some snippets that can be helpful.
Log File
Log Description
LocationServices.log
Client is not in any boundary group and ConfigMgr is no longer managing WindowsDO GPO. Set WindowsDO GPO to default values. Mode = LAN. GroupID = empty
CAS.log
The number of discovered DPs(including Branch DP and Multicast) is 0
In the content location request in the CAS.log, you will also notice the BoundaryGroup element doesn't contain the fields GroupID, GroupGUID, or GroupFlag.
ContentLocationRequest comparison
Tip: Search the text "ContentLocationRequest" in the CAS.log to find location requests performed on the client-side logs.
In the CAS.log here is an example of a response from the management point when the client is in no boundary group, and fallback is disabled, and no content was found.
If the content is not found, you will be able to note the following line in StateMessage.log
State message(State ID : 5003) with TopicType 1702 and TopicId ScopeId_CA3F999B-7A81-43BF-912C-56E267C1E565/DeploymentType_677dac51-d2a2-4bbd-aeb0-4b845aa288cd/1 has been recorded for S-1-5-21-1880864260-2612682489-34998949-6112
State messages - Configuration Manager
docsmsft
StateMessage ID 5003 with TopicType 1702
Scenario 3: Download Failure Due to Content Distribution Failure
This scenario covers some of the basics in troubleshooting content that has failed to distribute to a distribution point.
Log Files for Troubleshooting Content Distribution in ConfigMgr
Log File
Log Text
distmgr.log
Records details about package creation, compression, delta replication, and information updates. It can also include other activities from the distribution manager component. For example, installing a distribution point, connection attempts, and installing components. For more information on other functionality that uses this log, see Service connection point and OS deployment.
PkgXferMgr.log
Records the actions of the SMS_Executive component that is responsible for sending content from a primary site to a remote distribution point.
Understand components and threads - Configuration Manager
docsmsft
Example of Error if the Source Folder Doesn't Exist or the Site Server Doesn't Have Access
Log File
Log Text
distmgr.log
The source directory \\demo3\Sources\Applications\Igor Pavlov\7-Zip (x64) - MSI Install\aad16824-5471-4dd8-ae69-f71167d7051d\ doesn't exist or the SMS service cannot access it, Win32 last error = 2
distmgr.log
Failed to take snapshot of one or more contents in package DM300013
Scenario 4: Download Failure Due to Invalid Content
For scenario 4, we delete a file directly from the FileLib and modify a file directly in the FileLib. We will cover the content library in a future video. This builds off of scenario 3 by showing specific failure scenarios.
The fix for this type of scenario may be as simple as performing an 'update content' or 'redistribute' the content which is failing. Other times you may have to validate antivirus exclusions on your endpoints and servers. Using the log files to identify what type of error is occurring will be key to resolving the issue and determine where the issue lies.
Example of Error if the Hash of the Downloaded File Does Not Match the Expected Hash
Log File
Log Text
CAS.log
Failed to do hash verification with preference : 4. Try to verify at next hash algorithm
CAS.log
Download failed for content Content_ebb608a6-a6a7-4384-b168-63a0f446b7fb.1 under context S-1-5-21-1880864260-2612682489-34998949-6112, error 0x80091007
DCMAgent.log
appState: DownloadFailed
The above log files and lines would be helpful from the client when determining if there is a hash mismatch issue. It is good to note that the hash mismatch may not be due to a corrupt file in the Content Library, but it is still worth investigating. This can also commonly be due to Antivirus on the endpoint which lacks the prover exclusions for example.
Example of Error if a File is Missing from the Content Library When a Client Requests It
The Content Access service. Maintains the local package cache on the client.
CIAgent.log
Records details about the process of remediation and compliance for compliance settings, software updates, and application management.
CIDownloader.log
Records details about configuration item definition downloads.
CIStateStore.log
Records changes in state for configuration items, such as compliance settings, software updates, and applications.
ClientLocation.log
Records tasks that are related to client site assignment.
CMBITSManager.log
Records information for Background Intelligent Transfer Service (BITS) jobs on the device.
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.
DCMAgent.log
Records high-level information about the evaluation, conflict reporting, and remediation of configuration items and applications.
LocationServices.log
Records the client activity for locating management points, software update points, and distribution points.
StateMessage.log
Records details about software update state messages that are created and sent to the management point.
UpdatesDeployment.log
Records details about deployments on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
Server Logs
Log File
Description
MP_Location.log
Records location request and reply activity from clients.
IIS Logs
Built-in IIS logging - useful for all IIS based ConfigMgr roles. Log location and name may vary.