Sccm update distribution point not updating

20-Feb-2020 05:15 by 4 Comments

Sccm update distribution point not updating - Crolivecam

Each time the upgrade installs it resets my speech language to “English (United States)” which means Cortana stops working as my Region is set to “Australia” I also use Config Mgr to handle updates on my network (this would also apply for people using WSUS) so when I go into the Region & language settings I don’t get the Speech feature appearing under the “English (Australia)” options. I recently experienced an issue with a very large number of Config Mgr 2007 package updates (400) to a large number of sites (1700).It turns out there was already a distribution job that was “stuck” in the queue and when the large update went out it resulted in a massive backlog.

INI to H:\SCCMContent Lib\File Lib\EB90\EB90C09879C4D86BB5FD5EAB 7245DC68C9588661A38AC76945A4E6F99789CCE9. INI [B84][Sun 03/13/2016 ]: CFile Library:: Add File failed; 0x80070002 [B84][Sun 03/13/2016 ]: CFile Library:: Add File failed; 0x80070002 [B84][Sun 03/13/2016 ]: CContent Definition:: Add File failed; 0x80070002 [B84][Sun 03/13/2016 ]: Failed to add file 'Install-file.exe' to content library.

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).

Error code: 0X80070002 This was due to the files already being in the content library on the DPs with the same hash values however this one time the required INI and SIG files weren't created.

After trying everything I thought would fix it I had to resort to hacking the content library, luckily I had one DP that had a good copy of the package.

My personal preference is to define distribution groups, and always distribute content to distribution groups.

The main advantage of this is, that when you add a new distribution group in your hierarchy, you simply add the distribution point to the already existing distribution point group and it will be filled with the content defined for the distribution point group. Either distribute all content to all distribution points, or at least be consistent to always distribute to distribution point groups instead of distribution points.

Under some circumstances, this task isn’t cleaned up and so the reinstall keeps happening [Place holder post – FULL POST write up coming shortly]

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.

I don’t want to be blamed that content gets removed from your distribution point while you are cleaning things up. Removing content from a distribution point while initially deployed to a distribution point group is evil! If you remove a distribution point from a distribution point group, the content stays on the distribution point.

In order to test the behavior of distributing content to primary I created several scenario’s in my Config Mgr lab environment.

In large environments, inconsistent distribution of content can lead to distribution points which are not aligned to each other, while you intended them to be because you grouped them in a Distribution Point group. If you have the possibility to do so, use RBAC to restrict access to distribution points while giving access to the distribution point groups 2.