Task Sequence Pre-Cache for all Packages inside
It would be nice to have the ability to conditionally pre-cache all packages in Upgrade TS and not only OS Upgrade step.
To describe it in more details, in current design we are able to pre-cache only OS Upgrade step to computers based on conditions. This is not enough for companies with 20+ languages as best approach is to create en-us core image and then apply MUI on top of that. Doing this will cause system to report as e.g. de-de so we would need to download and distribute to 150+ DPs all supported Upgrade packages instead of distributing only en-us Upgrade package and them distribute much smaller MUIs.
As SCCM is currently supporting conditional pre-download in OS upgrade step so the function is already there, extending it to whole Upgrade TS will be a great benefit as we can then also put there e.g. Driver packs => so client will download only applicable driver pack, en-us Upgrade and appropriate MUI from one larger Upgrade TS. Right now we have to have 50 different Upgrade TSs to be able to support all languages in our company.
Updating status to Started.
SCCM 1904 Technical Preview is now released.
For more info:
This Technical Preview contains changes for task sequence pre-cache.
OS Images can be set for pre-cache – these follow the same properties as OS Upgrade Packages.
Driver Packages use the Model for determining if the package is to pre-cache or not.
Select * from Win32_ComputerSystemProduct where Name like “yourentry”.
There’s also a new column added for both objects showing the download rule.
Very much a work in progress, Packages are to be completed. Then the Create Driver Package wizards needs to be able to set the properties, PowerShell to be completed
Note: for testing, I know most Tech Preview is in small labs on virtual hardware. For testing using ‘Virtual Machine’ as the model name works fine, the content will go to CCMCache.
Adam Absolon commented
Hi Bob, big thumbs up to your team for adding it to latest TP & include driver pkgs and OS images, I will try it ASAP! :)
Aravinth Mathan commented
If implemented for all objects within TS, reduces upgrade time a lot!! My users can smile and upgrade over a coffee break without any delay
RE: I would say that it is still not implemented as if it would be then the status will be different. But that is something for MS guys to answer, Bob?
That's correct, pre-cache is limited to OS Upgrade Packages for now.
Adding the additional properties to Driver Packages is a small part of the work required to pre-cache Driver Packages, there's quite a bit of additional work with Content transfer, ExecMgr etc.
The additional properties were added to help manage deleting packages when there's no corresponding model in the environment.
I've no update for adding pre-cache for other objects.
Adam Absolon commented
I would say that it is still not implemented as if it would be then the status will be different. But that is something for MS guys to answer, Bob?
I'm wondering if this is now working as SCCM 1810 has the option to specify model and manufacture for driver packages.
Nectarios Gritzalis commented
Since Pre-Caching is already being validated/actioned for OS Upgrade packages in the TS, why not just also have an option that flags the pre-caching need in the "Run Command Line", "Install Package ", and "Install Application" step to allow these particular TS steps to also be pre-cacheable if desired, assuming the WMI condition is matched.
This would simplify everything greatly since customers like us with 40+ HW models don't have to run separate TSes just to pre-cache the appropriate drivers, packages, etc..to the different models and not everything for all hardware models as "Download all content before starting task sequence" currently does.
It would be big improvement which would facilitate the administration.
Chris Jonait commented
Absolutely love this idea!
Pavol Hevier commented
This would be great feature!