/bundles/itninjaweb/img/Breadcrumb_cap_w.png
I need to install GlobiLab software (globisens.net/support) on some staff Windows laptops, and I'd like to push this out silently through our K1000 appliance.  However, when I'm testing it out through the CMD window on my test computer (not bringing KACE into it yet - just figuring out the right switches/syntax), I can't get it FULLY silent.  I only have an .exe file and haven't been able to extract any .msi from it.  I've requested an .msi from the software company but haven't heard back yet.  I can't even find a readme file from them...

Anyway, at a command prompt, just typing GlobiLab.exe /s, I get the UAC prompt and a window asking to select my Language.  After that it installs the rest silently.  I've tried a few different combinations, such as /s /sms, /s /sms /f2Globilog.log, /Silent, /qn, /s LANGUAGE="English" to no avail.  I don't see an .iss response file either.

I configure random programs to install through KACE occasionally, but lots of time passes in between and it seems like each time I have to go back and re-try all these different methods until something works.  

Any suggestions on how to make this completely silent so the end user doesn't need to respond to any prompts?
1 Comment   [ - ] Hide Comment

Comments

  • When you try to run your silent installer, are you only running it through a Command Prompt where you selected "Run As Administrator"?

    When testing the app as it would deploy under KACE with "run as system" selected you will need to use PsExec or something so you can run your installers under the System account so you can debug your install script.

    -- Download PsExec and install.
    -- Open an elevated command prompt
    -- Navigate to PsExec.exe and run "psexec.exe /s cmd.exe"
    -- Confirm you are running as the system with "whoami"

    Also, it sounds like that program is using Install Shield. Did you run Setup /r first to record the setup.iss response file?

    http://publib.boulder.ibm.com/tividd/td/framework/GC32-0804-00/en_US/HTML/instgu25.htm
Please log in to comment

Answer this question or Comment on this question for clarity

Answers

0
Have you tried UniExtract? It's reasonably good at divining what installer was used to create the EXE.

Failing that, why not use the free AppDeploy Repackager to repackage it as an MSI?
Answered 01/26/2018 by: VBScab
Red Belt

Please log in to comment