windows10-upgrade and updates in stable and testing

Antworten
Benutzeravatar
d.oertel
uib-Team
Beiträge: 3319
Registriert: 04 Jun 2008, 14:27

windows10-upgrade and updates in stable and testing

Beitrag von d.oertel »

Dear opsi users

Hereby we release some testing packages now as stable.
Also we say hello to some new testing packages.

The Windows 10 "Fall Creators Update" will be published at 17.10.2017.
Therefore we publish a product, that will help you to make Win10 Release Upgrades
controlled by opsi: The product 'windows10-upgrade'
You may use this product also to upgrade to Windows 10 from a prior Version.
(Lear more from the readme inside the product).
The main focus is the regular windows 10 Release Upgrade (1511 -> 1607 -> 1703 -> 1710 ...).
So you may use this product now to update a windows 10 from 1611 to 1703.
It should also work to upgrade from 1703 to 1710, but this is not tested now
because 1710 is not available yet.
After we have tested this this product will be released as stable.
Like the opsi windows netboot products, you have to fill the 'installfiles' directory
of the product with the content of the installation media of the target windows version.
The standard way to get these media is the use of the 'MS Media Creation Tool' which you may download at Microsoft.
Do not forget to call 'opsi-set-rights' after integrating the installation files
to the Product.
This product is a localboot product and the installation takes a long time (about 45 Minutes).
Running this product, a temporary non administrative use will be created and removed when all is finished.
The installation need a loggedin user while the installation it self is started by opsiclientd
with system credentials.

By the way:
We like to point to some special Windows 10 opsi products which may useful for you:
classic-shell for comfortable work in the windows desktop:
http://download.uib.de/opsi4.0/products ... 3.1-1.opsi
Windows10 configuration via opsi:
http://download.uib.de/opsi4.0/products ... 0.7-7.opsi
see also:http://download.uib.de/opsi_stable/doc/ ... t-products
Chapter: config-win10

As testing we also publish a new version of opsi-script/opsi-winst:
ATTENTION:
In this version we changed the logging structure and the default log level.
The logging at the different log levels is now:
Log level 5:
comments,messages, Execution of sections
Log level 6:
Statements, New values for stringvars , results of complete boolean expression
Log level 7:
new values for stringlist vars,
output from external processes (shellInAnIcon) if the out put is not assigned to a stringlist variable,
results of parts of a Boolean expression
Log level 8:
other stringlist output eg. string lists from stringlist functions and
output from external processes (shellInAnIcon) that is assigned to a stringlist variable.

The new default loglevel is 7 (was 6).

We hope that the logs are now better structured:
Tipp: use opsi-logviewer to read external opsi logfiles

Eyery ideas to make the logging better is welcome.

In details:

As stable we publish:

Netboot products in the version 4.0.7.1-9

win10_4.0.7.1-9.opsi
win10-captured_4.0.7.1-9.opsi
win10-x64_4.0.7.1-9.opsi
win10-x64-captured_4.0.7.1-9.opsi
win2008-r2_4.0.7.1-9.opsi
win2012_4.0.7.1-9.opsi
win2012-r2_4.0.7.1-9.opsi
win2016_4.0.7.1-9.opsi
win7_4.0.7.1-9.opsi
win7-captured_4.0.7.1-9.opsi
win7-x64_4.0.7.1-9.opsi
win7-x64-captured_4.0.7.1-9.opsi
win81_4.0.7.1-9.opsi
win81-captured_4.0.7.1-9.opsi
win81-x64-captured_4.0.7.1-9.opsi


Localboot products

nothing

opsi-linux products

nothing

opsi-local-image:

nothing



As testing we publish:

LocalBoot products

* opsi-wim-capture 4.0.7.2-2
* opsi-client-agent 4.0.7.23-4
* opsi-winst 4.12.0.7-1
* windows10-upgrade 17.09-2


Netboot products in the version 4.0.7.1-10

win10_4.0.7.1-10.opsi
win10-captured_4.0.7.1-10.opsi
win10-x64_4.0.7.1-10.opsi
win10-x64-captured_4.0.7.1-10.opsi
win2008-r2_4.0.7.1-10.opsi
win2012_4.0.7.1-10.opsi
win2012-r2_4.0.7.1-10.opsi
win2016_4.0.7.1-10.opsi
win7_4.0.7.1-10.opsi
win7-captured_4.0.7.1-10.opsi
win7-x64_4.0.7.1-10.opsi
win7-x64-captured_4.0.7.1-10.opsi
win81_4.0.7.1-10.opsi
win81-captured_4.0.7.1-10.opsi
win81-x64-captured_4.0.7.1-10.opsi


opsi-linux products

* opsi-linux-client-agent (4.0.7.17-1)

opsi-local-image:

* opsi-local-image-capture (4.0.7.1-2)


regards
detlef oertel


Changelogs:
-----------
opsi-client-agent (4.0.7.23-4) stable; urgency=low

* remove of some del -s Options (bug created in last Version)
* removed unused section DosInAnIcon_lock_opsiclientd_conf
* unused file opsicliend.reg

-- Detlef Oertel <d.oertel@uib.de> Mon, 06 Oct 2017:15:00:00 +0200

opsi-client-agent (4.0.7.23-3) stable; urgency=low

* use 'sc failure' to configure opsiclientd service restarts after failure
* use allway -c option in delete and copy to avoid not wanted reboots

-- Detlef Oertel <d.oertel@uib.de> Mon, 02 Oct 2017:15:00:00 +0200

opsi-client-agent (4.0.7.23-2) stable; urgency=low

* Files_del_systray: Fixed wrong path.
* Trying to kill notifier.exe before copying

-- Erol Ueluekmen <e.ueluekmen@uib.de> Thu, 28 Sep 2017:14:00:00 +0200

=======================================================

opsi-winst/opsi-script (4.12.0.7) stable; urgency=low

* default loglevel is now 7 (was 6)
* new config: opsi-script.global.ScriptErrorMessages : boolean ; default=true (created as false)
* config: opsi-script.global.default_loglevel will be created as 7

-- Detlef Oertel <d.oertel@uib.de> Tue, 10 Oct 2017:15:00:00 +0200

opsi-winst/opsi-script (4.12.0.6) stable; urgency=low

* osconf: readConfigFromService reads configstates:
temporary uncommented: opsi-script.global.ScriptErrorMessages : boolean ; default=true (created as false)
opsi-script.global.AutoActivityDisplay : boolean ; default=false (created as true)
* general: adjusting log levels
5:LLNotice: comments,messages, Execution of sections
6:LLInfo; Statements, New values for stringvars , complete boolean expression
7: new values for stringlist vars, Output from sections,
shellcall if the output is not written to a stringlist, parts of a boolean expression
8: other stringlist output
9: content of saved temporary files

-- Detlef Oertel <d.oertel@uib.de> Wed, 27 Sep 2017:15:00:00 +0200


=================================================

opsi-linux-client-agent (4.0.7.17-1) stable; urgency=low

* opsi-script 4.12.0.7

-- d.oertel <d.oertel@uib.de> Tue, 10 Oct 2017 15:00:00 + 0100

opsi-linux-client-agent (4.0.7.16-1) experimetnal; urgency=low

* opsi-script 4.12.0.6

-- d.oertel <d.oertel@uib.de> Tue, 05 Oct 2017 15:00:00 + 0100

opsi-linux-client-agent (4.0.7.15-1) experimetnal; urgency=low

* Updating repositories prior running apt-get install commands

-- Mathias Radtke <m.radtke@uib.de> Wed, 04 Oct 2017 09:45:00 +0200


=================================================

windows (4.0.7.1-10) stable; urgency=low

* replaced opsi4.0 check with an opsi4.x check

-- Mathias Radtke <m.radtke@uib.de> Wed Oct 4 13:57:19 2017 +0200


windows (4.0.7.1-9) testing; urgency=low

* opsisetuplib.py: added sleep prior making NTFS partition

-- Mathias Radtke <m.radtke@uib.de> Wed Sep 20 08:12:22 2017 +0200

=================================================

opsi-wim-capture (4.0.7.2-2) stable; urgency=low

* new property image_flag: Flag will be set after capture
* set flag also after creat via dism
* update auf wimlib 1.12

-- detlef oertel <d.oertel@uib.de> Wed, 04 Oct 2017 15:00:00 +0000

opsi-wim-capture (4.0.7.2-1) stable; urgency=low

* try to include sysprep logs
* call method updateWIMConfig
* fixed ShellInAnIcon_imagex_flags
* fix create work.cmd for different netboot product versions
* start opsi-script in PE with /logproductid
* stop service tiledatamodelsvc before sysprep
* use powershell to get boot drive
* do not use WINDOWS Label to get captutre Drive Letter

-- detlef oertel <d.oertel@uib.de> Wed, 06 Sep 2017 15:00:00 +0000


opsi-wim-capture (4.0.7.1-5) stable; urgency=low

* workaround for setProductActionRequestWithDependencies (none Bug)

-- detlef oertel <d.oertel@uib.de> Thu, 20 Jul 2017 15:00:00 +0000


opsi-wim-capture (4.0.7.1-4) stable; urgency=low

* new property: shutdown_after_capture (default=false)

-- detlef oertel <d.oertel@uib.de> Tue, 07 Feb 2017 15:00:00 +0000

=================================================
opsi support - uib gmbh

For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
Antworten