opsi Version 3.3.1 - opsi Download - uib

4. Localboot products: automatic software distribution with opsi
When you interrupt the installation at that point, you often find the unpacked MSI-
package in a temporary directory.
This package can be used for unattended installation for instance with the statement:
msiexec /qb-! ALLUSERS=2 /i Product.msi
or
msiexec /i Product.msi /qn
Some more particular arguments can be supplied. An overview on the command line
arguments of “msiexec.exe” provides:
http://helpnet.installshield.com/robo/projects/InstallShieldXHelpLib/IHelpCmdLineMSI.htm
For more information on MSI have a look at:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/de/library/ServerHelp/9361d377-9011-
4e21-8011-db371fa220ba.mspx
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/msiexec.mspx
http://www.microsoft.com/windows2000/techinfo/howitworks/management/installer.asp
http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/featusability/winmsi.mspx
4.3.1.4. Customizing after a silent/unattended installation
After a successful silent installation some more customizing might be useful. The 'opsi
Winst' is a powerful tool to do that job. At first you will have to find out what patches
have to be applied. For example that could mean to analyze what registry settings are
affected by the GUI customizing tools.
You can use the tools portrayed in chapter 'Analyze and repackage' further down. Some
more tools can be found here:
http://www.sysinternals.com/
48