Sccm 2016 distribution point not updating

Posted by / 16-Jun-2017 18:32

Sccm 2016 distribution point not updating

Scenario 2: Distribution of a boot images towards two distribution point groups, remove the content from one of the distribution point groups.

I distributed one of the boot images towards two distribution point groups (DP_ALL and DP_MDT01), after validation that the content has arrived, I removed the content from one of the distribution point groups (DP_MDT01)and monitored what happened.

Then removed the MDT01 distribution point from the DP_All distribution point group.

Scenario 6: Distribute content to distribution point group, remove distribution point from distribution point group I distributed a boot image to the DP_ALL distribution point group, validated that the content arrived on both distribution points.

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.

If an application is retired, it stays on the distribution point, but you can’t distribute it anymore (leaving compliance in monitoring less than 100%) so if you expire an application remember to remove it from the distribution point groups. Make sure you understand how this works before you start cleaning up the mess, read this blogpost in order to understand the scenario’s.

My lab environment is configured as followed (thanks to Johan Arwidmark for sharing the possibility to install a Config Mgr environment using his Hydration solution – latest version here) In order to see what is really available on the Distribution Points I used the Content Library Explorer, which is part of the Configuration Manager 2012 R2 toolkit provided by Microsoft.

Scenario 1: Distribution of one of the boot images to the DP_ALL distribution group, remove the boot image from the MDT01 distribution point and perform a redistribute on the DP_ALL distribution group Boot image is distributed to both distribution points, after validating that the boot image has arrived we can see that the boot image is available as content on both the distribution point group and the distribution points.

sccm 2016 distribution point not updating-85sccm 2016 distribution point not updating-18sccm 2016 distribution point not updating-11

In Configmgr 2007,we do this by right click package, Update the package,which will take the changes to All Distributed Sites.