NetXMS Support Forum

I'd suggest to experiment a bit - you can make a new template with just one DCI and see what happens when you export or import that.

For duplicates - it's controlled by GUID of each template that is included in the .xml file. So if you import it back, it will replace the original template, even if the name is different. But if you change the GUIDs in the .xml, it will import as a new one.

Only "Replace templates" option is relevant if your .xml contains only templates. If it's not checked, then if template already exists, no changes will be done to it.

Just tried a fresh install on Win 10, HTTP / HTTPS buttons work from a dashboard. But other elements of dashboard could affect things.
Do you have any error messages in C:\Users\<Your username>\.nxmc4\nxmc.log when you try to use these dashboard buttons?

Hi,

git-enabled configuration might be nice, but then comes a question what should be included like templates and other stuff, so this may end up in serious development effort and the resources are limited.

What can be done currently - there's nxshell api that allows to do everything that management client can do. So you can import and export script library scripts (and get list which scripts are in the system).

Yes, it takes some effort to renew them and there's always no time for that. Which images are most problematic, you can just post image URLs from web version of docs or name of chapter.

Hi,

Can you add
DebugLevel = 6
to agent's log and collect the log for the period of time while package upgrade is happening?
You can share the log file via private message if needed.

The thing that I forgot to mention - in Configuration->Server configuration there's parameter named Server.ImportConfigurationOnStartup. Setting it to Always and restarting the server will revert built-in templates to their current versions (they are stored in /usr/share/netxms/templates/ on the server).

Setting "Only missing" has same meaning as not selecting "Replace templates" in the manual import - if given template (they are identified by GUIDs) is already present in the system, no changes will be made to it.
So if you have "Only missing" setting, delete a template and restart NetXMS - template will reappear (but all historical data on nodes will be gone).

IOS client is published to the App Store. It's still beta, so some things may not work properly.

It needs new API that is built in into NetXMS server. Latest server version is recommended, not that for Postgres users it's not recommended to upgrade to 5.2.5 as there's an issue there, pls wait till 5.2.6.

Quick setup guide:
- add "Module=webapi" to netxmsd.conf, module listens on port 8000 by default. You can change it:
[WEBAPI]
ListenerPort=12345

Please note, it's unencrypted HTTP!
- add nginx, reproxy, traefic - or any other ssl offloading app in front of it.
- connect to the API endpoint.

The progress bar above the buttons in this dialog should get filled with blue when the file got uploaded, then OK button would become active. This means that you have some issue with browser not uploading the file. Check security settings, may be try another browser or you can try the Desktop Client.

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.