AdobeAIR, Polycom Desktop Scripted install - MSIEXEC freezing
Ive been scripting an install of Polycom CMA Desktop, which requires AdobeAIR as a prerequisite, and have run into a bit of trouble. Script is below:
start /wait AdobeAIRInstaller.exe -silent -eulaAccepted
start /wait PolycomCMADesktop.msi /qn /norestart SBSERVERTYPE=2 SBSERVERADDRESS=[cmaserveraddress]
running the batch file manually will install without issues... mimicing the system account (ala https://www.kace.com/support/resources/kb/article/How-to-mimic-running-a-script-as-Local-System-User-Scripting) and running the batch will isntall without issues. But when its run via KACE, AdobeAIR will install but then it will not install CMADesktop. Looking at the taskmanager, I can see that MSIEXEC is running, but seems to be frozen.
Ive tried a few different workarounds to get it running, like putting a PING command inbetween the installers to delay the second install, but it wont progress past the first install, MSIEXEC still running and PING command wont start.
Ive tried swapping the order of the installs, but i seem to see the same issue here (CMADesktop will install, msiexec will freeze, then AdobeAIR will not start). Dont see this problem with any other similar scripts we use.
Ive even tried using a taskkill command after delay, to try and kill the MSIEXEC, so the next install can progress, but this doesnt work either.
Im a bit stuck for ideas right now, has anyone seen similar issues? or have any other suggestions to get this script running?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
pjgeutjens
12 years ago
First things first, have you tried adding logging to the msiexec command in your script? This should give you a starting point for troubleshooting.
Also, try replacing /norestart with REBOOT=ReallySuppress
Comments:
-
thanks for the suggestions. I have tried changing the Reboot switch and removing it completely, makes no difference.
Ive also enabled logging on the cmadesktop.msi, when the installs are in the order above, it doesnt leave a log at all, it freezes after the first install. when the order is changed, then it leaves a log for CMADesktop, no errors, 'installation completed successfully', but the script fails to continue. AdobeAIR is not installed, and msiexec is frozen when looking at the taskmanager.
Event Viewer also reports that it was installed successfully.
we have quite a number of installation scripts on our K1000 now, and this is the only time ive seen this problem. all the others are running fine - rjonesdj 12 years ago -
Instead of the AirInstaller.exe , what happens if u use the vendor msi directly ? the exe does install the msi itself , I just packaged Adobe Air 3.4.0.2540 and used the msi directly . Did not find any significant diff b/w the exe & the msi - hrs2cool 12 years ago
-
how did you package the msi? ive extracted the exe, but havent been able to run the msi alone. keeps returning errors ("cannot find ....") do all the files contained in the exe need to be deployed along with the msi?
did you use a transform file? or just msi switches? - rjonesdj 12 years ago-
I created a transform for the setup.msi . Yes all the files have to be kept along with it. External Uncompressed Files. - hrs2cool 12 years ago
-
sorry to bug further with this, what changes if any did you make to the tables when creating the transform?
Ive attempted creating one with Orca, but when running msi with the mst get the error "Could not access network location (computed)."
All files are located in the one local location, no network locations involved - rjonesdj 12 years ago
-
"%~dp0AdobeAIRInstaller.exe" -silent -eulaAccepted
:: Wait for 10 seconds
ping -n 20 127.0.0.1 > NUL
"%~dp0PolycomCMADesktop.msi" /qn /l*v "%temp%\test.log" REBOOT=ReallySuppress SBSERVERTYPE=2 SBSERVERADDRESS=[cmaserveraddress]
y dont you give the above shot by removing start /wait !!! and Making the current directory with %~dp0 - ontari.ontari 12 years ago -
thanks for the suggestion, tried changing my script to follow your method but again same issue.. - rjonesdj 12 years ago
Posted by:
jagadeish
12 years ago
Can you try this?
start /wait AdobeAIRInstaller.exe -silent -eulaAccepted
start /wait msiexec / i PolycomCMADesktop.msi /qn /norestart SBSERVERTYPE=2 SBSERVERADDRESS=[cmaserveraddress]
Comments:
-
thanks for the suggestion, i have already tried calling the msi that way, but unfortunately see the same results. thanks - rjonesdj 12 years ago
Posted by:
hrs2cool
12 years ago
Logging is definitely the way to go. ALternatively just try to remove the silent commands in both or the second one to see if u can get an error
Comments:
-
id hoped that too, but tbh the logs havent been helpful so far, dont report any problems at all.
ive tried removing the silent switches, but that seems to make things worse, first exe fails to install, and then the rest of the script fails to carry on. Hoped id be able to actually see what was freezing on screen, but as they are running as SYSTEM account, i guess, i still dont get to see whats actually happening.
either installer alone, scripted will install fine, but theres still one MSIEXEC lingering in the Task Manager by SYSTEM account.
no matter which order they are installed in.. and happens for both of these installers (one is exe one is msi) when run alone,
have created a number of scripts before, including entire PC build scripts which install multiple msis and exes and have never run into this before - rjonesdj 12 years ago
Posted by:
rjonesdj
12 years ago
I managed to resolve my own problem. but the resolution is just as boring as it was annoying to be honest.
I got hold of a slighty older version of the software 5.1.x which seems to not required Adobe Air (was trying to use 5.2.x)
Now the script is as simple as it gets:
start /wait CMADesktop.exe /S /V/QN