How can I "refresh" content for an application after I make a change to its source files?
I created a new application for Office 2010 in the SCCM console yesterday. After doing a test push install I realized that I needed to change a setting in my Office Customization Tool .MSP file. I navigated to my UNC content location, edited my .MSP and saved it. Several test pushes later I realized that the old .MSP file was still being pushed out by SCCM it is clearly not updating to reflect my changes (or if it is its happening very slow). How can I get SCCM to update my application content to reflect the changes I made to my source files or verify its updating at all?
July 11th, 2012 4:13am

Software Library > Applicaiton Management > Packages > Your Package and right click and select update distribution points.  This wil refresh the package by looking in your source directory for new or updated files.
  • Proposed as answer by Jörgen NilssonMVP Wednesday, July 11, 2012 6:24 AM
  • Unproposed as answer by ZeusABJ Wednesday, July 11, 2012 3:45 PM
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2012 4:37am

Software Library > Applicaiton Management > Packages > Your Package and right click and select update distribution points.  This wil refresh the package by looking in your source directory for new or updated files.
  • Proposed as answer by Jörgen NilssonMVP Wednesday, July 11, 2012 6:24 AM
  • Unproposed as answer by ZeusABJ Wednesday, July 11, 2012 3:45 PM
July 11th, 2012 4:37am

I had this same issue, here's how I solved it.

Click on the application (MS Office 2010 in your case), then click on the Deployment Types tab (down below in the CM console), then right click on the deployment object that's listed there. On the fly-out menu click Update Content; that will update the application's source content.

Free Windows Admin Tool Kit Click here and download it now
July 11th, 2012 3:11pm

I had this same issue, here's how I solved it.

Click on the application (MS Office 2010 in your case), then click on the Deployment Types tab (down below in the CM console), then right click on the deployment object that's listed there. On the fly-out menu click Update Content; that will update the application's source content.

July 11th, 2012 3:11pm

Software Library > Applicaiton Management > Packages > Your Package and right click and select update distribution points.  This wil refresh the package by looking in your source directory for new or updated files.
With the new Application model in SCCM 2012 there is no package for me to refresh.
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2012 3:46pm

I had this same issue, here's how I solved it.

Click on the application (MS Office 2010 in your case), then click on the Deployment Types tab (down below in the CM console), then right click on the deployment object that's listed there. On the fly-out menu click Update Content; that will update the application's source content.

Edward I really appreciate your taking the time to respond (that's why I voted you and Chad as "helpful"), and I'm thrilled that this worked for you. However it was really premature of the Moderator (Moiz Rassiwala) to mark this as the answer because it did not work for me. Moiz, I check my threads regularly and I'm quite capable of marking my own answers without your help. I'm more than fine with you proposing a response as the answer (thank you for your input Jrgen Nilsson, it's always appreciated) but you might want to make sure the problem is actually solved before making the assumption that a recommended course of action worked. I *did* wind up finding the solution on my own and it was none of the above. What worked for me is posted below (and marked as the correct answer).
  • Edited by ZeusABJ Wednesday, July 11, 2012 6:39 PM
July 11th, 2012 6:26pm

I had this same issue, here's how I solved it.

Click on the application (MS Office 2010 in your case), then click on the Deployment Types tab (down below in the CM console), then right click on the deployment object that's listed there. On the fly-out menu click Update Content; that will update the application's source content.

Edward I really appreciate your taking the time to respond (that's why I voted you and Chad as "helpful"), and I'm thrilled that this worked for you. However it was really premature of the Moderator (Moiz Rassiwala) to mark this as the answer because it did not work for me. Moiz, I check my threads regularly and I'm quite capable of marking my own answers without your help. I'm more than fine with you proposing a response as the answer (thank you for your input Jrgen Nilsson, it's always appreciated) but you might want to make sure the problem is actually solved before making the assumption that a recommended course of action worked. I *did* wind up finding the solution on my own and it was none of the above. What worked for me is posted below (and marked as the correct answer).
  • Edited by ZeusABJ Wednesday, July 11, 2012 6:39 PM
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2012 6:26pm

Thanks to everyone who responded. This is what is worked for me:

Right-click application, choose properties, navigate to "Content Location" tab, highlight the distribution point you wish to update and click the "Redistribute" button.

  • Marked as answer by ZeusABJ Wednesday, July 11, 2012 6:30 PM
July 11th, 2012 6:29pm

Thanks to everyone who responded. This is what is worked for me:

Right-click application, choose properties, navigate to "Content Location" tab, highlight the distribution point you wish to update and click the "Redistribute" button.

  • Marked as answer by ZeusABJ Wednesday, July 11, 2012 6:30 PM
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2012 6:29pm

Sorry to resurrect a very old thread, but I just wanted to note that ZeusABJ's solution did not work for me, while GonzEd's did. I've tried using Redistribute on a number of occasions and it has never updated the source files; previously, I was removing and recreating the deployments themselves, which was a real pain. I didn't know about what GonzEd suggested, so thanks!
October 4th, 2013 3:33pm

Did you find a solution for this problem...Update content and Redistribute option are not working for Applications like the office installation with a script (install.cmd).  I still have the same files then the first time 'a distributed when I update the content or redistribute to DP.  I have to delete and recreate the application every time.
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2014 4:45pm

Did you find a solution for this problem...Update content and Redistribute option are not working for Applications like the office installation with a script (install.cmd).  I still have the same files then the first time 'a distributed when I update the content or redistribute to DP.  I have to delete and recreate the application every time.

Have you ran "Machine Policy Cycle" and "Application Evaluation Cycle" after the changes on the client in case?

Those should trigger the update of the content. I also always remove the old revisions of the applications (by right click -> revisions) after I do changes.

March 10th, 2014 4:59pm

Did you find a solution for this problem...Update content and Redistribute option are not working for Applications like the office installation with a script (install.cmd).  I still have the same files then the first time 'a distributed when I update the content or redistribute to DP.  I have to delete and recreate the application every time.

Here's the method I use:

http://eskonr.com/2013/09/sccm-configmgr-2012-how-do-i-refresh-the-application-after-change-in-source-files-or-source-location/

Free Windows Admin Tool Kit Click here and download it now
March 10th, 2014 5:01pm

Hello Everyone.

For me the only that did it was to edit the deployment type and change the in the content tab the source folder to a new one. After that I could see in Monitoring->Content Status that my application had a new source version that was replicating.

Alin

September 24th, 2014 6:53am

I have used GonzEd's solution on several applications successfully.
Free Windows Admin Tool Kit Click here and download it now
April 18th, 2015 9:11am

Under the Programs tab of an .msi deployment, I added an " that I left out. Here is the installation command.

msiexec /i "QuickTime.msi" TRANSFORMS="quicktime.mst" /q

I forgot the 3rd ".

After fixing the installation command I went to the Content Locations tab and clicked on Redistribute. After 30 minutes of the Application Deployment not updating I went to the Application in Software Library. I clicked on Deployment Types on the bottom of the screen, then I right clicked on the Deployment Type and clicked "Update Content". About an hour after that I was able to install the application.

For 1.5 hours I knew that the application hadn't updated yet because the error message when trying to install the application indicated that I was missing a ".

June 25th, 2015 10:41am


After fixing the installation command I went to the Content Locations tab and clicked on Redistribute. 

So you did not modify the source files. That does not require to touch anything content related. That information is part of the policy that the client is downloading. 
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2015 11:38am


After fixing the installation command I went to the Content Locations tab and clicked on Redistribute. 

So you did not modify the source files. That does not require to touch anything content related. That information is part of the policy that the client is download
June 25th, 2015 11:40am

It depends on the settings of the policy polling interval. 
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2015 12:01pm

Shouldn't running the Machine Policy Retrieval & Evaluation Cycle and/or the Application Deployment Evaluation Cycle override that polling interval?
June 25th, 2015 12:04pm

Sure.
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2015 1:04pm

I made a change to my application and updated it with both of the suggestions here. After 25 minutes SCCM still has not updated the application. This could be the slowest moving software every created.
June 25th, 2015 2:39pm

What have you changed exactly and what did you expect to happen where?
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2015 3:39pm

Any "Redistribute" button you can find, click it. (see posts above)

Run Machine Policy Retrieval & Evaluation Cycle and the Application Deployment Evaluation Cycle.

If all that fails and you still see the wrong .cmd information running I would remove the application from all DPs and then rebuild the entire application and package.

I'm not saying the last idea is a good one, but it might work.

July 1st, 2015 8:53am

The only thing I found that works is this (found via searches in which other people experienced the same issue)

Software Library > Application Mgmt > Applications > click on your application > at the bottom there are 3 tabs [Summary | Deployment Types | Deployments] - click on deployment types > right click your deployment type > Update Content

This was the only thing I could find that would actually update the content library on the DP.

(edit: this was suggested in an answer above - I just wanted to second that answer...)

Free Windows Admin Tool Kit Click here and download it now
July 1st, 2015 9:04am

The only thing I found that works is this (found via searches in which other people experienced the same issue)

Software Library > Application Mgmt > Applications > click on your application > at the bottom there are 3 tabs [Summary | Deployment Types | Deployments] - click on deployment types > right click your deployment type > Update Content

This was the only thing I could find that would actually update the content library on the DP.

(edit: this was suggested in an answer above - I just wanted to second that answer...)

  • Edited by atom_acres Wednesday, July 01, 2015 1:05 PM
July 1st, 2015 1:00pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics