31 votesPhil Brandvold commented
This definitely needs to get fixed. I was extremely exited to use powershell scripting detection method, but I need to run Get-AppxPackage, which requires elevated permissions. The feature was *this close* to solving many problems for me (we use the Software Center to deploy quite a few Windows features and other settings with powershell scripts, and right now I'm having to create registry keys every time to mark that an installation has been made).
176 votesPhil Brandvold commented
This feature's unavailability is killing us right now. It's not about network speed, it's about hard drive space. Solidworks requires 15-20GB of free space to install already, and now you want me to free up 18GB for the install package itself? What's the point of that? We need to be able to install from a network location, and we need it yesterday.
1,270 votesplanned · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
Updating this one to planned. We have work in this area that should address the general set of comments that are in this suggestion. While we aren’t doing the NEVER reboot, we definitely hear you that you need more than a 24 hour window. We should have more details to share in the next TP so stay tuned for updates soon.
1,985 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.
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