Deployment always marked as successful even when it fails
Hello,
I have created a package and can successfully deploy it with PDQ - everything works very well.
This software is developed in-house and is updated weekly. The plan is to push the deployment once a week to update the software already installed.
When installing the software manually, if the software is already running, the installer pops up a window saying the software must first be closed and offers options to either end or close and continue.
When deploying, if the software is already running, the deployment finishes with error code 0 as if the installation was successful when in fact it was not.
Any idea as to how this should be handled?
I know in the pro version we could check for a process that is running, but I am still experimenting with the free version and building a use case for management.
Thanks,
Samuel
Comments
In free mode I'm a little fuzzy on their meaning of "Multi-Step and Nested package" from the Compare Modes table.
How are you deploying your application now? An Install Step? Is there any chance you can call it from a Powershell script? If so:
If(!(Get-Process [app_process.exe]) {
Start-Process yourappinstaller -ArgumentList 'your', 'args' , 'here' #comma separate and parenthesis your command line arguments
}
Else {
Stop-Process [app_process]
Start-Process yourappinstaller -ArgumentList 'your', 'args' , 'here' #comma separate and parenthesis your command line arguments
}
This assumes you can call the installer from a UNC path, or add some logic to this to copy the installer locally, run it, then delete the installation file(s) afterwards.
@Samuel
You can request a trial license if you want to try out Enterprise: https://www.pdq.com/try/
@Stephen Valdinger
We recently updated that page. Can you please take another look and let me know if it's still confusing?