opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
117 / 193
Now we examine the situation of a notebook, which at system startup often cannot connect the opsi-config-server:
• Trying to connect the opsi-config-server at system startup will result in a timeout.
• Connecting the opsi-config-server might be possible when a user logs on and a VPN connection to the corporate
network is established.
• Without connection the opsi-config-server no software deployment is available.
This situation also can be solved by using the WAN/VPN extension module.
The opsi-client-agent can be configured the following way:
• At system startup, if there are no opsi-products cached and ready for installation, the user can logon immediately.
• Triggered by network activation or a by timer event, the opsiclientd running on the client tries to connect the
opsi-config-server.
• If the opsi-config-server is reachable, the opsiclientd starts to:
– synchronize the configurations
– download the required files from the opsi-depot to the local file system.
In combination with the opsi extension module Dynamic Depot Selection, the download is done from the best
fitting opsi-depot.
• When the synchronization of the opsi-products is completed, a reboot request is triggered.
• The logged on user can accept the reboot request or the client will be rebooted at some time later on.
• At the next system startup, the cache is found to be filled with the opsi-products to be installed and the installation
starts. In this case, the installation will use the downloaded files from the local file system, which increases the
speed of installation even compared to a standard LAN installation. So the opsiclientd takes over the function of
both the opsi-config-server and the opsi-depot-server.
• At the next connect to the opsi-config-server the results of the installation process (configuration change, log files
. . . ) will be synchronized.
The download mechanism of product synchronization is multiple interruptible and will continue at the point of interruption.
So files that are already downloaded will not have to be downloaded again.
The WAN/VPN extension module allows to connect clients, that are outside of the secure corporate network. Therefore
additional security mechanisms are required regarding the communication between client and server.
So the opsiclientd now offers the ability to verify the identity of an opsi-server. Therefore the key pair of the SSL
certificate of the opsiconfd is used.
By this mechansim the opsi-config-server as well as the opsi-depot-server can be verified, assumed the communication
is performed via opsiconfd and SSL. In case of an opsi-depot the file access must be done by the opsiconfd using
HTTPS/WEBDAVS. Access done via CIFS/SMB will not be checked.
15.3 Caching of opsi-products
Caching of opsi-products is done by the ProductCacheService, which is part of the opsiclientd.
The ProductCacheService synchronizes the local copy of an opsi-product with the current version of the corresponding
opsi-products on the opsi-depot. The location of the local product cache can be configured and defaults to
%SystemDrive%\opsi.org\cache\depot.