A couple of tips: (as compiled by Torgeir Baklen)
Almost every MS system packages/updates/sequrity fixes can be made silent (but
often no documentation on how).
Almost every install that uses InstallShield can be made silent (I don't mean
the MSI version).
Also, with AutoItX (see further down), you can lock the mouse/keyboard so the
user can't interfere with the install (some limitations for old OS versions).
AutoIt/AutoitX can also be used for automating SW installs (but with *some*
important limitations)
For Runtime Install checkers/wrappers (this one can do a lot for you I think):
Take a look at "Launchers and Runtime Installers" here:
http://www.installsite.org/iswi/tips.htm-and-
you can try the free VB Setup Wrapper at
http://vbsw.giesler.org/MSI installs gives you a lot of possibilites:
A completely silent installation: q , qn (No UI), or just a progress bar with or
without a Cancel button: qb , qb- (Basic UI) . Use qb! to hide the Cancel
button, new in MSI 2.0.
To support multiple users on a PC, use the ALLUSERS=2 property on the command
line. Note: The install source (e.g. the original MSI file) must always be
accessible an the original placement if self repair kicks in for #2 user. Self
repair will start to e.g. create neccessary CurrentUser registry settings.
Here are some links (the links in my article at
http://communities.msn.com/WindowsScript/ doesn't work, MSDN has been redesignet
again):
MSI Command Line Options
http://msdn.microsoft.com/library/en-us/msi/app_73eb.aspMSI Error Codes
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/code_13ub.aspMSI Engine Redistributables:
Download for version 1.2:
INFO: MSI: How to Obtain the Windows Installer Engine
http://support.microsoft.com/support/kb/articles/Q292/5/39.ASPDownload for version 2.0:
Platform SDK - Redistributables
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdkredist.htmCommand line switches for v. 1.2 ( I guess it will work for 2.0 also):
Silent install with supress of reboot message (if any):
W9x: instmsia.exe /q /r:n
WNT: instmsiw.exe /q /r:n
(I think /q:a will also do the work for /r:n)
Software Installation and Maintenance
http://www.microsoft.com/windows2000/techinfo/administration/management/siamwp.aspQ227181 - How to Manage Windows Installer Local Policies
http://support.microsoft.com/support/kb/articles/Q227/1/81.ASPRepackaging Applications to Support the Windows 2000 Installer Service
http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/tcevents/itevents/tnq20102.aspNB! DCOM and MDAC can also be installed silently with command switches (we do)
Q257604 - FILE Install DCOM and MDAC Through a Windows Installer Package
http://support.microsoft.com/support/kb/articles/Q257/6/04.ASPStep-by-Step Guide to Creating Windows Installer Packages and Repackaging
Software for the Windows Installer Using VERITAS WinINSTALL LE
http://www.microsoft.com/windows2000/techinfo/planning/management/veritas.aspQ257718 - How to Create Third-Party Microsoft Installer Package (MSI)
http://support.microsoft.com/support/kb/articles/Q257/7/18.ASPQ264478 - INFO Disadvantages of Repackaging Applications
http://support.microsoft.com/support/kb/articles/q264/4/78.aspQ265194 - OFF2000 Windows Installer Appears Every Time a Program Is Started
http://support.microsoft.com/support/kb/articles/Q265/1/94.ASPIf you are going to make *very* silent installs, you should put up some kind of
progress bar that tells the user that something is happening. To get an idea, go
to Jim Warringtons (fun to read) Web site:
http://home.att.net/~wshvbs/index.htm#UsingIEforDialogs(or if you are comfortable using notoriously untrustworthy and unreliable
third-party controls as Jim Warrington says it ;-)
http://home.att.net/~wshvbs/index.htm#wshLtWtNonModalDlg
