How to run Icinga for Windows in 2025/26

Icinga 2 Icinga for Windows
1

We started Icinga as a a pure Director based installation. Most of our infrastructure is imported by automations.

Except for the 100+ Windows servers. They use the self-service facility in Director. On the Windows side the bootstrap happens as part of a scheduled task.

I totally appreciate the elegant IfW API infrastructure, mTLS, etc. The only thing that’s weird is the Icinga Agent on the Windows side - behaving like a satellite in our cluster.

I am aware of Icinga for Windows without an Icinga 2 agent , but I can’t quite grasp the consequences. Once the agent used the self-service ticket to add itself to Icinga, do I still need it?

There is a scheduled task in the Powershell framework that will renew the certificate every now and then - is this part of the agent?

When I uninstall the agent, will my host still be registered in Icinga, how do I properly demote the Windows client - it should only be a host from now on?

2

Pretty simple. You need to change the Host Template to one that doesnt have the “Agent Host” (or however its called) Setting set to true.

3

Sounds reasonable, but how would I tell the service to use command_endpoint = host_name ?

4

in the director? pretty hacky atm, as there is no feature to set the command_endpoint directly as far as i know. You could do this by importing a host_template using the kickstart or (i think) with an director basket.