To resolve this issue is to modify the PkgStatus table on the central site server SQL database, and then refresh the affected distribution points.Run The SQL query for each affected distribution point.
update pkgstatus set Status = 2 where id = '< package ID >' and sitecode = '< site code >' and type = 1
update pkgstatus set SourceVersion = 0 where id = '< package ID >' and sitecode = '< site code >' and type = 1
Note:
Microsoft stated that this issue can randomly occur in larger SCCM environments with large packages and slow WAN links, and they are unable to exactly pinpoint the problem due to its random nature
No comments:
Post a Comment