<![CDATA[watch service and start automatically]]>Hello,
i want to watch a service called FileWaveWinClient.
The Alarm works fine, but the Server action does not work.

In agent´s config file I added this line:
ActionShellExec = StartFileWaveService:"C:\Windows\system32\net.exe" start FileWaveWinClient

I tried also:
ActionShellExec = StartFileWaveService:net start FileWaveWinClient

In Actions Configuration I added
Name: Start_FileWaveWinClient_Service
Type: Execute command on remote node via agent
Remote host <empty>
Agents´s action: StartFileWaveService
(See attachment "Action Configuration.png")

I create a Event Processing Policy
Events: ... Process not running
Alarm - this configuration works fine. The Alarm is working
Server Actions: Start_FileWaveWinClient_Service - does not work
(See attachment "Event Processing Policy.png")

The Alarm works fine, but the Server action does not work.

Thank you
Rainer

Action Configuration.png

Event Processing Policy.png

]]>https://forum.netxms.org/topic/7499/watch-service-and-start-automaticallyRSS for NodeFri, 13 Nov 2026 09:55:30 GMTWed, 24 Aug 2022 07:00:10 GMT60<![CDATA[Reply to watch service and start automatically on Thu, 25 Aug 2022 10:02:51 GMT]]>I was looking for a bug that isn't a bug at all. The system is already working fine. I just thought that this line is added after agent restart. You can check the success quite simply by reading out the "Supported actions" on the client, and the desired one is there

Many many Thanks for this perfect support
Rainer  😄 😄 😄 😄 😄

]]>https://forum.netxms.org/post/31804https://forum.netxms.org/post/31804Thu, 25 Aug 2022 10:02:51 GMT<![CDATA[Reply to watch service and start automatically on Thu, 25 Aug 2022 09:48:20 GMT]]>Yes, I did not mention this - config policies are not actually modifying the main agent config file. Each policy confiig is kept in a separate file in config_ap under agent's DataDirectory (by default C:\Windows\System32\ config\systemprofile\ AppData\Local\nxagentd on windows). When agent starts it reads these files. In recent agent versions it dumps actual configuration into it's log file, so your line should be visible there.

]]>https://forum.netxms.org/post/31802https://forum.netxms.org/post/31802Thu, 25 Aug 2022 09:48:20 GMT<![CDATA[Reply to watch service and start automatically on Thu, 25 Aug 2022 04:49:52 GMT]]>I have made a Template with automatic bind to all clients with running service I need (FileWaveWinClient)
In this Template I choose Agent Policies and created a new "Agent Configuration" policy called StartFileWaveClientService
I only inserted this (1) line:
ActionShellExec = StartFileWaveService:"C:\Windows\system32\net.exe" start FileWaveWinClient
(see AgentPolicy.png)
For test I removed 2 clients and poll "Automatic bind"
The 2 (test) clients added automatically to this Template

Until now every thing works perfect - thank you

But the agent config file at the new clients is not modified and the line I need is not in agent´s config file
I waited a long time

Thank you
Rainer

AgentPolicy.png

]]>https://forum.netxms.org/post/31797https://forum.netxms.org/post/31797Thu, 25 Aug 2022 04:49:52 GMT<![CDATA[Reply to watch service and start automatically on Wed, 24 Aug 2022 13:52:32 GMT]]>Have a look at "Agent policies" in templates. One of the option is "Agent configuration" policy, where you can specify agent config lines. When template is added to a node, these config lines will be sent to agent and will start working after agent restart.

]]>https://forum.netxms.org/post/31795https://forum.netxms.org/post/31795Wed, 24 Aug 2022 13:52:32 GMT<![CDATA[Reply to watch service and start automatically on Wed, 24 Aug 2022 13:29:24 GMT]]>Thank you very much  🙂 😄
No it works fine

I have the problem to add this line to agent config file

ActionShellExec = StartFileWaveService:"C:\Windows\system32\net.exe" start FileWaveWinClient

To all of my clients.
Only to add, not to send each client the same config file

Please help and thank you so much
Rainer

]]>https://forum.netxms.org/post/31794https://forum.netxms.org/post/31794Wed, 24 Aug 2022 13:29:24 GMT<![CDATA[Reply to watch service and start automatically on Wed, 24 Aug 2022 12:28:45 GMT]]>In action properties you need to specify hostname/ip address of the machine where your netxms agent is running. This is made so for greater flexibility, as event may be coming from one node, but you might need to execute the action on another system, for example.

You can use %a macro in "Remote host" field - in this case IP address of node where the event is coming from will be used.

]]>https://forum.netxms.org/post/31792https://forum.netxms.org/post/31792Wed, 24 Aug 2022 12:28:45 GMT