NetXMS Support Forum

Hi Alex,

have the developers been able to find anything in the meantime?
We're unfortunately losing track quite quickly due to the high volume of messages, as many of the monitored servers are terminal servers with a large number of users.

Best regards,
Alwin

Hi Alex,

this would disable all package changes - including the system alerts that we need to monitor. We are waiting for the development team and hope for a solution. Thank you for reopen the case!

Hi Alex,

i have pinned "Package Deployment Jobs" to the pinboard. In this view, the status of the scheduled jobs is not visible. However, if I access the "Package Deployment Jobs" directly through the configuration, the data is refreshed and suddenly all jobs are visible.

If we now try to cancel the jobs, we get the error "Request is out of state"

Update:
We can see the active jobs for a short time about 10 minutes after they start, but they run so fast that there's no way to cancle them before they disappear from the list again.

Hi Alex,

Thank you for your detailed explanation.

In our case, we cannot see the scheduled jobs and therefore cannot delete them either, as they do not appear in the list (Client 6.1.1).

As you suspected, the error is "Unable to connect to agent." This situation arose because a package was deployed to a node that is monitored only via ICMP (Agent Communication Option - "Use ICMP ping on primary IP address to determine node status"). How can we prevent this? We regularly deploy packages to the cluster that consist of a mix of agent-based and ICMP-based monitoring.

It would be very helpful if we could disable the automatic retry via a central configuration option.

best regards,
Alwin

The new overview for package deployment jobs in version 6.x and later is generally great.
However, we haven't yet found a way to stop jobs that are in the "Failed" status. The system keeps trying to run them over and over again. How can we delete these jobs? Right-clicking only allows us to hide all jobs.
Does anyone have any ideas?

Hi Filipp,

unfortunately, we cannot confirm that this fix works.
We have been experiencing this behavior since updating the NetXMS Agent from 5.0.8 to 6.1.1. Is there a setting to disable these messages during user logins?

We have also noticed that the system is now detecting more non-essential installed software, which is flooding our alarm browser.  For example:

CapturePicker 10.0.17763.1 was installed
Hello-Setup 10.0.19585.1001 was installed
File Explorer 10.0.17763.1 was installed

Is there perhaps also a way to hide specific notifications?

Thanks for your help 

Hi Victor,

has this feature been implemented yet? Or is there another way to save a password and pass it along?
Unfortunately, I can't find anything on that. Thanks for your help.

Hi @all,

we have configured two custom schedules for one parameter. 

Every 15 Minutes, Monday through Friday
*/15 * * * 1-5

Every 59 Minutes, Saturday through Sunday
*/59 * * * 6-7

The second schedule for weekenk does not work. The parameter is not queried (we see this in the history).

Can only one schedule be configured? 
Have we possibly chosen the wrong format for the second schedule?

Our NetXMS Version is 4.3.2

Thanks for your help,

best regards,
Alwin 

Hi Victor, 
 
H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems for {f3e82f6e-9df4-425d-a5d5-3a9832005b16} (Das angegebene Objekt wurde nicht auf dem Computer gefunden.)

H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems for {7d937e49-cfd5-438f-af4f-b3047d90a5c3} (Das angegebene Objekt wurde nicht auf dem Computer gefunden.)

H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems for {115b92b4-7191-491a-a9b5-93c8e9fb641b} (Das angegebene Objekt wurde nicht auf dem Computer gefunden.)

best regards,
Alwin

Hi Victor, 

we have the actual version installed but there are still many PDH errors on every node.  We have now try to solve this problem, but there is know way for us to do that. Any news on the case yet?

Thanks for your help!

best regards,
Alwin

Hi @all,

it is possible to move nodes from Cluster-A to Cluster-B? We tried with "Drag n Drop" and "Object -> Bind to...".
We would like to restructure our organizations but recreate each device takes too long.. :-( 

best regards,
Alwin

Hi Filipp,

we have tried another command, which also generate an empty line in the first output line.

Thanks for your workaround - it works great!

It would be nice if the behaviour was the same as in the previous versions.

best regards,
Alwin

Hi Victor,

the current Server an Agent version is: 4.1.404

The command needs 34ms to execute. In the agent configuration we have also added the line "ExternalParameterProviderTimeout = 60"

We try it with the following command (is this the correct syntax?)

ExternalParameterShellExec = DefenderEngineLastUpdate:powershell -Command "& {Get-MpComputerStatus | Select -ExpandProperty AntivirusSignatureLastUpdated}"


We added also the following parameters to the agent configuration file:

SubAgent = wineventsync.nsm
DebugTags=winsyncevent:6

Now we have logs in the windows event log but no entrys for the executed external parameters.

best regards,
Alwin

Hi all,

since NetXMS Agent Version 3.9.178 (last working version) we do not get values for the following external paramenter anymore

ExternalParameter = DefenderEngineLastUpdate:powershell -Command "& {Get-MpComputerStatus | Select -ExpandProperty AntivirusSignatureLastUpdated}"

If we run the powershell command directly on the node, it works without any problems.
Other powershell paramenter are however correctly transmitted and displayed - for example:

ExternalParameter = Defender:powershell -Command "& {Get-MpComputerStatus | Select -ExpandProperty RealTimeProtectionEnabled}"

We have no idea anymore and suspect that there is a bug or changed syntax in netxms. Does anyone have the same problem?

best regards,
Alwin