Add files to existing software package

[chrismcevoy72]

We currently have a few software packages that simply copy files to a specific folder on the client PC.  We do this by adding the files to a software package, which is attached to a software release and then specifying the destination folder in the quick delivery task and unticking the "delete if unused" options.  We find this is much more reliable than using hte copy file task.  For these software release we don't use rules or assosiations - they are very basic as they only need to deliver files to a folder.

We've now gone back to edit the original software pacakge of one of these to add a new file to the list to be copied.  It's been added to the package and appears in the list of files when editing the package.  However, when we re-deploy the package with the quick delivery task - the new file never arrives at the client.  Almost like the original package is being delivered instead of the updated one or the new file hasn't been added to the original package.

We've tried changing the version number of the release and changing the name of the package, but the new file still never arrives as part of the package.

What are we doing wrong?  I assumed you could edit an existing package to change file contents and those new contents would be delivered when the package is next deployed?

 

[Alex Hedley]

When making an update to a file you need to inform the NS that the has been done so the Policies can get the updated files.

Under Actions

• Update Distribution Points (OK)

Now run the following on the NS

• NS.Package Distribution Point Update Schedule
• NS.Package Refresh
• NS.Package Server Status Event Capture Item

 

[Alex Hedley]

[chrismcevoy72]

Hi Alex,

Thanks for the suggestions.  The files were originally updated last week and the update schedules have run many time since then.  I just ran them again, just in case, and tried another deploy of the package.  Same result - the new file is not downloaded to clients that previously had the package.  

However, deploying the package to a client that hasn't received the package previously results in the all of the files - including the new one - to be copied as expected.  So it seems that clients that previously had the package are somehow ignoring the updated package...?