opsi Service Release 4.0.5 stable

[bhubal]

Dear opsi user,

today we release opsi Service Release 4.0.5 for stable.

Although opsi 4.0.5 is released as a service release, it contains many new features and extensions that would have made it worth a major release. But because there are no significant changes in the data structure, we have decided to release it as opsi 4.0.5.
So we got around the additional work of changing the repositories, for the benefit of mighty feature extensions. So for the administrators the update from 4.0.4 to 4.0.5 is kept simple.

An extended overview with details and changelogs of all new features is to be found in the Releasenotes Manual.

http://download.uib.de/opsi4.0/doc/opsi ... tes-en.pdf

In short the new features are:

New opsi extensions
With opsi 4.0.5 several new opsi extensions are available. The new extensions are co-funding projects and currently with costs.

• opsi Linux support:
With opsi 4.0.5 the installation of Linux clients is supported.
Windows and Linux clients can be administrated from a single management interface. For details see the regarding chapter of the release notes.

• opsi UEFI (Netboot) support:
more and more clients are equipped with an UEFI BIOS, which requires fundamental changes of the netboot and operating system installation. With the opsi UEFI netboot support UEFI devices can be integrated into opsi and the advantages of UEFI can be used. For details see the respective chapter of the release notes.

• opsi extension opsi-local-image (for training classroms of the public administration):
This extension provides a quick restore for training classrooms clients to restore them to a well defined initial state during a break. The concept of this feature is based on an image backup of the packet based initial installation on a second local partition, from which it can be restored in short time. For details see the respective chapter of the release notes.

Further new opsi features, that are available at no costs with the opsi kernel:

• Images with opsi clonezilla:
allows to save and restore images of clients on a network drive.

• opsi-setup-detector (automated generating of new opsi packets):
in response to many requests the opsi-setup-detector is a tool for automated opsi install script generation. It analyses the install files and creates a suitable opsiscript for installation. For details see the regarding chapter of the release notes.

• opsi-configed:
the opsi configuration editor is released with many new features and improvements. It comes with enhanced performances through improved data access especially when handling several depot servers.
The long missed feature of editing the depot specific property default values is now integrated.
The search for failed installations has become more specific, e.g. it can be queried for installations "failed today" or all installations "failed in the last 3 days".
For details see the respective chapter of the release notes.

With opsi 4.0.5 the following distributions (exclusively) are supported as opsi server:

– Ubuntu: 10.04 (Lucid), 12.04 (Precise), 14.04 (Trusty)
– Debian: 6.0 (Squeeze), 7.0 (Wheezy)
– UCS 3.2
– openSUSE 12.3, 13.1
– SLES 11SP3
– CentOS 6.5, 7
– RHEL 6.6, 7

If you are using an OS version which is not contained in the list above, we recommend updating the OS before installing opsi v 4.0.5

• new opsi bootimage:
with opsi 4.0.5 comes a new opsi bootimage based on Ubuntu
Precise / Kernel 3.1.15 with support for recent hardware (like tablets), UEFI support and Linux hard disc encryption.

• Windows netboot products:
– driver integration per byAudit also according to vendor and model of the Motherboard
– as applicable UEFI/GPT compatibility
– new property setup_after_install for process automation.

• opsi-winst / opsi-script:
– logging to c:\opsi.org\log\opsi-script.log
– new constants and string functions

• opsi-client-agent:
fixes für Windows 8.x (Loginblocker)

Discontinuation of opsi products:
With opsi v 4.0.5 the opsi products
• ntfs-write-image
• ntfs-restore-image
are not supported anymore.

Discontinuation of python 2.5 support:
python version 2.5 is not supplied with updates anymore. So opsi requires python 2.6 or python 2.7.

For December 2014 / January 2015 we have scheduled an online user survey, which will be announced by email.
In advance I would like to ask you at this point, to communicate your experience with the new opsi version 4.0.5 by the forthcoming online user survey.

With kind Regards,
Birgit Hubal

[mirkt]

Thank you for the new release! :)

[mirkt]

Are you going to update opsi-adminutils package with configed 4.0.5?

Today I noticed that my colleagues (on Windows) are using old version of configed.. I just copied new configed.jar to opsi-adminutils/files.configed and redeployed, but I think it would be nice to update opsi-adminutils package on repository..

[n.wenselowski]

Hello mirkt,

today we had a talk about the opsi-adminutils being quite outdated. We are planning on updating the package and to make it more modular. We can currently not tell when a new version will be released.

As a workaround in your case I'd suggest to use the standalone .opsi-Version of configed for the deployment.


With kind regads

Niko

[mirkt]

Sorry, I have missed that there is a standalone opsi-configed*.opsi! :) (autoInstall = false in repository_uib settings)

Thank you

[SisterOfMercy]

Configed is sooooo much faster now, finally! :-D

[mmorris]

I am sorry if this is the wrong place or i missed it but how do you upgrade to the newest version? Is the update command do that or do you have to export everything and setup a new linux server and import back into newer version? Is there a in place upgrade option?

Thanks for your time!

[knollo]

Hi,

we're using the opsi-adminutlis on our Workstations to configure the opsi server. Are there any disadvantages using this old 4.0.3.2.1 version?

Is it ok to just replace the the configed.jar from "opt/pcbin/install/opsi-adminutils/files.configed/" with the newer one at "/usr/lib/configed/"?



regards
knollo

[n.wenselowski]

Hello,

we're using the opsi-adminutlis on our Workstations to configure the opsi server. Are there any disadvantages using this old 4.0.3.2.1 version?

Is it ok to just replace the the configed.jar from "opt/pcbin/install/opsi-adminutils/files.configed/" with the newer one at "/usr/lib/configed/"?

should probably work.
But I'd recommend using the standalone product you can find in http://download.uib.de/opsi4.0/products/localboot/

I am sorry if this is the wrong place or i missed it but how do you upgrade to the newest version? Is the update command do that or do you have to export everything and setup a new linux server and import back into newer version? Is there a in place upgrade option?

The Release Notes hold information on this. Please read them before upgrading. For the update of the OS packages you can use whatever tool your distribution provides (apt-get, yum, zypper...). For the update of the opsi packages you use the opsi-product-updater.


With kind regards

Niko

[mmorris]

I am confused!! The documents for getting started with 4.0.5 said its supports ubuntu "Trusty" but said it don't support ubuntu "Trusty Tahr" What version is Trusty?? The only versions i see is ubuntu 14.04 trusty tahr?? And is 4.0.5 the current version if i am building a new server? Looking on the site its so confusing i wish the site would say the current version is 4.0.5!!!

If it is what version of ubuntu is recommended?

Thanks!