We made some changes in the TS step for App Deployment, that gives you more control over cache. Try this out in #SCCM TP 1906
Updated to Noted. We’ve been discussing the same in our planning meetings.
BobMN on behalf of SangeeV for SCCM OS Deployment
1,988 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.
105 votesGreg DeGuire commented
This has been possible for years.. (note there is a known issue with this occurring in a TS, but you can get it to work)
What you need to do is send a mandatory time in the future and suppress the notifications, and the ability for the user to on their own. When the client checks in next, it will see that it has osmething to run in the future and will download the source files ahead of time. Then, at the time you want/need it to run (say to correspond with a database/server change, for example), then just change the future mandatory date to whenever you want them to run. This will cause the install to occur from the pre-cached source at the time specified or, if the change in mandatory date took place over the weekend and the machine was offline, it runs as soon as the date change is picked up since, presumably, its now changed to a time in the past.
Works with Applications too but youll need to throw a step in there to run something like cmd.exe /c right away, and then another step for the actual install.
Again, beware of the TS bug that is going to be fixed in 1610...
Test it out.. good luck.