Updating status to started.
The first iteration/slice of this is available in the 1905 Tech Preview.
1,950 votesstarted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
I’m re activating this one based on the fact that we don’t show the intrusive reboot countdown after the software was installed. We still have some work to do here to make this experience meet the requested behavior.David Grand - Systems Engineer at NWEA commented
Why is this still an issue. This is a very simple request. Allows SCCM Admins to send Dismissable messages about Restarts. The "toaster" notifications are really no notification in our environment.
Updating status to started – see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of values.
Our 1906.1 Technical preview is released today and contains changes to address this ask. On the Install Application steps there’s a new checkbox ‘Clear application content from cache after installing’.
This can be used for static or dynamic App install and is per step not per app so if you’ve been using the 99 max. you may want to refactor your task sequence to use multiple Install Application steps.
For more info:
Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Filter-apps-deployed-to-devices-in-ConfigMgr-Technical-Preview/ba-p/688881David Grand - Systems Engineer at NWEA commented
I am seeing the same issue with in place operating system updates (like going from Win 10 1511 to Win 10 1709) where our users are failing due to too many old items in the cache. And we don't persist ANY content in our cache so I am not sure why stuff is hanging around so much in ccmcache.