Hello,
Following a modification to our network, we can no longer use the “opsiclientd.event_gui_startup” property on our opsi clients.
We now use the “opsiclientd.event_on_shutdown” installation.
The installations run perfectly on shutdown, but is there a way of displaying a message for a few seconds so that the user can choose to postpone these installations if necessary ?
Thanks,
Possibility to postpone "event_on_shutdown" installations ?
Re: Possibility to postpone "event_on_shutdown" installations ?
Without having tested this particular combination. I guess setting these might do the trick:
Code: Alles auswählen
opsiclientd.event_on_shutdown.action_user_cancelable = 3
opsiclientd.event_on_shutdown.action_warning_time = 60
Re: Possibility to postpone "event_on_shutdown" installations ?
Hello,
Thank you for your reply.
I have added the recommended settings, this solution works almost perfectly for our system.
There is still one problem, we have set the opsiclientd.event_gui_startup.active to false.
This means that the opsi-script is no longer executed when the workstation is started; the packages are executed on shutdown.
Since adding the parameters that you suggested, I've been able to cancel the execution of the packages a certain number of times on shutdown, but I've noticed that a gui_startup event is triggered on the next start-up, although it's normally deactivated.
Thanks,
Thank you for your reply.
I have added the recommended settings, this solution works almost perfectly for our system.
There is still one problem, we have set the opsiclientd.event_gui_startup.active to false.
This means that the opsi-script is no longer executed when the workstation is started; the packages are executed on shutdown.
Since adding the parameters that you suggested, I've been able to cancel the execution of the packages a certain number of times on shutdown, but I've noticed that a gui_startup event is triggered on the next start-up, although it's normally deactivated.
Thanks,
Re: Possibility to postpone "event_on_shutdown" installations ?
Hi,
the reason for this is most likely
opsiclientd.event_gui_startup{installation_pending}
which is a separate event and by default active.
You could disable this as well and would not have any installations on startup, however this is not recommended, because some installations require a reboot during installation and these packages might produce broken results when the installation is left in an unfinished state (because it would continue only at next shutdown/reboot...). windows11-upgrade is one of these packages
the reason for this is most likely
opsiclientd.event_gui_startup{installation_pending}
which is a separate event and by default active.
You could disable this as well and would not have any installations on startup, however this is not recommended, because some installations require a reboot during installation and these packages might produce broken results when the installation is left in an unfinished state (because it would continue only at next shutdown/reboot...). windows11-upgrade is one of these packages