deploying a batch file - says failed even tho it was a success

0

hi all,

im deploying a batch file on a target pc using pdq deploy and its a success even tho pdq deploy console says its failed

i know its a success as i rdp into the target pc and i have seen its installed in add/remove programs

heres my bat file -

start /wait msiexec.exe /i \lon-p-pdq\pdq\lpw\LightPointWeb_6.1.1.msi /passive /norestart

start /wait \lon-p-pdq\pdq\lpw\LPWAutoConfig-London.exe

thanks, rob

Cancel
login to comment
0

Hi Rob,

What return code are you getting when you run that package? That may help glean some information as to what - if anything - is going wrong. It could also just be a case of a non-zero success code, since PDQ's batch file step only accepts 0 as a success by default. If your installation is returning 3010 for example, that would mean the installation is successful, and it just needs a reboot to complete. You can make PDQ mark the installation as a success then by just adding the code 3010 into the Success Codes section of that step.

Cancel
login to comment

0

Hi,

it runs and it normally takes 39 seconds for it to install lightpoint as all the time on the target pc i keep on refreshing add/remove control panel and it appears in there after 39 seconds

i abort it as if i dont it just continually runs (until the pdq timeout which is 60 minutes)

i dont get any error code as im aborting it

here is the screenshot -

enter image description here

thanks, rob

Cancel
login to comment

0

this is interesting my last line i have put this

if %errorlevel% eq 0 exit /b %errorlevel%

but in pdq deploy its still running even tho my .bat file has exited, i know this as i see light point web in add/remove programs

how do i get my bat file to exit after a succesfull installation, maybe if i get this right, pdq will mark it down as a success

Cancel
login to comment

0

If you separate those two lines into individual steps, that could help narrow down the issue a bit more as you'll be able to see based on the step which part of the installation is getting stuck. I'd recommend putting the msi into an install step itself rather than wrapping it in a batch file too.

Generally though when you see an installation running indefinitely on an .exe it's because you're missing some silent install parameters, and I'm guessing the hang is on that second line. /s and /q are the most common silent switches, but you should be able to find which ones to use in the product's documentation.

Cancel
login to comment

Reply