<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows on polar-node // runbooks</title><link>https://polar-node.work/tags/windows/</link><description>Recent content in Windows on polar-node // runbooks</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 12 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://polar-node.work/tags/windows/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows Firewall disabled on multiple hosts. Our monitoring never noticed the change</title><link>https://polar-node.work/posts/custom-zabbix-windows/</link><pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate><guid>https://polar-node.work/posts/custom-zabbix-windows/</guid><description>&lt;p&gt;Windows Firewall disabled on multiple hosts. Our monitoring never noticed the change&lt;/p&gt;
&lt;p&gt;A few months back while working with Zabbix for our mixed environment, I realized that the default Windows template doesn&amp;rsquo;t monitor whether Windows Firewall is actually enabled across its three zones (Domain, Private, and Public). There also wasn&amp;rsquo;t a straightforward way to see who was or still is logged into each Windows machine.
For something as critical as firewall status, this felt like an important gap, so I came up with a two-fold solution:&lt;/p&gt;</description></item></channel></rss>