opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
set [ProgressBar] BarColor = $winst_skin_color$
set [ProgressBar] StartColor = $winst_skin_color$
set [ProgressBar] FinalColor = $winst_skin_color$
set [ProgressBar] ShapeColor = $winst_skin_color$
set [Form] Color = $00E7E7E7
23 Important files on the depot servers
23.1 Configuration files in /etc
23.1.1 /etc/hosts
181 / 193
The hosts file stores all IP addresses and IP names known to the network. The IP addresses and names of all clients
have to be entered here. There might be aliases (additional names) and comments (starting with #).
opsi needs full qualified host name (including the domain name) and this might come from the /etc/hosts as well
from the DNS.
Example:
192.168.2.106 dplaptop.uib.local dplaptop # this opsi-server
192.168.2.153 schleppi.uib.local
192.168.2.178 test_pc1.uib.local # Test-PC PXE-bootprom
With the following command you may test the name is resolved:
getent hosts $(hostname -f)
The result should be similar to:
192.168.1.1 server.domain.tld server
If the result isn’t like that and contains for example 127.0.0.1 or localhost you should correct your /etc/hosts or
your DNS before you continue with the installation.
23.1.2 /etc/group
The required opsi groups are pcpatch and opsidamin. All users who are administrating opsi packets need to be member
of the pcpatch group. Membership of the group opsiadmin allows users to connect to the opsi web service (for instance
using the opsi-configed).
23.1.3 /etc/opsi/backends/
Configuration files for the used backends.
23.1.4 /etc/opsi/backendManager/
• acl.conf
Configuration of the access control lists to the opsi methods.
• dispatch.conf
Configuration which of the in /etc/opsi/backends/ configured backends should be used for which method.
• extend.d/
Directory for backend extensions. For example this is be used to implement the old opsi 3 methods which are
mapped to the new opsi 4 methods.