Option to pre-download content to client cache for 'Available' deployments
As we know, 'Required' deployments download content to client cache as soon as possible assuming content is available and req's are met. A common scenario is setting a deadline off in the future which essentially stages or pre-downloads the content to the client cache so it's available as soon as the user hits install, or the deadline is reached.
We'd like an option, per deployment, to pre-download content in a similar fashion for 'Available' deployments.
Understood that available deployments may never get executed, but there are several scenarios (poorly connected, remote offices w/no DP) where this would be extremely desirable. (With the proper client cache size/mgmt.)
Even with Branch Cache, at a minimum the first client to request content for an available deployment still needs to wait for the download from a DP. In some cases this can be very slow, and some scenarios can't afford for users to wait at all.
Lastly, faking this by using required deployments with deadlines years in the future does get the content staged, however it introduces other user experience issues in Software Center related to a required deployment such as confusing status and the inability to use the uninstall button.
Dave Hoppert
shared this idea
AdminBob Mac Neill
(Software Engineer, Microsoft Endpoint Configuration Manager)
responded
Hi. I’m updating to status=complete for our 1706 release – https://blogs.technet.microsoft.com/enterprisemobility/2017/07/28/now-available-update-1706-for-system-center-configuration-manager/
Improvements for this scenario for Task Sequence/OS Deployments and OS Upgrade Packages include a new condition for language comparison and controls for selecting language rather than entering an LCID. This moves away from having to use a WMI query
These changes don’t address the asks for extending the same pre-cache functionality to Applications, SWD etc., closing this item will return your votes, please use them to add a new User Voice request
Thank you all for all your feedback and suggestions
14 comments
-
George Simos
commented
What the implementation does for the TS is not helpful because it:
1) Downloads payloads to the CM Cache
2) Copies the previously cached content to _SMSTASKSequence folder and we end up having the same content in two places.
It will be removed when the TS completes from _SMSTASKSequence but it will remain in the CM Cache, this isn't helping when doing In-Place Upgrades of Windows.
Especially when you are tight in space.... -
Michael
commented
This is not completed, you merged two separate requests together and only did half of them.
-
Nick Greeley
commented
This really shouldn't be marked completed. You addressed the TS model, however, most of us would like to see this for the Application/Package model. Reading the original user request, he did not specifically request the TS model, so to say it's completed and we have to re-open if we want some other area is deflecting on the original request.
-
Matt Schultz commented
Hoping to see this added to applications and package/programs as well.
-
Shaun Usman
commented
We would like to see this implemented for applications as well. For example, we have created some scripts that users can run from Software Center to perform tasks that would normally require admin privileges, and would like users to be able to perform these tasks when they need to, including when they are not connected to the network. The option for Pre-caching these would allow that functionality!
-
Joshua Binney
commented
This needs to be an option in the Task Sequence deployment.
-
ASM
commented
In direction of the new "peer cache client setting" it would be helpful to be able to deploy content (only) to defined clients that are determined as an peer cache client to play as a content hub.
-
dave hoppert
commented
According to the TP1611 release notes (comments section) this was only implemented for task sequence deployments... a good start.
Will this be enhanced to support all deployments (app/pkg/su)? Although not specifically stated... that was the original intent of my/this user voice submission : /
-
-
-
Harry Caskey commented
Have the ability to mark an application or package as pre-cached in the Task Sequence to a Device. So when the task sequence is initiated it will download all the packages that are marked as pre-cached. This way during the Task Sequence if a device can no longer communication with the SCCM server it can still complete it's task.
This would be very helpful for running an upgrade on a remote system that is connected over a VPN connection. Once the upgrade starts it reboots the system and is unable to communication back to the server. If there was an option to pre-cache the remaining packages it can complete the task sequence successfully.
-
Tom Wahab
commented
This is a great idea and task sequence will be so much faster!
-
Lawrence Lozzano
commented
Please add. Thks!
-
Mitch Beck
commented
Ability to allow SCCM administrators to pre-cache an entire task sequence with associated apps and packages to device collection. Along with this some logic to keep the cache updated as admins modify the selected task sequence programs and/or apps. I think this would be a big win with respect to network load and OS Deployment time. I'm sure this feature request if implemented can be expanded to many other use cases (i.e.: off-prem, or Wifi OSD jobs).