opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
-h show this help text
-V show version information
-q do not show progress
-v increase verbosity (can be used multiple times)
-c clean destination database before writing
-s use destination host as new server
-l log to this file
and can be:
- the name of a backend as defined in /etc/opsi/backends (file, ldap, ...)
- the url of a opsi configuration service
http(s)://@:/rpc
21.6 Boot files
/tftpboot/linux contains the boot files needed for the system start with the PXE boot proms.
21.7 Securing the shares with encrypted passwords
178 / 193
The opsi-client-agent accesses the shares provided by the opsi-server to get the software which have to be installed at
the client.
The mount of these shares is done by using the user pcpatch. That these shares are not public and have to be mounted
using a password is important for: * general system security and data integrity * meet the license agreements of special
software packets
To give the client task opsi-client-agent access to authentication data, the server creates a specific key (opsihost-key)
when creating a client. This key is stored (at the file backend) in the file /etc/opsi/pckeys and is
passed to the PC with the (re)installation request. The opsi-client-agent will store this key in the local file
c:\program files\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf during system installation (access
rights limited to the administrators). Also, on the server, the file /etc/pckeys is only accessible by the user root
and members of the group opsiadmin. This way every PC has got an unique key only known to the client itself and the
opsi-server, not accessible by client standard users. The key is used to encrypt the password of the user pcpatch. The
encrypted password will be transferred to the client at boot time via web service. Hence the servers pcpatch password
can be changed any time. The new encrypted password will be sent to every client at the next reboot.
22 Adapting the opsi-client-agent to your Corporate Identity (CI)
Adapting the opsi-client-agent to your Corporate Identity (CI) will enhance the acceptance of a opsi roll out.
It is possible to manipulate the graphical skin of the opsi-winst by changing the file
bg.png in the sub directory winstskin. After any change at this file in the directory
/opt/pcbin/install/opsi-client-agent/files/opsi/opsi-winst/winstskin you should execute the command
touch /opt/pcbin/install/opsi-client-agent/files/opsi/opsi-winst/winst32.exe
which changes the time-stamp of this file. As result of this operation the opsi-client-agent will see a changed opsi-winst
at the next startup and copy the opsi-winst and all it files (including bg.png) to the client.
In addition you will find at the directory /opt/pcbin/install/opsi-client-agent/files/opsi/dist/notifier the
files action.bmp and event.bmp which may be changed to fit your preferences. These files will be transferred to the
client at the installation of the opsi-client-agent.
You may may change location, color and font of the labels which will be displayed at run time by changing the Ini
files of the notifier (event.ini, action.ini, shutdown.ini). Please note that these files will be overwritten in case
of installing a new version of the opsi-client-agent at the server.