Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

PDQ Deploy says "Successful" but installation failed - how to troubleshoot?

I have downloaded a trial of PDQ Deploy and have successfully installed three programs with no problem on network computers but one program fails every time I try it. I get an email that says "successful" and the console also says "successful" but the program fails to deploy. I can go to a user PC, open an elevated DOS prompt and paste in the exact same command and switches and the program will install fine.

How can I figure out why it does not work with PDQ Deploy?



Date Votes
  • Hi Wires382,

    Here are a couple of ways a deployment may finish as successful: 1) The Error Mode is set to continue in the deployment's Options tab for one or more steps and 2) the installer returns a successful code even if it fails. It's the second one that is harder to figure out. It could be that it's programmed to always return the successful install code. It might call another installer to install a program or configure settings that are required to run that is failing, but this failure is not being returned by the main installer.

    PDQ will only copy the install file to the local PC. So if it needs additional files, the install may not work correctly. You can select additional files to be copied on the step that runs the installer on the Details tab. You can also write a script to call the installer from the UNC path and the installer will have access to any additional files it needs in that same path since it will run from the server. There are pros and cons to both solutions and you have to find the one that is right for the deployment you are running. A command/batch script would look something like this:

    @echo off
    :: This script will run the installer from the server using the parameters you specify and exit with the return code of the installer.
    :: I like to show the script name and some basic information for when the script is run manually.
    echo.Running %~n0 - Installing ProgramName. Please wait...
    start "" /wait "\\server\share\path\setup.exe" /s
    exit %errorlevel%
  • There is also this PDQ documentation that might be useful:

  • MinutemanHS - thanks much for you replies. I used your exact script in PDQ Deploy with the path to my install batch file and PDQ Deploy says successful, but the target computer uninstalls the old version of the program and then hangs with msiexec showing in processes all night long until I killed it - but the new version of the program does not install. I ran the exact same batch file from the computer and the program installs perfectly.

    Any other suggestions?