Dynamic application and package deployment for prestage media
We are trying to use prestage media to deploy images to machines on sites with little bandwidth, but still with a network connection to the corporate network.
We have a large number of sites and our current online build uses an MDT database with Roles and Make / Model configurations for a large number of sites and hardware types.
Within each of these, we have a number of packages and applications which are installed depending on the site / model required.
This all works fine for an online build, however when using prestage media, even if we include the packages in the image (ie. in c:\sms\pkg\<packagecode>) through the prestage media wizard, the package data is still retrieved from an SCCM server which may be across a WAN connection. There is currently no way to force the installation of packages from the local disk when using dynamically assigned applications or packages.
We have spoken to Microsoft regarding this issue and it has been confirmed that this is indeed the case.
Our solution works globally using seperate task sequences for Windows 7, 8.1 and 10 and using individual task sequences with assigned applications and packages is just not an option due to the numnber of sites and devices covered.
There is an existing request for something very similar here - https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8341257-support-installation-of-packages-apps-via-dynamic - howver this refers to standalone media not prestage media.
Thanks for the feedback, updating status to Noted.
Anton Burgess commented
Hi there, I have been running some tests within our environment and have found that although defined steps within the task sequence for applications and packages do indeed install from the local cache, if applications or packages are installed via a dynamic list based on a variable, the content is downloaded again from the distribution point. Could you please include a fix for this in the next version of ConfigMgr.
I am a developer in ConfigMgr team. We fixed the issue when Install Application task did not use local Prestaged Media content for application content and downloaded it from a DP instead. The fix should be available in 1610 release of ConfigMgr.