Many times when running a task sequence (Task Sequence), it would be useful to have the needed software "already" on the local disk. This can now be achieved without much difficulty, as there is a new "Download Package Content" command available in the Task Sequence editor.
When configuring the indicated command, we have a choice of different options for the copy flow:
Looking at the given capabilities, it can be assumed that the use of Custom Path will give the ability to indicate the exact path to the directory where the copied files will be located. In order to test how the command works, two software packages containing script files were prepared. It was assumed that the files should be located on the target system in the C:SRIPT1 and C:SRIPT2 directories, respectively. On the tested system, the C:SCRIPT1 directory did not exist, while the C:SCRIPT2 directory was established, and a file with the same name as in the prepared software package was also introduced inside it.
As a result of the test, it turned out that a subdirectory with a name that is the code of the Package object is assumed in the path specified in the command configuration:
Testing the case of an existing path and the files placed in it overlapping with those contained inside the package, no conflict (or error) was triggered, since the files contained in the distribution package go to a subdirectory, not directly to the directory indicated in the configuration:
To summarize the observations, it can be said:
- If the destination path is set to an existing directory, a subdirectory with the contents of the package to be copied is created inside it.
- If the directory indicated in the configuration does not exist on the target system, it will be created, and a subdirectory with the contents of the package to be copied is created inside it.