Extend "Model" field to Packages & Applications for Pre-caching of Task Sequence content
The new Model field on drivers is useful, but needs to be extended to other content types, like Packages & Applications, where Model specific items need to be installed (e.g. specific HP SoftPaqs, or video drivers that need to run from .EXE etc).
Thanks for your feedback and suggestion – updating status to noted. See https://docs.microsoft.com/en-us/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.
I would add that some drivers require setup to runs, which I usually create as a standard package for simplicity.
Jeff Poling commented
Pre-caching content for a task sequence is great, but we do not use driver packages for installing drivers in a task sequence. We use normal packages and the download package content step. This is true for in-place upgrades as well. As it works right now, when running an upgrade task sequence, the client downloads all of the packages for drivers, regardless of whether they are needed for that particular model. It would be nice to have a way to specify which package containing drivers gets cached for a particular model.
William Bracken commented
This a two part request actually
1. The ability to use the content already downloaded into the ccmache folder, rather than duplicating the required disk space by copying the content from ccmcache to _SMSTaskSequence\Packages during the TS execution.
2. The ability for an in place upgrade Task Sequence with Pre-caching enabled to run the option checks on the TS steps (like WMI queries for driver packages) so that the device only downloads what is needed to run the upgrade on that device
The amount of additional disk space/network bandwidth required for both of these scenarios is magnitudes larger than it needs to be to complete the upgrade.