Kdyer
(KiX Supporter)
2003-01-14 08:12 AM
How do we deploy an application? - InstallShield and others

This may also be of interest to you - Install Packagers

{Edit}
Removed the %COMPUTERNAME% information. However, you should insure that either the WEFCNAME.INI or the Registry is updated with the @WKSTA variable.
{/Edit}

Topic originally discussed at - Citrix Client Silent installer

Thanks for the feedback of Les, Rad, and Jens on this.

Citrix Client Silent installer
Please refer to: http://www.winnetmag.com/Articles/Index.cfm?ArticleID=7965
(1) Download the ICA32.EXE from http://www.citrix.com or use similar site/application.
(2) Use WinZip or similar program to extract the files from the self-extracting archive.
(3) Create the SETUP.ISS file by running the SETUP.EXE with a -r switch
When completed, you will find the SETUP.ISS in your Windows Directory. You can then copy this file to the install folder.

Note: Users will need to have Power User rights or better to run this

Installshield Switches - Thanks Jens!
Ref - http://www.appdeploy.com/tips/detail.asp?id=18

-f1[path\ResponseFile]
Specifies an alternate location and name of the response file (.iss file).
If this option is used when running InstallShield Silent,
the response file is read from the folder/file specified by[path\ResponseFile].
If this option is used along with the -r option,
the response file is written to the folder/file specified by[path\ResponseFile].
If an alternate compiled script is specified using the -f switch,
the -f1 switch entry must follow the -f switch entry.

-r
Causes Setup.exe automatically to generate a silent setup file (.iss file),
which is a record of the setup input, in the Windows folder.

-s
Runs InstallShield Silent to execute a silent setup.

-SMS
Prevents a network connection and Setup.exe from closing before the setup is complete.
This switch works with setups originating from a Windows NT server over a network.
Please note that SMS must be uppercase; this is a case-sensitive switch.

-z
Prevents Setup.exe from checking the available memory during initialization.
This switch is necessary when running a setup on a machine with more than 256 MB of memory; if it is not used,
Setup.exe reports insufficient memory and exits.

Example, we used to deploy 40 Workstations over the weekend that moved from our Corporate Office to a remote location.
Code:

BREAK ON
CLS
$windir = READVALUE('HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion','SystemRoot')
$systemdrive = SUBSTR($windir,1,2) ; -- This will show C: or M: or what drive Windows is installed on
$PathString = '\\APPSERVER\Apps\Citrix'

IF exist($systemdrive+'\Program Files\Citrix\ICA Client\pn.exe')
RETURN
ELSE
'Citrix is being installed. Please wait..'
SLEEP 3

RUN("$PathString\disk1\setup.exe -s -SMS -z -f1$PathString\setup.iss ")
RETURN
ENDIF




Kdyer
(KiX Supporter)
2003-07-09 02:17 PM
Re: How do we deploy an application? - InstallShield and others

Originally discussed here - install links... for FAQ

Unattended/Silent Installation Switches for Windows Apps
This covers:
  • MSI packages (*.MSI)
  • InstallShield
  • PackagefortheWeb (PTFTW - From InstallShield)
  • Wise InstallMaster (or just simply WISE)
  • Inno Setup
  • Nullsoft Scriptable Install System
  • Microsoft hotfixes and older packages (i.e. Qnnnnn.EXE)

Other ways to approach the installer are discussed here too.
Superior RIS: Automating Application Setups > RIS is "Remote Installation Services"
Deployment
Microsoft OEM System Builder

What Command Line Switches Are Supported? Windows Installer

227091 - Command-Line Switches for the Microsoft Windows Installer Tool (MSIEXEC)