Icinga
Feature: Adds support to offload service and JEA actions to scheduled tasks
This feature allows Icinga for Windows to offload all tasks regarding JEA-Profile generation as well as service management to be offloaded to a scheduled task instead of being run within the same shell instance.
This ensures that remote installation tasks are more easily configurable as well as prevents the Icinga Agent services of being stuck in the "Scheduled for deletion state" during upgrades of the Agent.
I wanted to check whether there is a rough ETA on this? At the moment, it is incredibly frustrating to install IfW with JEA enabled in a larger environment, getting to a point where we might decide to completely ditch JEA, as it seems to behave differently after each update. If there is a solution that would enable us to more easily deploy and update IfW including JEA remotely in a larger environment, some pointers would also be appreciated.
What do you mean by that? This offloader is only intended to work for remote installation by using WinRM for example. Installing Icinga for Windows is on a regular basis easily done by enabling it on the wizard and embedding it in your installation JSON or by running
Install-IcingaSecurity
on those machines.
The only limitation at the moment, is by running the above command through a WinRM session. Because this will not work, as the WinRM service restarts during the installation and interrupts the profile registration.
That's exactly our problem. It is unfeasible/unreliable to install or even upgrade Icinga on multiple machines with JEA because WinRM restarts and the install fails. We currently have a very weird workaround which also involves tasks, but the script worked with 1.11 and now does not work anymore with 1.12 (we haven't investigated very thoroughly why). We are now installing Icinga without JEA and will enable it manually afterwards.
So in essence: having a way to reliably install icinga remotely on multiple machines with JEA enabled would make our lives a lot easier.
Thanks for the update. Yes, this is something we are currently working on and should ship with v1.13