Select Page

Summary

This document lists a number of commonly used examples of creating packages for software installers and is aimed at Science IT staff or those people wanting to use and create  software packages.

SCCM uses packages to distribute software to staff and student machines. A package is a software application to be installed on a  computer, but it might also contain individual files, updates, or even an individual command.

Also you can use GP to install the package on the pc.

What can I use to create a software package?

Installing software or updates with packages involves creating a Microsoft Windows Installer file (msi installer). An msi file is essentially an installation package used when you want to install, update or remove software on a Microsoft Windows system.  The installation package contains all the information needed to install a particular software component.

For example:
msiexec /i "%~dp0openafs-en_US-1-5-25.msi" ALLUSERS=1 /qb /lvx* "%temp%OpenAFS.log"
msiexec /i "%~dp0openafs-en_US-1-5-25.msi" transforms="%~dp0csAFS.mst" REBOOT=ReallySuppress ALLUSERS=1 /qb /lvx* "%temp%OpenAFS.log"
msiexec /u "%~dp0openafsUpdate.msu" REBOOT=ReallySuppress ALLUSERS=1 /qb /lvx* "%temp%OpenAFSUpdate.log"

 

WISE installer

Wise is another application that you can use to create packages for Windows software installations.

The link below contains some useful information.

Setup.exe /s

 

Inno installer

Inno is a free installer for Windows programs.

The links below contains some useful information about using Inno.

setup.exe /VERYSILENT /SP- /SUPPRESSMSGBOXES /NORESTART /MERGETASKS=”!desktopicon” /LOG=”%temp%setup.log”

 

InstallShield installer

InstallShield can be used to install software on desktop, server platforms,as well as  mobile devices.

The link below contains some useful information about using InstallShield.

http://unattended.msfn.org/unattended.xp/view/web/40/

1. setup.exe -R

2. The setup screen will appear normally. Steps through the installations.

At the end of the installation, setup.iss file will be created in C:Windows

3. Copy the setup.iss to the same folder of the setup.exe

4. Unattend install using setup -s

OR

setup.exe /S "/v /qn REBOOT=ReallySuppress /lvx* %temp%setup.log"

OR

setup.exe -r [-f1"%~dp0setup.iss"] [-f2"%temp%setup.log"]

 

 

-r     Record a silent installation response file (By default it saves setup.iss file to Windows or Winnt directory)

-f1   Name of the silent response file being recorded. No space is allowed between -f1 and the file.

-f2   Name of the result log file. No space is allowed between -f2 and the file.

Example of [Remedy silent installation http://documents.bmc.com/supportu/documents/57/19/65719/65719.pdf]

 

Nullsoft (NSIS) installer

setup.exe /S /D=path

eg. setup.exe /S /D=C:Program FilesTest

(Don’t put any quote around the path)

Nullsoft (NSIS) version 2 installer

/S = Silent install

S=start menu icons, F=file association, Q=quicklaunch icon, D=desktop icon, R=fake registration, A=run winamp agent/set default

 

eg.

winamp50*.exe /S /install=SFQDRA
Skip to toolbar