NetXMS Support Forum

In my environment I only use SubAgent for wineventsync.nsm. I don't use Logwatch. I also don't use the agent policy (I set everything via the INI file of the nx agent).
So if I make a policy and use the logwatch subagent, can I also collect Windows events?

Hi Uldis, I tried several possible where to specify the ProcessOfflineEvents parameter with a value of true, but none sent the event after running nxagent again.
I tried
First option:

[Logwatch]
ProcessOfflineEvents = true

[WinEventSync]
EventLog = Application

[WinEventSync/Application]
ProcessOfflineEvents = true
WinEventSync = *
Second
[WinEventSync]
EventLog = Application
ProcessOfflineEvents = true

[WinEventSync/Application]
WinEventSync = * Last
[WinEventSync]
EventLog = Application

[WinEventSync/Application]
ProcessOfflineEvents = true
WinEventSync = *By the way, the Logwatch section is only for the logwatch subagent, and for the Windows event is the WinEventSync section. Or this section is common for both subagents?

In many text field in NXClient (for example script text filed), is not possible use Ctrl + A, Ctrl + Z and Ctrl + Y.
Please add support for this actions.

If I mistakenly enter a semicolon /;/ instead of a comma (,) in a scheduled File.Upload job and the job starts, the netxmsd service crashes and cannot be started anymore (it crashes itself after a while)

When the deployment is run as a scheduled task, the log writes:
2024.10.08 17:45:00.732 *D* [packages ] CreatePackageDeploymentTask: invalid package id 0
2024.10.08 17:45:00.732 *D* [packages ] ExecuteScheduledPackageDeployment: cannot create deployment task for package

• (RCC = 36)

If I run the deployment manually, everything goes correctly and the package is installed. I tried both the package name as a parameter and its index.

Hi Victor, thank you for the explanation. I was thinking that when the execution object (node) can be selected, then the action on the agent side can be executed.

I used the NetXMS Client, in the Configuration view I created a One time execution scheduled task. I found a post that address the same problem, but also has no solution, just a workaround.

I created an agent action. If I run it through a script or as object tools, everything works correctly. But if I schedule the action, nothing is executed and an event is logged in the log
2024.10.02 16:03:00.033 *D* [action            ] Cannot execute scheduled action

• on node [187]: original event is unavailable

2024.10.03 16:03:00.033 *D* [client.session.0  ] Sending message CMD_NOTIFY (48 bytes)
2024.10.03 16:03:00.038 *D* [scheduler          ] AdHocScheduler: sleeping for 3600 seconds

Windows events that occur when an agent is disabled are not synchronized when the agent is started. The documentation says that the agent stores the value of the last event in the registry and sends all events since the last synchronization on startup.

Windows Event Log parser ignores if I enter a range (for example 80-90) in the text field. If I enter a single value, everything works correctly. But the documentation says that a range can be entered.

Does the NXSL script support a function to make a request to a web service and return the retrieved data and HTTP code?

Please add option to use properties file for NXShell. Source

NXShell does not support the use of properties file? It is better for me to use a properties file rather than an environment variable or a command line.

I want to set NXShell properties through the .properties file (not through the command line). I have tried nxshell.porperties and netxms-client.properties, but they don't work. What is the correct name of the properties file for NXShell?

Process.CountEx metric is not working properly. If I use only the first argument and don't specify the other optional ones, it returns an incorrect process count.
If I specify the process owner name, it returns an incorrect count (all processes are returned but the owner name is ignored).
As shown in the screenshot - the metric is set to Process.CountEx(cmd.exe), realistically there are 6 cmd.exe running under different users, but the returned value is 44. Other arguments when I enter, also the metric returns incorrect values.
Process.Count metric works correct ly and returns the correct number of processes.