opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
142 / 193
So as precondition to use this extension you need as first an activation file. For evaluation purpose you will get a
temporary activation file if you ask for it in a mail at info@uib.de.
Technical preconditions are opsi 4.0.1 with the following package and product versions:
Table 5: Needed product and package versions
opsi product Version
opsi-client-agent >=4.0.1-23
opsi-winst >=4.11.2.1
python-opsi >=4.0.1.31-1
19.2 Introduction
The opsi-winst has some special commands to manipulate profiles. These commands act at the local stored profiles.
If you are using Roaming Profiles this feature of the opsi-winst does not help you because all modifications at the
profiles will be overwritten by the server stored profile while login.
The opsi extension for User Profile Management gives you the possibility to do the needed profile manipulation after
the login of the user, at the correct profile. This is done by starting the opsi-winst after the user login again and run
some special userLoginScripts.
19.3 Concept
If you can’t do the profile manipulation while installing the software on the machine, you have to separate the machine
part of the software installation from the profile part. This can be done inside of a script and also by putting the
profile part into a separate script. Many admins still use the second idea by integrating profile parts into a domain
login script.
According to the method you use the profile part of your opsi products are part of the opsi installation scripts for
installation and deinstallation or they are separated for example as part of the domain login scripts.
The goal of this opsi extension is to provide the possibility to integrate both variants of scripts easily.
The core concepts of this opsi extension are:
• Executing special userLoginScripts scripts at the user login
At the user login the opsiclientd uses the event_user_login to startup the opsi-winst in a special login script mode.
In this special mode the opsi-winst executes only the userLoginScripts which are assigned to the opsi products.
• Executing these scripts with administrative privileges inside the context of the logged in user
Domain login scripts may be used to execute profile parts. But they run only with user privileges. opsi userLogin-
Scripts run with administrative privileges. They run with these high privileges in the user context, so that is easy
to manipulate file and registry parts of the profile using the same commands you may use in a domain login script.
• Executing these scripts inside of the opsi service context
The opsi userLoginScripts run inside the opsi service context, so that they know all details about at which opsi
product name, version and package version they are just working. They have the complete access to product
properties and other information that can be requested by opsi service calls.
Restrictions:
• The opsi userLoginScripts will be always executed online and not from a local cache. Even if your client runs with
the opsi WAN extension.