NetXMS Support Forum

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