TLDR: Use $ErrorActionPreference = "Stop" so the agent knows one of the script's command failed. Found the root cause, but I forget to post it here. Despite several issues and discussions on winget-cli's github suggesting it can be run in system context it turns out that it is in fact impossible. So when i tried to execute it with the agent it returned instantly with a non zero exit code, but the ps script returned normally due to the lack of $ErrorActionPreference = "Stop" which would have caused the agent to recognise the script had failed. For now I'll use chocolatey with a custom caching proxy that rewrites packages - so even external resources can be cached locally by nginx - until MS figures out how to create a usable package manager. P.S. Thank you for the tip about auto termination, I'll keep that in mind. Also sorry for the late reply.

Thank you!!

Thank you so much!

Historically SecondsToUptime() function was introduced before measurement units were added. So currently you can select  "Uptime" in measurement units and have it without transformation script. Threshold <= 600 should work. Also, you can try threshold with function "Diff with previous value", 1 sample, < 0.

Community string from node properties is used for read operations during polls and data collection. Write operations, as far as I know, could be performed from NXSL scripts only and in createSNMPTransport method (https://www.netxms.org/documentation/nxsl-latest/#_instance_methods_13) you can specify custom community string. You can store this community string in a node custom attribute.

Hi, Everything is OK. Thanks!

Hi, Everything ok with the display. Thank you very much!

OK, thanks a lot. Fred

There are agent metrics for that, e.g. File.Time.Modify(/etc/passwd) https://www.netxms.org/documentation/adminguide/appendix.html#file-time-modify Metric would return unix time. First thing is to create Data Collection Item on a node with that metric. Then you can add threshold, if you need a notification when modification time changes, you can use function "Diff with previous value", operation "!= : not equal to". Then rule in event processing policy is needed, we can discuss this later on.

Hi! In properties of map object on Map Appearance tab there's Drill-down object field where you can select the dashboard. This setting is saved in node's (or other object properties), so if node is placed to another map this setting there will be same.

can you share this nxshell script? I could not find the method for disabling DCI

many thanks, but I found more row duplicate   ... then I adopted the query below... delete from config a using config b where a=b and a.ctid < b.ctid; it works well... also for all duplicate on db.  I resolved.

I see..  Thanks for the info I will give the custom attributes a go as it does seem like a much cleaner solution appreciate it.

thanks so much.

It didn't make any difference. Same error.

View state saving is planned for 5.0 which should be out in January. Rearranging items might require some work, so could be expected somewhere later.

Thanks Filipp, You are correct, I had missed the last line. This now gives me a path that I can experiment with. Thank you again, Phil.

The problem is that single quotes are get lost somewhere during all this process. You can specify using "" which will be escaped to " in the end, e.g.: ExternalMetric=RegQuery.EBTransfer720:""D:\Program Files\NetXMS\custom\CheckRegKey\CheckRegKey.exe"" "HKLM\SOFTWARE\WOW6432Node\Aucotec\Engineering Base\7.2.0\Server\Files" "ImageFilePath" But better way is to use new (and not yet documented) docker-style syntax: ExternalMetric=RegQuery.EBTransfer720:['D:\Program Files\NetXMS\custom\CheckRegKey\CheckRegKey.exe', 'HKLM\SOFTWARE\WOW6432Node\Aucotec\Engineering Base\7.2.0\Server\Files', 'ImageFilePath'] currently that works with single quotes (') only, but in next patch release double quotes (") will also be supported.

Appreciate it thanks Filipp.  Fedora IoT has been an interesting platform for some appliances we've been testing with netxms and some containerized apps.

Ah, right, # is treated as beginning of comment. You can specify password in double quotes (" "), then it can contain # character. I'm glad that it worked.