Difference Between Update and Refresh Packages in SCCM
Do you know what the difference between updating a distribution point and refreshing a distribution point is in SCCM 2007? It can be quite confusing, and when to use one over the other is not obvious.
UPDATING A DISTRIBUTION POINT
Lets first talk about Updating a Distribution Point:
Here’s a scenario:
You have created a new package for an application in which you have changed some source files. For example, you have changed settings in a file, added additional files or maybe you have removed files. What it does is it will recreate the whole package with the updated source files and will update the old package with the new package on all distribution points. SCCM will increment the package source version by 1. So a package with source version 1 will become source version 2. When using this, keep in mind the changing of the source versions, as this might cause issues if you have different versions of the packages at your distribution points, causing content mismatch. Make sure that all your Distribution Points update to the new version.
REFRESHING A DISTRIBUTION POINT
What about Refreshing a package on a Distribution Point:
One of your applications is not working and you want to make sure that all the files are intact on your Distribution Point. In this case, you want to repair the package. Doing a refresh of the package will copy the package from the local site system to the Distribution Point, and not from the package source. Unlike doing an update of a package, refreshing will keep the previous source version.
I hope this information has been informative for you 🙂
About the author
Daniel Classon works as a Senior Consultant at Mansoft, focusing on Microsoft Configuration Manager, Windows 10 and Powershell