Quantcast
Channel: Configuration Manager 2012 - Security, Updates and Compliance forum
Viewing all articles
Browse latest Browse all 6382

Cleaning up deployment packages

$
0
0

I am running SCCM 2012 SP1

Each month after update Tuesday I run an Automatic Deployment Rule and add updates to a deployment package.  That package is now about 6GB in size and I am having issues trying to get it to update on all Distribution points.  This week I have gone through all the updates I have and removed any superseded updates from the software update groups that they were associated with (I did this by selecting all superseded updates and editing their membership, I did not use a script).  I am not sure how to now remove these from the Deployment package.  If my understanding is correct, expired updates will automatically get removed from a Deployment package after 7 days but that isn't the same for the superseded updates which I have removed.

I have seen some forums mentioning scripts but am not sure what is a tried and true way of doing it.  Is there anything supported by MS ? 

I realise that I should have created a new deployment package before now.  Even if I can reduce the size of the deployment package am I best to go to this months update group, and download it into a new deployment package ?

One last question, as I said, some of my distribution points have failed to update with the most recent update of the deployment package.  When I update the distribution points again, some of the failed distribution points successfully get the content and distribution points which had successfully received the content fail.  Am i correct in assuming that even though they failed when I updated the distribution points the fact that they succeded the first time the content was distributed means that they will have the up to date contents and the clients will be able to retrieve the updates ?

Thanks

G


Viewing all articles
Browse latest Browse all 6382


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>