I hope someone can help as this has been driving me insane!

I've currently developed an RIS server for my company which rolls out different applications depending on what use the computer is for. There are 3 main types, Claims, Legal and Ensign. With a customised variable, the relevant script for each build is selected within the [runonce] heading of the .sif template.

So far so good.

I've managed to get one script to work perfectly, but it is quite uncomplicated and mostly deals with .msi installers.

The problem now is trying to use .exe installshields that don't seem to signal to the OS when the installation is complete, resulting in patches starting to install before the main programs have been installed etc. Below is my script...

cmdow @ /HID
@echo off

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY% /V TITLE /D "Installing Ensign Applications" /f

REG ADD %KEY%\005 /VE /D "Installing ODBC" /f
REG ADD %KEY%\005 /V 1 /D "regedit.exe /s %systemdrive%\install\odbc.reg" /f

REG ADD %KEY%\010 /VE /D "Faxclient 12" /f
REG ADD %KEY%\010 /V 1 /D "%systemdrive%\install\faxclient.msi /QN" /f

REG ADD %KEY%\015 /VE /D "Adobe Reader 7" /f
REG ADD %KEY%\015 /V 1 /D "%systemdrive%\install\Adobe\ar.msi /QN" /f

REG ADD %KEY%\020 /VE /D "Office 2003 std." /f
REG ADD %KEY%\020 /V 1 /D "\\serverris\Office2003\STD11.MSI /QB" /f

REG ADD %KEY%\025 /VE /D "Clearing .db File Association" /f
REG ADD %KEY%\025 /V 1 /D "regedit.exe /s %systemdrive%\install\removeDB.reg" /f

REG ADD %KEY%\030 /VE /D "Mapping Progress Install Drives" /f
REG ADD %KEY%\030 /V 1 /D "%systemdrive%\install\MapProgress.cmd" /f

REG ADD %KEY%\035 /VE /D "Installing Progress 91D" /f
REG ADD %KEY%\035 /V 1 /D "r:\setup.exe -s -f1q:\setup.iss" /f

REG ADD %KEY%\040 /VE /D "Installing Progress Service pack 5" /f
REG ADD %KEY%\040 /V 1 /D "t:\setup.exe -s -f1s:\setup.iss" /f

REG ADD %KEY%\045 /VE /D "Installing Ensign Live" /f
REG ADD %KEY%\045 /V 1 /D "%systemdrive%\install\EnsignVBS\CopyLive.vbs" /f

REG ADD %KEY%\050 /VE /D "Copying Directories" /f
REG ADD %KEY%\050 /V 1 /D "%systemdrive%\install\EnsignVBS\Copy2folders.vbs" /f

REG ADD %KEY%\055 /VE /D "Configuring Progress for Ensign" /f
REG ADD %KEY%\055 /V 1 /D "%systemdrive%\install\EnsignVBS\Copy1-3.vbs" /f

REG ADD %KEY%\055 /VE /D "Copying Files" /f
REG ADD %KEY%\055 /V 1 /D "%systemdrive%\install\EnsignVBS\Copy4Files.vbs" /f

REG ADD %KEY%\060 /VE /D "Cleaning Up and Rebooting" /f
REG ADD %KEY%\060 /V 1 /D "%systemdrive%\install\Commands\cleanup.cmd" /f


As you can see, the keys are added into the RunOnceEx node of the registry and once the computer has auto logged on, the application should install in order. This works fine in the other scripts but the main problem is the .exe installers and the moving of the files.

Now is it possible to either create .msi files from the .exe files or create an installer that will envelop the .exe installer and provide structure to the installation.

Oh and it has to be silent!


0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


bkelly just added the "InstallShield Setup Parameters" article/pdf on the command line support provided by InstallShield setups (MSI and InstallScript) here: http://itninja.com/blog/view/installshield-setup-parameters

Have a look at the "/s", "/SMS" and "/f1" parameters described in this article.
Answered 08/16/2006 by: AngelD
Red Belt

Please log in to comment
Thanks, the /SMS switch might just do it!

Answered 08/16/2006 by: steve.mccall
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity