NetXMS Support Forum

Hi,

Then thing is that this list is updated on node's configuration poll. You've probably tried this after server restart, when not all nodes went through the conf poll. However, in templates a joint list of parameters from all nodes is shown, so as soon as first node had conf poll this list has some entries.

It's better to add check for $node:

return $node && $node->isAgent && $node->platformName like "windows-*";

the reason is that there are some other types of object - clusters, sensors, collectors on which templates can also be applied, but there will be no $node on these objects.

You can find all out-of-the-box templates here: https://github.com/netxms/netxms/tree/master/contrib/templates

Note, that if you want to import them into NetXMS that is older then 5.x, you need to switch to stable-4.6 branch as there are differences in the scripting language.

Consulted with developers, when configuration is parsed the parser does not know, if a parameter is single-value one (like EnableWatchdog) or multiple-value one (like MasterServers). So parser stacks all the values it finds together, that's why it's seen this way in the running configuration.

When agent needs the value of specific parameter, it will take the last value if it's single-value parameter. So in your case it will take EnableWatchdog = no, as it's last in the list.

You can check this, if you enable DebugLevel = 6, then in agent log you'll see
2025.09.11 15:58:09.499 *I* [watchdog           ] Watchdog process startedif watchdog is enabled.

You can easily test it - just take any node, select Execute script from the context menu and paste your script there. Your script will be executed in the same way as when a template executes it on nodes.

In addition, when you execute it that way you can use println() commands to print, so you can use it for debugging purposes.

Here's a fixed version:

if (!$node)
   return false;

pn = $object.platformName.toLowerCase();
if (pn != null && pn.startsWith("windows"))
   return true;

sd = $object.sysDescription.toLowerCase();
return (sd != null && sd.contains("windows"));
$object always exists, so there's no need to check for that. NXSL never had LowerCase() or StrStartsWith() functions, did you use an AI to generate this?

Could be that during the execution of the first script it deleted all the duplicates.

Hi, 

The problem is that "apt upgrade" automatically started nxdbmgr background-upgrade.
But there's currently no lock mechanism, so starting it manually ended up in it running two parallel processes of it. 
Lock will be added in a future version. Currently just don't run nxdbmgr background-upgrade after the upgrade (you can check with ps command that it actually running). 

Hi!

Sorry, it took a while, we've had some vacations here. 

I've replicated this behavior if there's more then one path of inheritance for the custom attribute - e.g. a node is present in two containers. Created a ticket for that: https://track.radensolutions.com/issue/NX-2831

You probably have several hierarchies under Infrastructure which contain same nodes in them. If so, for now the fix could be to avoid multy-path inheritance by creating custom attributes only on one container under Infrastructure. The reason is that currently custom attributes are not handled correctly in such situation, there's another ticket for that, possibly related to the one I've just created: https://track.radensolutions.com/issue/NX-2717

Log should be specified as:

*Microsoft-Windows-TaskScheduler/Operational

(if you open Properties for that log in Windows Event Viewer, the correct name is in the Full Name field)

Table DCI summary tables work, I've tried in the new API, but it should be same in the old one under /summaryTable/adHoc

curl -s -X 'POST' 'http://127.0.0.1:8000/v1/dci-summary-tables/adhoc-query'  -H 'Authorization: Bearer xxxxxxxxxxxxxxxxxxx' -H 'Content-Type: application/json'  -d '{ "objectId": 2, "tableDefinition" : { "flags": 2, "dciName": "Network.Interfaces" } }'
P.S. flags are the following:
/
 * Summary table flags
 */
#define SUMMARY_TABLE_MULTI_INSTANCE      0x0001
#define SUMMARY_TABLE_TABLE_DCI_SOURCE    0x0002

/
 * Summary table column flags
 */
#define COLUMN_DEFINITION_REGEXP_MATCH    0x0001
#define COLUMN_DEFINITION_MULTIVALUED     0x0002
#define COLUMN_DEFINITION_BY_DESCRIPTION  0x0004

Do you see file(s) with configuration from your policin in this folder?:
C:\Windows\System32\ config\systemprofile\AppData\Local\nxagentd\config_ap

(files have .xml extension, but inside there should be plain-text agent configuration). 

There's StartupDelay parameter in agent config. Setting it to some time in seconds should prevent server connection to the agent for that time. Pls give us update if this helps. 

Well, not so sure now, will check how this works. But don't think it's currently exposed to the API

For historical reasons all events, also related to specific interface are generated on the node object. 
Object selector in EPP currently allows selection of interfaces, but this is a bug, this will be fixed. 

If you don't need events for specific interfaces you can
- change interface expected state to "Ignore"
- unmanage an interface
- if you still need this in EPP, it could be done by EPP filter script