Check for running .exe, give the User the option to postpone
It would be nice to have an integrated solution for that. I would like to have the option to add the programs ".exe" names to the application in sccm. during deployment, if the .exe is currently running, it should ask the user to close it or give the options:
- postpone deployment
- close the application and start update immediatly
if the .exe is not running, it should just go ahead and install it without asking.
and also a silent version of this: check if the .exe is currently running, if no -> go ahead and install. if it's running -> try again another time.
and yes there are some powershell solutions available for that, but it would be nice and easier to have an integrated solution
There are many comments on this feedback item. We’ve read over them many times while building this feature and feel that we’ve hit the core functionality for this request in the 1702 release and so today we are marking this feedback item as complete.
We look forward to all of your passionate commentary, and votes, on the parts of this feedback that aren’t included in the current release to help us decide where to focus our efforts next.
As always, thank you for your passionate support and feedback.
maybe make app deployment toolkit avaiable for all applications native.
Michael Griswold commented
Allow a customizable UI message to be displayed prior to application installation. This could be to warn users to close open apps and similar scenarios.
+1 well it would also be nice, if the execution of this application would be blocked until the Installation is finished.
I would like to postpone a reboot if a process is running, wait for the process to complete before the restart happens or restart the counter at a smaller number and keep recycling until the process completes. Then reboot
Glenn Turner commented
This would be amazing! It would certainly help us to get our Java updates out a lot quicker.
You'd also want to check that the app isn't running when doing an uninstall via supersedence.
Brian Purdy commented
Let me add to this idea:
1. While waiting for the running .exe (or other process) to complete, allow admins to set a countdown of hours or minutes to wait until killing the process. Most users don't work more than 8 to 10 hours at a time.
2. Add the ability to monitor multiple processes, separated by a semi-colon.
Nick Gailfus commented
I'm currently looking into using Powershell App Deployment Toolkit for this. But it would be nice if it was native.
Christian Knutsson commented
This would be immensely useful for anything IE or Office related, as well as many other applications that usually running most of the time that a client is online.
well it would also be nice, if the execution of this application would be blocked until the Installation is finished.