With the release of System Center 2012 Configuration Manager, Microsoft introduced the distribution point groups functionality.Distribution point groups provide a logical grouping of distribution points and collections for content distribution as described in the following Technet Article: Configuring Content Management in Configuration Manager, Create and Configure Distribution Point Groups A Distribution Point can be made member of one or more Distribution Point Group, based on the content deployed to that Distribution Point Group and whether the Distribution Point is member of that group, the Distribution Point receives content which is defined for the Distribution Point group.In this case doing this manually wasn’t an option due to the number of files, so I resorted to a quick script based on the one found here: https://tricksntreats.wordpress.com/2010/05/30/sccm-backlog-fighting/ I first had this happen on just one of my servers.
These are listed in the class For starters I filtered the packages after Status being 2 or 3 but there is no obvious property containing the name of the Distribution Point, only the property Server NALPath.
After some more digging on MSDN I found the WMI class SMS_Distribution Point Info which can be used to retrieve the Name and the Server NALPath for a distribution point. So for starters, get the Distribution Point info: $Query = "Select NALPath, Name From SMS_Distribution Point Info Where Server Name Like '%$Dist Point%'" $Distribution Point = @(Get-Wmi Object -Namespace "root SMSSite_$Site Code" -Query $Query) $Server Nal Path = $Distribution Point.
NALPath On the first row I use the operator ‘Like’ which in WQL supports wildcarding by using “%” and regex-like syntax (more on that to come).
Under some circumstances, this task isn’t cleaned up and so the reinstall keeps happening [Place holder post – FULL POST write up coming shortly] https://social.technet.microsoft.com/Forums/en-US/3ac88d59-d1b5-4826-a44d-bb94bfd80f66/configmgr-2012-update-source-content-deleted?
If a Distribution Point in System Center Configuration Manager has failed packages it probably has a cause and resending the packages might not be the right solution to the problem.