When deploying a machine with a task sequence and using "Download content locally when needed by task sequence", package source filesthat aredownloaded during the task sequenceare not kept on the machine, but removed after the install of the package is finished. The packages are also not downloaded to the normal client cache (c:\windows\system32\ccm\cache), but to c:\_smstasksequence\packages\<packageid>. Is this how it should work? It causes us major problem, because if windows installer packages is installed during task sequence, the windows installer source files is not available if the programs need to repair. It is ok if the machines is connected to network because then we can use windows installer source list update, but we have many portable machines not always connected to network that need the source files locally.

We're also experiencing this issue. All our application deployments are part of a task-sequence, so that some logic can be applied before install - i.e dependancies, application ordering methods etc.. Now, a package we have operates correctly via a standard advertisement. Deployment via a Task Sequence doesn't persist the package in the cache. It does exactly what kungcocos describes. This has serious issues with our deployment, as most of our MSI apps repair on first use (in order to install the user-section), to do this, it needs the source-files.Erm........ TS has already cleared it's cache.... I believe my tech has already raised this with MS directly, so should hopefully have an answer soon. But if anyone has experienced this, or got a work-around, please post. BTW - SCCM SP1 + R2

Got answer from Microsoft, this is how its works right now, its by design. A lot of people have this problem andthe MS technician i spoke to said that therearea design change requests filed to the SCCM development team, so hopefully we will sea change in SP2. Meanwhile my workaround is to create a script that first copies the files from _SMSTaskSequence\Packages\<packageid> to another folder on the harddrive and then run the installation from there. Not optimal, but it works. Also addning sourcelist through the SCCM windows installer source list update method.

It's an old thread but maybe you can publish the script you created to solve this issue? Thanks

hi Joachim, although not the as mentioned above, it will perform a similar task (copying the contents of the package to a dir you specify) http://www.windows-noob.com/forums/index.php?/topic/2758-how-can-i-copy-files-from-a-package it will also shed light on how the advertisement distribution point settings can affect what you copy My step by step SCCM Guides I'm on Twitter > ncbrady