opsi manual opsi version 4.0.2 - opsi Download - uib
opsi manual opsi version 4.0.2 - opsi Download - uib
opsi manual opsi version 4.0.2 - 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.
<strong>opsi</strong> <strong>manual</strong> <strong>opsi</strong> <strong>version</strong> <strong>4.0.2</strong><br />
<strong>opsi</strong>-admin -d method backend_info<br />
{<br />
"<strong>opsi</strong>Version" : "3.99.0.0",<br />
"modules" :<br />
{<br />
"customer" : "<strong>uib</strong> GmbH",<br />
"vista" : true,<br />
"vpn" : true,<br />
"license_management" : true,<br />
"expires" : "never",<br />
"valid" : true,<br />
"multiplex" : true,<br />
"signature" : "DIES-IST-KEINE-ECHTE-SIGNATUR",<br />
"treeview" : true,<br />
"mysql_backend" : true<br />
}<br />
}<br />
7 <strong>opsi</strong>-client-agent<br />
7.1 Overview<br />
55 / 193<br />
To make Software distribution manageable for the system administrator, a client computer has to notice that new<br />
software-packets or updates are available and install them without user interaction. It is important to make userinteraction<br />
completely obsolete as the installation can run unattended this way and a user cannot stop the installation<br />
during the installation process.<br />
These requirements are implemented in <strong>opsi</strong> by the <strong>opsi</strong>-client-agent:<br />
On the client side the service <strong>opsi</strong>clientd examines usually at boot time, before the user logs in, whether an update<br />
has to be installed for this client.<br />
If there are software packets to be installed on the client, the script processing program <strong>opsi</strong>-winst is being started to<br />
do the installation job. The server provides all the installation scripts and software files on a file share. At this time<br />
the user has no chance to interfere with the installation process.<br />
As an additional option the module loginblocker can be installed to prevent a user login before the end of the installation<br />
process is reached.<br />
Before any software can be installed with the <strong>opsi</strong>-winst program, it has to be prepared as <strong>opsi</strong>-product-package. For<br />
details see Chapter Integration of new software packets into the <strong>opsi</strong> software deployment from the getting started<br />
<strong>manual</strong>.<br />
7.2 Directories of the <strong>opsi</strong>-client-agent<br />
The <strong>opsi</strong>-client-agent is installed at %ProgramFiles%\<strong>opsi</strong>.org\<strong>opsi</strong>-client-agent.<br />
This directory contains all programs of the <strong>opsi</strong>-client-agent like e.g. the <strong>opsi</strong>clientd, the <strong>opsi</strong>clientd notifier, the<br />
<strong>opsi</strong>-winst and some required libraries. Also we will find here the configuration files and graphical templates (skins)<br />
of the mentioned programs.<br />
The directory %ProgramFiles%\<strong>opsi</strong>.org\<strong>opsi</strong>-client-agent is protected against manipulation by users without<br />
administrator privileges.<br />
The directory %ProgramFiles%\<strong>opsi</strong>.org\<strong>opsi</strong>-client-agent\<strong>opsi</strong>clientd contains the configuration file of the<br />
<strong>opsi</strong>clientd and you need administrator privileges to read it.<br />
There also is the directory c:\<strong>opsi</strong>.org.<br />
This directory is used (at the moment) for caching installation files and data (see WAN-Extension). In future it will<br />
have some more functions like containing log files.<br />
You need administrator privileges to read the directory c:\<strong>opsi</strong>.org.<br />
The log files of the <strong>opsi</strong>-client-agent you will find in c:\tmp.