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.
Best Answer
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?
Update
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.
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.