Windows server not being discovered

[bloodyskullz]

Hi All,

I got a windows server that is not being discovered even though I have both the discovery actions and discovery rules in place.

I have checked the following:

Windows zabbix service is running and set to automatic - successful
Windows server can telnet the zabbix server on port 10051 - successful
Windows server can ping zabbix server - successful
Zabbix server can ping windows server - successful
Windows zabbix config file has the server and passive config pointing to the zabbix server
I attached pictures for the discovery rule and action.

The same rules and actions are being used for linux servers which have been successful, the windows is the only problem. Windows zabbix logs don't indicate anything that point me in the direction of a resolution.

Any thoughts?

[Markku]

Did you test that the Windows agent port 10050 is reachable from the proxy? I see your discovery rule uses proxy but you say that you only configured Zabbix server in the agent's Server directive.

Markku

[bloodyskullz]

Thanks for posting, yes I tested this and the proxy is able to connect to the windows server via 10050. Connected without issues so I know the windows firewall isn't problematic.

[Markku]

So you fixed this?

Windows zabbix config file has the server and passive config pointing to the zabbix server

And no problems anymore?

Markku

[bloodyskullz]

Oh sorry, config file is pointing to the proxy server and its still not being detected by the main server.

[bloodyskullz]

It seems a manual addition of the server to zabbix works fine and detects the agent without issues after a bit (couple of mins).

When i go to the monitoring section, I do see that the server was discovered based on the rules I created. Anyone have ideas on what to do?

[Markku]

In your discovery action, you match system.uname with "Windows". Have you checked that your Windows agent returns system.uname with that value?

Markku

[bloodyskullz]

Is there a powershell command to check this value?

[Markku]

https://www.zabbix.com/documentation/current/en/manpages/zabbix_agent2

zabbix_agent2 -t system.uname

(Depending on your path settings you may need to add the path to the executable)

Markku

[bloodyskullz]

https://www.zabbix.com/documentation.../zabbix_agent2

zabbix_agent2 -t system.uname

(Depending on your path settings you may need to add the path to the executable)

Markku

I did have to navigate to the path where the agent is stored first but it came out with this value:

zabbix_agent2.exe -t system.uname
system.uname [s|Windows HOSTNAME 10.0.20348 Microsoft Windows Server 2022 Standard x64]

EDIT: I tried changing the discovery action to agent.hostmetadata and that didn't make a difference.

[Markku]

I tried changing the discovery action to agent.hostmetadata and that didn't make a difference.

How is host metadata configured in the agent?

Markku

[bloodyskullz]

I removed the comment behind the "hostnametadata" and added "=name of server_ip address", every other option for the host metadata is still commented.

Same thing I did with the linux vm's

[Markku]

So I guess you now got it working?
- Changed the agent configuration
- Also adjusted the discovery rule to match to the correct string

Markku

[bloodyskullz]

Nope, still not working actually. I have tried everything I can think of and nothing is working.

[Markku]

Please show the current discovery rule and agent configurations.

Markku