forum.opsi.org

might do what you want.

Go to the webinterface of your opsi server. https://opsi-server.domain:4447/
There should be a list of locked packages.

Yeah, but still.. I looks like there is a much simpler solution.

Ok, ich habe jetzt alles geupdated und habe die Installationsdateien vom opsi-client-kiosk auf /media/opsi geladen und diese in das Verzeichnis opsi-client-kiosk auf dem Depot installiert. Huh? Why? Which opsi repos are active? I guess at least the windows one is? # cat /etc/opsi/package-updater.re...

für eine Software muss bei uns in der Reg zur Kontaktaufnahme mit einem Server eine Anpassung gemacht werden. Mit der Reg funktion im OpsiScript selbst funktionierte das nicht ganz wegen eines Leerzeichens. Why don't you use the registry function? Like a registry_install call in the primary section...

You should probably change this value via configed.

It will probably be fine using the standard location, except when you use the user login scripts of opsi, and have stuff running from the depot and executing it as the logged in user.

Hey thread necromancer, there are no iso files being used on the depot.

Get the newest boot cd from here: https://download.uib.de/4.2/boot-cd/

Why are you opening multiple threads about the same issue? viewtopic.php?p=58825#p58825

Well, I've looked at your log and I can only say: whiskey tango foxtrot. You first get an msi error 1603, but the error code is not checked, so the script doesn't see this is an error. Of course then the update script runs, because no errors have been raised. In your update script a section called &...

Have you read the getting started manual? This would have explained it.