NetXMS Support Forum

Good afternoon, Victor,

Below is the link for Portuguese of Brazil netxms tool.
My team and me have implemented here in the company earlier this year the tool and we are using.
This is a way to thank you for sharing the tool that we use.

We look forward for the Portuguese version and probably will need to adjust other settings but as soon as the first version is available we set and send the appropriate corrections.

In more thank you.

http://bit.ly/netxmsptbr

Quote from: Victor Kirhenshtein on June 13, 2016, 11:30:08 PM
Hi, sorry for late reply! Portuguese translation would be awesome. Attached is archive with Portuguese language files.
Best regards, Victor

Hi Victor,
We are working on translation to portuguese but we are with a doubt.
The expressions have & for example:  "Show &object details" this & is used in which context?
We need to understand to know if it is necessary to adjust the translation.
Tks!

Nice!!

it's possible to use HEAD parameter in ServiceCheck.HTTP request?
If possible, with the HEAD method to minimize traffic, bringing only the header.
Tks!

Hi tomaskir,
Tks again for reply.

I used custom attribute. Created with name "Farm"
In action configuration add:  Farm: %{farm}

https://wiki.netxms.org/wiki/UM:Event_Processing

Hi all,

It's possible set comments on nodes or in containers and then make reading these comments for sending alerts?
The same thing to custom attributes.

Below a exemple of alerts we send:

Server: %n \\n
IP: %a \\n
Data: %t \\n
Event: %<dciDescription> \\n
Current Value: %<currentValue> \\n
Threshold: %<thresholdValue>

Hi,

I can help translate to portuguese if needed.
Just send a files to me and i can translate it

Make a shellexec to cmd.
Use grep for windows and look in C:\windows\windowsupdate.log

If are you using windows 10:

Windows Update logs are now generated using ETW (Event Tracing for Windows).
Please run the Get-WindowsUpdateLog PowerShell command to convert ETW traces into a readable WindowsUpdate.log.
For more information, please visit http://go.microsoft.com/fwlink/?LinkId=518345

Hi,

Install agent on server.
Then create a dci to monitor services.
Look in this thread have alot of information:

https://www.netxms.org/forum/configuration/status-return-codes-for-windows-services/

Hi Alex,
Tks for reply.
With this option we see alot of information in screen.
When I think about the kiosk mode, would be something like direct link to dci table or just a direct link to a graph.

Tks,

Hi,

Sure.
You can use Netxms as syslog server and parser windows events.

https://wiki.netxms.org/wiki/UM:Log_Monitoring

Hi,

What version of Windows are you using?
Are you trying to monitor Windows default backup solution or 3rd party?
You can create a shellexec to CMD and use a command Wbadmin to get results of backup.

https://technet.microsoft.com/en-us/magazine/dd767786.aspx

It's possible create a kiosk mode to web version or a viewer?
Show only a Predefined Graphics or a summary table, without menus etc..

Tks

Hi, it's me again

I Performed the update to version 2.0.3 netxms. And I used the update of the agents (Windows) centrally through the NPI.
Was performed successfully 70% both x86 as x64 Windows versions. However in the other 30% error occurred in the deploy.

In all cases the error was equal, the older version of the agent (2.0.2) has not been removed.
When you try to remove the agent manually (log in the server) error message appeared.
To install the new version was necessary to restart the servers after the process the 2.0.3 version was installed successfully.

Below is the image as well as the errors encountered in application logs.
The purpose of the post is trying to help so that the problem be identified:)

Anyway the success rate was very high which facilitated the upgrade process.     

Error from image:
Faulting application nxagentd.exe, version 0.0.0.0, time stamp 0x56a7b06b, faulting module libnxdb.dll!?
DBSetDebugPrintCallback@@YAXP6, version 6.0.6002.23154, time stamp 0x51da29f7, exception code 0xc0000139,
fault offset 0x00009f5d, process id 0xa80, application start time 0x01d18c32df60f7e0.


Log application:
Activation context generation failed for "C:\NetXMS\bin\nxagentd.exe".
Dependent Assembly Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",
version="8.0.50727.6195" could not be found. Please use sxstrace.exe for detailed diagnosis.

Tks,

Hi,

Tks for fast reply.
I did it. If it occurs again, I warn:)
Thank you very much.