[wds] Software install .bat fails but succeeds if the exact same commands are run manually.

[Garacesh]

Trying to have the Adobe CS5.5 suite install as part of the image deployment. All of the relevant files are stored in the deployment share and the deployment share is mounted as Z: as part of the imaging process. During the 'Install Applications' step of the task sequence, one of the applications is a batch file containing the following script:

 

REM .msi's crafted with AAMEE expect explicit paths. ".\" will NOT work.

REM Install Adobe Acrobat X, pre-requisite to CS5.5
START /WAIT "Acrobat X Installer" msiexec.exe /i "Z:\Applications\Adobe Creative Suite 5.5\Exceptions\AcrobatProfessional10.0-EFG\AcroPro.msi" EULA_ACCEPT=NO REGISTRATION_SUPPRESS=YES SUITEMODE=1 TRANSFORMS="Z:\Applications\Adobe Creative Suite 5.5\Exceptions\AcrobatProfessional10.0-EFG\en_GB.mst" INSTALLLEVEL=101 AS_DISABLE_LEGACY_COLOR=1 IGNOREAAM=1 /qn

REM Install Adobe Creative Suite 5.5
START /WAIT "Creative Suite Installer" msiexec.exe /i "Z:\Applications\Adobe Creative Suite 5.5\Build\Adobe Creative Suite 5.5.msi" /qn

REM Install PDF Settings
START /WAIT "PDF Settings" msiexec.exe /i "Z:\Applications\Adobe Creative Suite 5.5\Exceptions\AdobePDFSettings10-mul\AdobePDFSettings10-mul.msi" ADOBE_SETUP=1 /qn

pause

 

This script, however, does not work. As far as I can tell, though, the issue is not with the commands themselves.

 

Due to the pause command the imaging process is halted at the end of this script. During this time, I can launch a new cmd window and paste in each command exactly as it appears in this script, and everything works as expected.

 

What gives?

 

Edit: Update: If I navigate to Z:\ etc and run the exact same batch file that the Lite Touch Installer launches, it works. WUT

 

Edited April 27, 2016 by Garacesh

[Fazza]

I would imagine the Lite Touch runs it with Administrator privileges. Try right-clicking the batch file and running as Administrator.

[Joanne]

try saving the script as a .cmd file instead. Sometimes Win 7/8/10 prefers cmd to bat.

[Garacesh]

I would imagine the Lite Touch runs it with Administrator privileges. Try right-clicking the batch file and running as Administrator.

The script works regardless of if it's run as an administrator or not. I've tested it manually as both, and it works. The issue isn't that LiteTouch works and the script doesn't - quite the opposite. LiteTouch fails whereas running it manually succeeds

 

try saving the script as a .cmd file instead. Sometimes Win 7/8/10 prefers cmd to bat.

Hm. Can't hurt to try.

[Fazza]

The script works regardless of if it's run as an administrator or not. I've tested it manually as both, and it works. The issue isn't that LiteTouch works and the script doesn't - quite the opposite. LiteTouch fails whereas running it manually succeeds

 

Oh I misread it!

[Garacesh]

Oh I misread it!

Yep, now you see why I'm so confused!

 

try saving the script as a .cmd file instead. Sometimes Win 7/8/10 prefers cmd to bat.

Nada.

 

Adding an ECHO %ERRORLEVEL% line after each command, let's see if that gives me any useful information...

 

Edit:

%ERRORLEVEL% is 1618: ERROR_INSTALL_ALREADY_RUNNING

That explains why it works "later on", though I'd have expected msiexec to not be running.

Previous steps are to install AntiVirus, and then .Net Frameworks 3.5 and 4.6, but I would've thought it would have finished installing those before proceeding to the next step..

 

The thing is, I can put other installers in front of this (if I select all of applications currently in WDS, the install order is MSOffice 2013, Visio 2013, then Adobe) that also use msiexec and they complete fine.

Edited April 27, 2016 by Garacesh

[Garacesh]

DEEEEEEEEEERRRRRRPP

 

Yeah, my bad.

 

I had the AntiVirus installer just as running the exe, not START /WAIT, so it would launch the exe and move on (thus having msiexec running and unable to spawn a new process)

 

Whoops