opsi is open source and free of license fees. Nevertheless the development of new opsi modules is expensive. So uib invented the cofinancing process as an instrument for financing the open source development.
The following modules are developed as cofunding projects. This means, that these parts of opsi are only available for those customers who pay a contribution to the development costs of the module.
As soon as the development of a co-funding project is refinanced, the component will be part of the free opsi-distribution and can be used free of charge. It will be open source then (as long as not prevented by technical reasons).
The opsi default backend is file based. For larger installations (> 300 clients) the faster MySQL-Backend is recommended because of its much better performance.
User Profile Management
The opsi-winst may be used to modify user profiles.
By default, these modifications affect the locally stored profiles. If you use roaming profiles, local profile changes are overwritten by the server-side stored profiles.
With the opsi extension „User Profile Management“ the actual working profiles are open to be changed.
The core features of this opsi extension are:
* These scripts run with administrative permissions but in the user context
* Additionally, the opsi 'UserLoginScripts' run in the opsi service context. Via script constants they have access to information about name, version and package version of the processed product, as well as to values of the product properties.
The opsi Nagios connector can be used to monitor opsi environments with Nagios or Nagios derivatives like e.g. Icinga.
The main functions are:
* Monitoring opsi-server functions
The opsi-servers (even in distributed environments) send their state and performance data to Nagios without installing any additionally Nagios plugins.
* Monitoring software rollouts with opsi
The results of software rollouts will be transmitted to the monitoring-server, grouped by clients or by software. So a quick overview of success or errors during the software deployment is possible.
* opsi-client monitoring
On each client simple checks can be executed via opsi-client-agent. The results (even from distributed environments) will be returned to the Nagios server.
Load Balancing / High Availability / Multiprocessor Support
The main service of a standard opsi server uses only one processor. In order to provide a higher server performance for larger installations, this extension enables the opsi server to get the best result in multi processor machines.
For higher reliability the opsi service can be allocated on several servers. A hot standby and load balancing can be achieved. (Projected, will require MySQL-Backend)
The opsi extension License Management can be used to standardize and simplify the complex and laborious management of software licenses for software installed on opsi managed clients.
The main features are:
* The License Management uses the same management interface as software deployment and OS installation: the opsi Configuration Editor.
* For opsi products, license keys can be automatically allocated, assigned, and reserved.
* Among the supported licensing models are: single license, volume license, license bound to a specific host, licenses for which the number of concurrent usages is regulated by a license server.
* Automated release of license keys when uninstalling licensed software or removing the host.
* Manual processing of allocated licenses e.g. for licenses of software not deployed with opsi.
* Generating several report types: overview of license usage, documentation of license usage, reconciliation of opsi managed licenses with the licenses found via opsi Software Inventory.
By virtue of the opsi WAN extension, computers used by travelling sales representatives, homeworkers, or from small remote locations connected via WAN to the company's network can be integrated into opsi.
Its features are:
* The activation of the opsi-client-agent can be triggered by and limited to the activation of special network interfaces (e.g. VPN interface). With this configuration, a client does not try to connect to the opsi server at every system start but only if it is connected via VPN to the company's network.
* Because of the limited bandwidth of WAN connections, the standard direct software installation is not recommended for remote clients. Therefore the WAN extension enables the bandwidth saving download of installation data per https/WebDAV and stores the data locally.
* The download process is reconnectable and continues after disconnection. Furthermore all necessary auxiliary data like product properties, license keys and so on are cached on the local system.
* The installation starts when all required data are downloaded to the local client. During the installation process no connection to the opsi server is required. The installation results are stored locally and reported to the opsi server with the next connect.
* In order to run the WAN extension you need the MySQL-Backend extension as precondition.
opsi - ITSM Connections realized by our partners:
OTRS::ITSM Connection - via KIX4OTRS by c.a.p.e IT GmbH
opsi is a powerful component in a professional IT Service Management Solution. The opsi modules 'Inventory' and 'License Management' provide important data that can be provided to other management tools.
Therefore our partner and ITSM specialist c.a.p.e. IT developped an opsi / OTRS::ITSM interface. This module enables via opsi web service interface the automated import of specified data into the OTRS CMDB and keeps the database up-to-date.
For further information see:
iTOP / opsi Connection by ITOMIG GmbH
iTOP, the IT Service Management Tool from out partner ITOMIG GmbH now comes with an iTOP / opsi connector that imports the opsi-inventory data directly into the iTOP CMDB.
For further information see: