opsi Version 3.3.1 - opsi Download - uib
opsi Version 3.3.1 - opsi Download - uib
opsi Version 3.3.1 - opsi Download - uib
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
4. Localboot products: automatic software distribution with <strong>opsi</strong><br />
As an additional option the module 'loginblocker' can be installed to prevent a user login<br />
before the end of the installation process is reached.<br />
Before software packets can be installed with the 'wInst' program, they have to be<br />
prepared as <strong>opsi</strong> packets. The 'wInst' executable supports the <strong>opsi</strong> wInst script<br />
processing language and and provides different ways of installation:<br />
• Existing setup programs from the original software manufacturer can be executed<br />
from within a wInst script in 'silent' or 'unattended' mode. It depends on the setup<br />
program whether silent installation mode is supported<br />
• The standard setup can be analyzed and 'recorded' to do the installation tasks<br />
directly by the 'wInst' program. Usually that is something like file installation to the<br />
local file system and patching the registry<br />
• The interactive answers required by the original setup program can be given<br />
automatically by using the free tool 'autoiIt' (www.hiddensoft.com/autoit/). That means<br />
providing an autoIt script for unattended installation<br />
Usually a combination of all different ways in one script does the job best. Like doing<br />
the basic installation by the original setup if available and then do some customizing by<br />
patching registry or file based configuration.<br />
4.1.2. Integration of the software installation with the <strong>opsi</strong> preLoginLoader<br />
The primary objective of software distribution is to accomplish automatic software<br />
installation without user interaction. Software installation and user activity should be<br />
strictly separated. In most cases the installation process requires administrative<br />
privileges which the user usually doesn't have. So the installation process has to be<br />
done independently from the user. In that way neither the user can interfere with nor the<br />
user is affected by a software installation process.<br />
37