Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently set up a new SCCM 2012 environment at my workplace and now we are creating our applications for distribution.

Some applications are set up using a script. When during testing, something was not right and the content of the application needs to be changed. The distribution point keeps on serving the old content to the clients.

I was wondering what the proper procedure is for updating the DP's when the content of an application changes. I have tried redistributing to the distribution points and deleting old revisions but to no avail.

share|improve this question
You may be having problems with the DP Update processes. Anything in the site's logs (Administration, Site Operations, and some other menu options I can't remember off the top of my head)? – Chris S Feb 18 '13 at 15:32
up vote 2 down vote accepted

There is an option on the package to disconnect users so that sccm can update the package. Is this happening with all packages or just one?

enter image description here


I think I know what's happening. I've never used the redistribute option as I never saw the point, now I'm curious and this blog post confirmed my theory that it's more for repair and not updating a package. It copies the package from a third location (not package source like updating the Distribution point) to the DP, which is not what we want to do.

To update the DP, highlight your package and click the highlighted button in my screenshot.

enter image description here

2nd Update

When working with App-v Applications, if I have to update the content, once I stage it to the directory that sccm will copy it from, I highlight the package, then go to the Deployment Types tab, then up top I will click on 'Refresh Content' and go through the prompts. I can confirm this works. In my particular application, this installs from the App Catalog, but apps advertised to the machine should work the same.

enter image description here

share|improve this answer
It is happening with a small number of packages, not all. That looks really useful. (I'm on holiday at the moment, but will certainly give this a try when I get back) – Omnomnomnom Mar 3 '13 at 22:20
I've tested this, but it does not solve the problem. – Omnomnomnom Apr 12 '13 at 12:15
@Omnomnomnom just to confirm you are updating the DP after you add the content to the fileshare, correct? – BigHomie Apr 12 '13 at 12:58
Yes, after changing the content for an application. I go to its properties, click on the content tab and choose redistribute for the necessary DP's. – Omnomnomnom Apr 12 '13 at 14:08
@MDMoore313 - Yup thats exactly what i did. Should have update this thread really. Can confirm that it works for me too – Joe Taylor Jul 12 '13 at 14:09

just wrote a small powershell script that updates all applications :

$DPGroup = "PTB"
Get-Wmiobject -Namespace "root\SMS\Site_ptb" -Class SMS_Application -Filter "isLatest='true' and isExpired='false'" | foreach{
           $name = $_.LocalizedDisplayName
           echo "Application : $name"
           $dptypes = Get-CMDeploymentType -ApplicationName "$name"
           foreach ($dpt in $dptypes){
                $dptname = $dpt.LocalizedDisplayName
                echo "Deployment Type: $dptname"
                Update-CMDistributionPoint -ApplicationName "$name" -DeploymentTypeName "$dptname"
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.