If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
No, we don't have a command line method of automatically killing the process. Since it is currently running, the user is assumed to be interacting with it, so we want to warn them they would lose their progress. You could kill any BCompare.exe processes running before applying the upgrade, but this might be disruptive to the user and could result in losing edits or stopping in progress copies, etc. If performing an update running a Setup.exe /silent, they would see the prompt to close their application, and could then accept and continue.
No, we don't have a command line method of automatically killing the process. Since it is currently running, the user is assumed to be interacting with it, so we want to warn them they would lose their progress. You could kill any BCompare.exe processes running before applying the upgrade, but this might be disruptive to the user and could result in losing edits or stopping in progress copies, etc. If performing an update running a Setup.exe /silent, they would see the prompt to close their application, and could then accept and continue.
The plan was to update everyone overnight with SCCM under the SYSTEM context so no prompts will be shown to the end-user. So my understanding is that we need to kill the process ourselves if we want to silently update every older instance of Beyond Compare?
Thanks for the assistance.
Correct, you can look for the BCompare.exe process to end task if you assume the program is running. Or you could issue a reboot (which would kill any open tasks) and then issue the install. We don't have an internal method to silently end task without user interaction.
Comment