Yearly clean up for Software Update Automatic Deployment Rules

OK Shield

okshield

Each year it is good to clean up the software update packages so they don't grow out of control and cause havoc in your sccm town.

Review current Deployment Packages.

 

  1. If not already fix up, rename and date the Deployment Packages appending the year. Ie;
  • Windows 7 x64 Updates - 2014
  • Windows 7 x86 Updates - 2014
  • Windows 8 x64 Updates - 2014
  • Office 2013 Updates - 2014
  • etc

  1. Under Deployment Packages ensure the packages aren’t having any distribution problems, Green is good.  If so the package may have too many updates (Limit is 1000, I still think it should be 500) and you should move some to a new package.

Create new Deployment Packages for each type of update

 

Creating yearly packages will reduce the size of the packages and will have less distribution problems. The easiest way is to use a powershell script created by Nickolaj Andersen as creating packages in the console is stupid and slow. Check out http://www.scconfigmgr.com/2014/11/06/create-a-deployment-package-in-configmgr-2012-with-powershell/ for the script.

Usage:

.New-CMDeploymentPackage.ps1 -SiteServer SiteServerName -Name "Windows 7 x64 Updates - 2015" -Description "Windows 7 x64 Updates - 2015" -SourcePath "\PathWindows7x64-2015" –Verbose

 

Replace the bold with whatever makes you happy.

Next, add the new packages to distribution points by right clicking them and choosing Distribute Content

 

Modify the Automatic Deployment Rules to use the new packages.

 

Modify each Automatic Deployment Rules (ADR) to use new deployment packages for the new year.

  • Open Properties of the ADR
  • Go to the Deployment Package page
  • Click Browse and choose the new package.

OK Shield

  • Click Browse and choose the new package.

 

Remove Expired and Superseeded Updates

 

Under All Software Updates run a search with the criteria Expired = Yes.

Select all then updates then click Edit Membership

Untick all the updates in the next window

 

You can also do this for superseded updates by changing the search criteria to Superseeded = Yes. For more information about superseedence and expired updates visit https://technet.microsoft.com/en-us/library/cc708465%28v=ws.10%29.aspx

2 Comments

  1. Hi Jay.

    Thanks for taking the time to write this post.
    Recently we run out of space in our SCCM server due to the Updates role and therefore the updates deployment packages stop distributing the content. Since we were unable to increase the storage that was already at 1tb, as an immediate "solution" we had to delete some updates from the "sources" folder. As a consequence, we release more than 200gb but some of the content from those packages that wasn't distributed became "orphan" on the content library and now we are not able to distribute those deployment packages because it cannot find the match from the sources folder.
    Ex:
    The source directory \\sccm\sources$\Updates\Windows 8\664da4a1-5548-416f-8511-990dca0b31eb doesn't exist or the SMS service cannot access it, Win32 last error = 2
    Failed to take snapshot of one or more contents in package PT10008A

    We run the query from this site https://fritschetom.blogspot.pt/2014/04/software-updates-deployment-package.html?showComment=1507907428860#c2698584159045046139

    but cannot find the update Kb; the articleID is empty.

    If we cannot find the KB, we only have one solution which is to delete all the packages and create everything from scratch.

    My question is: if we delete the deployment packages will the content-library also get cleaned for the matching updates or do we need to run a clean up to clean it?

    Any other tip to solve this problem?

    Thank you in advance for your time.

    Cheers,
    Pedro

    • Author
      Jay Connor November 3, 2017 Reply

      Hmm Your update deployment package is dead..
      You need to delete your deployment packages from the console.
      Make a new deployment to create a new deployment package.
      Go to old deployment(s). Select updates and download to new deployment package.

      I think the content library should resize a bit when it's not referencing any files removed.

      Get more storage and use the Content Library Transfer tool

Leave a Comment

Your email address will not be published. Required fields are marked *

*