While I did not see anything in either of the release notes we are running 4.1.377 and this issue appears to be resolved.  Suspect there was some change and maybe not significant enough to make the notes.  Thanks!

Was hoping to see how I can setup the windows logs to show me specifically users logged in and logged off. ANy chance anyone had set this up? or done this??

Yes, the VLANs are reported against the switchports correctly with both GENERIC and CISCO-SB driver [here I am discussing CBS350-24FP-4X]. The "Location" field is no longer populated once switching to CISCO-SB. I think this is not a problem, with GENERIC it shows the location as "0/1/0/29" for interface te1/0/1, I am not sure that location is correct. [image: ksnip_20220613-110728.png]

A fixed management client has just been released.

Hi, Filipp. our new production NetXMS server is up and running. Thanks a lot to Victor and you for your kind help. Kudos. Finally, What I did to fix the connection error window in the latest post reply. I updated the NetXMS client. Problem solved. My best Jose

Will do.

Make sure you put password in single quotes. Also, user should have appropriate access rights ("access server console" in global system access rights). Best regards, Victor

Actually 6733 (first part of primary key) should be ID of the node this package belongs to. Best regards, Victor

It is planned to rework file upload mechanism in the near future - when this will be done, we will double-check that all issues like this one are fixed.

Thanks , Dmitry Martynov Resolved Date None→7 months ago (01 Nov 2021 14:12) Fred

Many thanks Egert

Oh.. I was right clicking the items not double clicking previously. That is why I could not find those. :-X Thank you very much Filipp. Best regards. Azur

Thank you Victor! Unless it is your own code..  Netxms fixes bugs the fastest!  

Great work, Victor. Added snmp.ignore.ipAddressTable as custom param on this example Sonicwall, re-polled and it now shows the correct IPs after a "Configuration (full)" poll.

   Brilliant, thanks Victor

Many thanks! Wish all those litle snipets of info would be published.

Hi, looks like nobody checked that client proxy actually compiles. Do you really use it? If not, just remove --with-client-proxy from configure (we will fix compilation anyway though). Best regards, Victor

Not each output of powershell begins with empty line, only this specific command does. You can filter output further, probably from powershell itself as well, but I don't know how (not using it). However, command line pipe should work as well (I assume you are interested in line with version number): ExternalParameterShellExec = ExchangePatchNumber:pwsh -Command { Get-Command Exsetup.exe | ForEach {$_.FileVersionInfo} } | find "ExSetup.exe" Best regards, Victor

Thank you, Viktor! That worked just fine.

OK, Unifi APs don't support this MIB.