opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
Figure 63: License management: copying the license-ID to the license options from the context menu
109 / 193
This softwareLicenseId is needed for the further configuration steps. You can keep it in mind or copy it with drag&drop.
You can as well look for the ID in the "Available license options" list of the "Edit licenses" tab. The context menu
supports copying the ID.
The important step now is to connect this softwareLicenseId to an additional license pool.
Therefore a new record has to be registered from the "Available license options" table of the "Edit licenses" tab. The
fields of the new record have to be filled with the softwareLicenseId and the ID of the additional license pool (in this
case the pool for Windows XP licenses). For installing Windows XP based on this license, an applicable Windows XP
license key already in use by another client has to be added.
After saving the new record, there are two different license options based on the same software license! The opsi
service counts the use of either of them as an installation deducting from the maximum installation count. So in case
of a downgrade license (with maxInstallations = 1), the opsi service delivers a license key for a Vista installation or
for a XP installation, but not for both of them.
14.6 Assignment and release of licenses
Using a license option by installing the software on a client results in the actual licensing (which is the use of the
license option).
In the opsi context installations are done script based and automatically, which is the client running the Winst script
invokes some calls to the central opsi service.
The following chapters introduce some of these service calls, which are relevant for the license management. For
further information about Winst and opsi commands see the documentation on Winst and opsi.
14.6.1 opsi service calls for requesting and releasing a license
The opsi service call for requesting a license option and retrieving the license key for doing the installation (as
transmitted by a Winst script) is
getAndAssignSoftwareLicenseKey
The parameters to be passed are the client hostID (hostID of the client where the software is to be installed) and the
ID of the license pool the license is requested from. Instead of the licensePoolId also an opsi-product ID or a Windows
Software ID can be passed, if they are connected to a license pool within the opsi license management.