How to troubleshoot DP content issue
Question
We have 50 DPs. Out of which content didnt go properly to 20 DPs. How to troubleshoot the issue?
Also if content gets corrupted in few DPs, how to get the same content to remaining DPs?
Also how to verify whether the content went properly to a DP? Do we need to check in log files? If so, what data do we need to check in log files.
Answers ( 4 )
Most of the time distmgr.log would help to sort out the issue. There could be several possibilities , may be network communication issues , sendor is unable to connect to remote server (DP) , IIS related issues DP and so on.
Content validation option you can use to check the consistency of the content on DPs
Hi,
We have 50 DPs. Out of which content didnt go properly to 20 DPs. How to troubleshoot the issue?
Karthik – How about your Site DP throttle configured? for troubleshooting use ankit link.
Also if content gets corrupted in few DPs, how to get the same content to remaining DPs?
Karthik – Enable content validation that will periodically check the content on all distribution points.
Also how to verify whether the content went properly to a DP? Do we need to check in log files? If so, what data do we need to check in log files.
Karthik – Distmgr.log will provide log details. – To check the status you can use SCCM console DP monitor status.
or you can use below SQL query. create RDL file and use in reporting portal enable subscription
—————————————————————————————————————–
Select
vp.PackageID,
vp.Name,
Case vp.PackageType
When 0 Then ‘Package’
When 3 Then ‘Driver’
When 4 Then ‘Task Sequence’
When 5 Then ‘software Update’
When 7 Then ‘Virtual’
When 8 Then ‘Application’
When 257 Then ‘Image’
When 258 Then ‘Boot Image’
When 259 Then ‘OS’
Else ‘ ‘
END AS ‘PackageType’,
vp.Manufacturer,
vp.Version,
vp.Language,
(pkgs.SourceSize/1024) as ‘Package Size (MB)’,
vp.PkgSourcePath,
vp.SourceVersion,
vp.SourceDate,
Pkgs.Targeted,
pkgs.Installed,
pkgs.Pending,
pkgs.Retrying,
pkgs.Failed,
pkgs.Unknown
from
vPkgStatusSummary as Pkgs
Inner Join v_Package as Vp on pkgs.PkgID=vp.PackageID
order by 3
——————————————————————-
Thanks
Karthikeyan
Basically you need to analyse the “distmgr.log” which Records details about package creation, and updates.
For more details refer the article provided by Ankit.
Below Is the article which is enough to understand and troubleshoot content distribution.
https://support.microsoft.com/en-gb/help/4482728/understand-troubleshoot-content-distribution-in-configuration-manager