I have been messing around with Prestaged Media lately and to be honest I wish I had done this before. I see alot of value in providing a vendor with the source files from your Task Sequence and not having to download them during the deployment. I will be publishing the steps I took to create my media as I’m sure I’ll be using it again but did run across the following information that I wanted to post regarding Packages and Driver Packs and how they interact with PreStaged Media.
In System Center 2012 Configuration Manager Service Pack 1, new functionality was introduced for prestaged media that allows you to specify applications, packages and driver packages to deploy with the operating system.
The documentation states that the task sequence will check the cache for valid content first, and if the content cannot be found or was revised, the content is downloaded from the distribution point.
Ref: Microsoft TechNet. What’s New in Configuration Manager SP1 – Operating System Deployment. http://technet.microsoft.com/en-us/library/jj591552.aspx.
However, while this check does occur, the new content for packages is never downloaded and the cached content will continue to be used.
An issue has been identified where packages and driver packages do not download revised content after the pre staged media has been created in Configuration Manger 2012 SP1. It should be noted that applications are not affected by this issue, they will still continue to download content after they have been updated.
It is recommended that the prestaged media should be regularly updated if packages and driver packages are updated frequently.