Monitoring infrastructure is not something you want to deal with only after problems appear. In production environments, even a short downtime or missed alert can lead to serious issues - from failed services to unnoticed CPU spikes and broken integrations.
That is why tools like Zabbix Agent are widely used. It helps collect system metrics from Windows Server 2025 and sends them to a central Zabbix server for monitoring, alerting, and visualization.
In this guide, we'll go through a clean step-by-step installation process, including configuration, firewall setup, testing, and common mistakes to avoid.
What You Need Before Installation
Before starting, make sure you have:
- Windows Server 2025 with administrator access
- Running Zabbix server instance
- Network connectivity between server and Zabbix (port 10050)
- Official Zabbix Agent Windows package
Step 1. Download Zabbix Agent
Download the official Windows version of Zabbix Agent from the Zabbix website.
After extraction, you will see:
- zabbix_agentd.exe
- zabbix_agentd.conf
- supporting binaries
Place files into:
C:\Program Files\Zabbix Agent\This directory will be used for both configuration and service execution, so keep it unchanged unless you have a specific deployment requirement.
Step 2. Configure Zabbix Agent
Open configuration file:
C:\Program Files\Zabbix Agent\zabbix_agentd.confThis is the key step where the agent is linked to your Zabbix server.
Set the following parameters:
| Parameter | Value Example | Description |
|---|---|---|
| Server | 192.168.1.10 | Zabbix server IP (passive checks) |
| ServerActive | 192.168.1.10 | Zabbix server IP (active checks) |
| Hostname | WIN-SERVER-2025 | Must match host name in Zabbix frontend |
| ListenPort | 10050 | Default agent port |
| ListenIP | 0.0.0.0 | Optional: binds agent to all interfaces |
Step 3. Install Zabbix Agent as a Windows Service
Run PowerShell as Administrator:
cd "C:\Program Files\Zabbix Agent"
zabbix_agentd.exe --install
zabbix_agentd.exe --startAlternatively, you can install it manually as a Windows service:
sc create "Zabbix Agent" binPath= "C:\Program Files\Zabbix Agent\zabbix_agentd.exe"
sc start "Zabbix Agent"Zabbix Agent runs as a lightweight Windows service and immediately starts collecting system metrics after launch. It has minimal performance impact and is designed for continuous monitoring workloads.
Step 4. Configure Windows Firewall
Allow inbound traffic on port 10050:
New-NetFirewallRule -DisplayName "Zabbix Agent" -Direction Inbound -Protocol TCP -LocalPort 10050 -Action AllowWithout this rule, the Zabbix server will not be able to reach the agent in passive mode.
Step 5. Add Host in Zabbix
In Zabbix frontend:
- Go to Configuration → Hosts
- Click Create Host
- Set hostname (must match config exactly)
- Add server IP
- Assign template: “Windows by Zabbix agent”
- Save changes
After a few minutes, the host should appear online. If it stays red, the issue is usually configuration or firewall related.
Step 6. Test Zabbix Agent Connection
Before troubleshooting in the UI, it’s better to test connectivity directly.
You can use:
zabbix_get -s 127.0.0.1 -k system.hostnameAlternatively, check if port 10050 is open:
Test-NetConnection -ComputerName localhost -Port 10050Common Mistakes When Installing Zabbix Agent
- Hostname in config does not match Zabbix frontend
- Firewall blocks port 10050
- Wrong Zabbix server IP in configuration
- Service is installed but not started
- Using passive checks without allowing inbound traffic
Most “agent not visible” issues come from these five points.
Troubleshooting
If the agent is not visible in Zabbix:
- Restart service:
Restart-Service "Zabbix Agent"- Check logs:
C:\Program Files\Zabbix Agent\zabbix_agentd.log- Verify connectivity to server IP
- Ensure correct template is assigned
FAQ
Why is Zabbix Agent not showing in dashboard?
Usually due to hostname mismatch, firewall blocking port 10050, or incorrect server IP in configuration.
How do I test if Zabbix Agent is working?
Use zabbix_get or Test-NetConnection to verify connectivity and response.
Do I need port 10050 open?
Yes, for passive checks the Zabbix server must reach the agent via TCP 10050.
Can I use active checks only?
Yes, by configuring ServerActive parameter and allowing outbound connections.
Does Zabbix Agent affect server performance?
No, it is lightweight and designed for continuous monitoring.
Can I install multiple agents?
Yes, but only in advanced setups with separate configs and ports.
Conclusion
Installing Zabbix Agent on Windows Server 2025 is a straightforward process once the configuration is done correctly. Most issues in real environments are not related to installation itself, but to networking, firewall rules, or mismatched hostnames.
After setup, you get full visibility into Windows Server performance, which is critical for production monitoring, incident detection, and infrastructure reliability.
