{"id":1105,"date":"2014-01-10T17:30:26","date_gmt":"2014-01-10T17:30:26","guid":{"rendered":"http:\/\/www.autoitconsulting.com\/site\/?p=1105"},"modified":"2025-07-26T12:51:46","modified_gmt":"2025-07-26T11:51:46","slug":"mass-redistribute-packages-configmgr-2012","status":"publish","type":"post","link":"https:\/\/www.autoitconsulting.com\/site\/deployment\/mass-redistribute-packages-configmgr-2012\/","title":{"rendered":"Mass Redistribute Packages in ConfigMgr 2012"},"content":{"rendered":"\n

Overview<\/h2>\n\n\n\n

Recently I came across an issue with System Center Configuration Manager (ConfigMgr) 2012 where a large number of packages and applications had failed to be distributed to a new Distribution Point (DP). There were many thousands of packages in the environment and a few hundred were showing in the error state in the console. Unfortunately, once packages get into this state then they don\u2019t fix themselves as it appears that the ConfigMgr validation schedule only reports that there was a problem distributing – it doesn\u2019t actually trigger a redistribution.<\/p>\n\n\n\n

To fix the problem you have to identify each package that has a problem and go into its properties. Then you need to select the DPs you want to redistribute to and click Redistribute.<\/p>\n\n\n\n

\"CM2012<\/a><\/figure>\n\n\n\n

<\/p>\n\n\n\n

You have to to do this for each package<\/strong> that has a problem taking care to only redistribute to the DPs that have have failures. In an environment with a few hundred problem packages with thousands of DPs this is completely impractical. What we need is a script that can do the following:<\/p>\n\n\n\n