Dear opsi-user,
opsi 4.0.1 is declared as Final Release now.
All english manuals are written.
We announce the end of live of opsi 3.
Opsi 4.0.1 is a minor release respectively a feature pack.
This means that nothing is fundamental changed and most things are new add-ons.
It is not necessary to do any changes in the repository nor special works on the server.
But at least, there are some recommended tasks to do after the upgrade
The new add-ons come with the continuing updates of the opsi 4.0 repository or with the opsi-product-updater call to you system.
A summary about the new features of opsi 4.0.1 and about the recommended tasks are given below and in the releasenote/upgrade-manual.
The opsi 4.0.1-documentation can be found here:
http://download.uib.de/opsi4.0/doc/opsi ... ual-en.pdf
http://download.uib.de/opsi4.0/doc/opsi ... 401-en.pdf
http://download.uib.de/opsi4.0/doc/opsi ... 401-en.pdf
A preconfigured opsi 4.0.1 VM can be found here:
http://download.uib.de/opsi4.0/opsi4.0.1-servervm.zip
Here is a summary about the new features of opsi 4.0.1:
• opsi WAN/VPN-Extension to integrate clients behind slow connections.
* Local caching of the installation files.
* Local caching of the installation meta data.
* Download the installation data as background process with dynamical bandwidth, so the user will not be disturbed.
* The data download may be interrupted any time and will not restart but continue the download as soon as possible.
* The Installation is using the local cache - no network connection is required.
* Using alternatively the smb/cifs or the https/webdav protocol to download the required files to the local cache.
* Possibility to use https/webdav even for the OS installation.
* opsiclientd info page to visualize the opsiclientd activity.
* This is a co-funding project, which means that it is fee-required until all project costs are earned.
• dynamic depot selection:
* In a multi location / multi depot environment, a client is now able to detect which depot is the best to get the required software from.
* This is a co-funding project, which means that it is fee-required until all project costs are earned.
• software on demand
* This module enables any user to install dedicated software via opsi (using a product group software on demand)
* This works using a local website which is created by the opsiclientd.
• opsi management interface (opsi-configed) enhancements
* Depot property editor.
* Interactive GUI language selection.
* Interactive query and display which clients are on-line.
* A pseudo client group which contains automatically all clients with a installation result: failed.
* Possibility to use product groups.
* Which columns are visible in the opsi-configed may now be stored at the server.
* Clients may now be selected using a search field.
* License management: At the crystal tab Reconciliation now only those clients are shown, which have a entry in the table.
* You may select clients by this criteria: a product on the client is on a lower version than it is available on the server.
* You may change the log level while running the configed.
* The license management now takes multiple occurrences of software inventory patterns that are assigned to one license pool only as one installation of this software.
This means that if for example a license pool office2010 is assigned to 10 different software inventory patterns, only one installation will be counted even if we find all 10 pattern on a single client.
• New Windows NT6 netboot products (Boot-Partition, System-Partition, enhanced driver integration)
• Configuration of the name resolution in the new configuration file /etc/opsi/backends/hostcontrol.conf
• Configuration of directed broadcasts in the new configuration file /etc/opsi/backends/hostcontrol.conf
• New opsi-client-agent with enhanced configuration and enhanced notifier
• The password for root in the opsi-linux-bootimage may be now set via opsi-linux-bootimage.append host parameter
pwh=<password-hash>
• An authentication of the opsi-server at the client is now possible
End of live opsi 3
With opsi 4.0.1 we announce now 9 month after the release of the new stable opsi 4, the end of support for opsi 3
for the 1. July 2011.
In concrete:
• We will not check any new packages for functionality in a opsi 3 environment.
• New packages may have a topical opsi 4 client-agent as precondition.
• There will be no fixes for opsi 3 anymore.
• uib will no more maintain a opsi 3 test environment. So any opsi 3 support call will take a longer time and will be
therefore more expensive.
• We strongly recommend to upgrade all opsi 3 installations before in July 2011 to opsi 4
For further opsi 4.0.1 updates, please look at the changelogs in:
viewtopic.php?f=1&t=2605
viewtopic.php?f=1&t=2616
viewtopic.php?f=1&t=2647
viewtopic.php?f=1&t=2702
viewtopic.php?f=1&t=2756
viewtopic.php?f=1&t=2763
With kind regards
yours
opsi-team