You could build a custom definition in patch and compliance which would give you the built in option to stop a process. If you wanted to use software distribution, there are a couple methods but what may be the easiest is to write a batch script using taskkill to end the process, and then either create a distribution bundle that runs your batch script first, or, you could just add the next line to the script to execute your software.
If you chose the latter option, then you would write a batch script that uses taskkill as the first command and then executes your MSI as the second command. You'd create a batch package in ivanti and add the batch script as the primary file and the msi as an additional file. The additional file will be copied to the sdmcache directory, so in the batch script you'd need to reference that path.
Let me know if that helps and whatever other questions you have.
I would use a powershell script to terminate the process. I think that you can use this in the actual software distribution, custom definition or group it in a scheduled task.
I had been looking for some way to integrate the command(s) into the package itself, but in the end (I'm still learning how LDMS works best) I just created a separate batch file package and bundled it in between the MSI uninstall and install packages. It's working great. Thanks for your suggestions.
The "good / bad" thing is (as I keep telling people) that there's pretty much always at LEAST 3 different ways of getting the same thing done. Personal preference & learning / knowing the product tend to help.
Take it at your own pace, and just keep at it. You're not going to run out of things to learn in a hurry - so do it at your own pace .