Hi,

There are plenty other CMA checks available for Windows.

The procedure has been updated.

You can also have a look on our documentation.

Regards,

Hello,fmattes, 

Tthank you. I was just looking at this documentation yesterday, and I didn't think I'd seen the details of the CPU and RAM (...) commands.

Thank you very much for this update.

We agree that we still need to manually create the checks, or is it possible to download:

centreon-pack-operatingsystems-windows-centreon-monitoring-agent.deb in open source?

You are welcome ​@Christopher ! 

Monitoring connectors are part of the IT or Business editions.

In Open Source edition, you need to create et update templates manually.

fmattes, your responsiveness is greatly appreciated!

 

For your information, I configured all the checks and templates using a script (CLAPI).

In addition, I set up a Windows test host with CPU, RAM, and Storage checks.

After restarting the agent, no changes were observed.

 

I’m not sure if this issue is the same as the one described here:
https://thewatch.centreon.com/centreon-monitoring-agent-61/probleme-de-check-client-centreon-sur-windows-4947

 

Here you can find the CMA debug logs : 

/2025-09-02 20:20:46.343] .centreon-monitoring-agent] ginfo] imain_win.cc:219] centreon-monitoring-agent start
<2025-09-02 20:20:46.344] .centreon-monitoring-agent] gdebug] egrpc_client.cc:52] client this=0x20fbea91c10 activate compression deflate
<2025-09-02 20:20:46.344] .centreon-monitoring-agent] ginfo] igrpc_client.cc:68] encrypted connection to centreon.primaxion.fr:4317 cert: ..., key: ..., ca: ...
<2025-09-02 20:20:46.357] .centreon-monitoring-agent] gdebug] egrpc_client.cc:88] set max message length to 4194304
<2025-09-02 20:20:46.358] .centreon-monitoring-agent] gdebug] escheduler.cc:56] scheduler start 0x20fbf58dfc0
<2025-09-02 20:20:46.358] .centreon-monitoring-agent] gdebug] ebireactor.cc:52] create client this=0x20fbf590dc0 peer:centreon.primaxion.fr:4317
<2025-09-02 20:20:46.410] .centreon-monitoring-agent] gdebug] ebireactor.cc:141] 0x20fbf590dc0 client 44 bytes sent
<2025-09-02 20:20:46.594] .centreon-monitoring-agent] gdebug] escheduler.cc:223] all checks will use a time step of 199632859231/10000000]s
<2025-09-02 20:20:47.594] .centreon-monitoring-agent] gdebug] escheduler.cc:313] start check for service 
 2025-09-02 20:20:47.595] 7centreon-monitoring-agent] adebug] dprocess.cc:192] start process: o"cmd.exe", "/C", "echo", "Centreon", "Agent", ]
]2025-09-02 20:20:47.630] 7centreon-monitoring-agent] adebug] dprocess.cc:209] pid:13796 process started: a"cmd.exe", "/C", "echo", "Centreon", "Agent", ]
]2025-09-02 20:20:47.630] 7centreon-monitoring-agent] adebug] dprocess.cc:446] fail read from stdout of process r"cmd.exe", "/C", "echo", "Centreon", "Agent", ]: The pipe has been ended
d2025-09-02 20:20:47.630] 7centreon-monitoring-agent] adebug] dprocess.cc:506] fail read from stderr of process r"cmd.exe", "/C", "echo", "Centreon", "Agent", ]: The pipe has been ended
d2025-09-02 20:20:47.700] 7centreon-monitoring-agent] adebug] dprocess.cc:321] pid:13796 end of process r"cmd.exe", "/C", "echo", "Centreon", "Agent", ], exit_code=1
12025-09-02 20:20:47.700] 7centreon-monitoring-agent] adebug] dscheduler.cc:333] end check for service  command cmd.exe /C echo Centreon Agent

 

and for exemple :