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.
Marty List commented
This seemed like such a great enhancement, and we were really looking forward to using it. Too bad it's so buggy and unpredictable, most of the time it works on lab VMs but users just get the horrible looking error code 0x87D00443, even on 1906 with KB4517869.
Thx Adam. Show notification for new deployments is enabled in my Client Settings.
The notification is shown only when users hit the Retry button in the Software Center. My deployment is in required mode. Maybe it's by design.
Adam Juelich commented
Be sure you have 'show notification for new deployments' enabled in your Client Settings under Computer Agent.
The new software center just gives an error code 0x87D00443 without further details. We need users to be notified and the warning should show all applications that need to be closed before installing. This need to be patched.
In an appx deployment the tab is not there?
Michael A. commented
Can you improve the message. Just add an additional button "Close application and Re-Run".
The users will never close the application, searching for the software center, searching for the application and the button "Retry".
Pierre Rondeau Manningham commented
Would it be possible to extend this feature to uninstall commands? We have some applications that refuse to uninstall when specific processes are running so it would be useful if SCCM could detect and kill the process when needed.
Stephen K. commented
The behavior in 1702 is different depending on if using the old or new software center. The old software center gives a nice display when clicking on the failure reason, saying close the following applications. The new software center just gives an error code 0x87D00443 without further details.
Would you be able to add this "install behavior" EXE check for Packages and Task Sequences? The Application portion is awesome but having it available for Packages and Task Sequences would be so beneficial. We utilize a lot of non-OSD type Task Sequences and this dialog or prompt would be great. Thank you.
I agree with Frode F, this should definitely be an option. Just force closing an application seems a little over the top for anything that is required.
Frode F commented
There should be an option for the user to delay a required deployment if they are running an executable that needs to be closed. Either for 1 hour at a time and/or until the executables are closed. AFAIK the only option we have now is to let it fail and try again later (ex. every 24h depending on your application evaluation interval) or force close them which can be unacceptable for software like Citrix Receiver where you have no idea what the user is curently doing.
Would it be possible to also have the ability to select different styles of user notifications for prompting users that install or updated is needed? E.g. Give them a few chances to delay for x number of minutes or hours and after a limit is reached advise them that it is happening. Also, allow for varying degrees of message, eg a message box in the middle of the screen that cannot be moved. We have had to build custom scripts to do this for applications that require restarts or for applications to be closed. And also built another script for silent installs when no-one is logged on. If this logic could be built into SCCM for all applications that would be ideal. E.g. Silent installs for when no one is logged on and prompts that get more aggressive the more the user delays the update when a user is logged on. Also, if the user is logged on but has been idle for a long time. E.g. left it on overnight, force the closure of applications and saving of their data if possible and then update the application and reboot if necessary.
Technical Preview 1702 now includes this ability: https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1702
Matthew DeBoer commented
Stefan, I believe this should be merged with this:
(Just in case you want to add your votes to that one :-) )
So basically everything PsAppDeployToolkit is offering currently...
William France commented
I think this is a good start, but I think it would be better if you could associate the executable with a custom description of the application and possibly associate multiple executables with a single custom message (i.e. winword.exe, excel.exe, etc. associated with MS Office).
Not sure if I am describing this correctly, but see script excerpt below for how I handle this currently to get an idea of what I am describing:
' Check if applicable apps are running
Set oProcesses = oWMI.ExecQuery("Select * From Win32_Process")
For Each oProcess In oProcesses
Select Case UCase(oProcess.Name)
MsgBox "This application cannot be installed while Microsoft Office applications are running." & vbcrlf & vbcrlf &_
"Please close all Microsoft Office applications and then attempt the installation again.", 4112, "Error: Microsoft Office Applications Open During Application Installation"
MsgBox "This application cannot be installed while Nuance Power PDF is running." & vbcrlf & vbcrlf &_
"Please close Nuance Power PDF and then attempt the installation again.", 4112, "Error: Nuance Power PDF Open During Application Installation"
MsgBox "This application cannot be installed while Adobe Acrobat is running." & vbcrlf & vbcrlf &_
"Please close Adobe Acrobat and then attempt the installation again.", 4112, "Error: Adobe Acrobat Open During Application Installation"
Qasim Mashwani commented
This feature is incomplete if the option to force the closing of the application is not included. Also, if force-close feature is to be included it is only useful if the close-application thread kills the entire process tree runs and runs in the system context regardless of the context of the deployment.
Roth, Chase commented
Doesn't show all messages mean it will keep telling the person "new software is available" each time they login also? I don't want that and it seems to do that in my older version (2012 R2 CU3). Maybe that is not an issue with TP/CB. That is a bit off topic though...
However, I do want to the prompt to work when install is initiated by the user. If not initiated by the user it should not prompt, as in a forced install during a Required deployment.
Sascha Stumpler commented
@Jonas: I had to change the Deployment visibility option to show All Messages and Notifications from the default option to show only messages for reboots and errors to see the notification.
I just tested the feature and put notepad.exe in. But i dont see any window saying i should close notepad. Instead the app install fails and is showing an 0x... error. Is this the expected behaviour?
A window with the exact app name would be better for the end user