Print Page - Agent on the Windows server 2012 Problem

Title: Agent on the Windows server 2012 Problem
Post by: hzdtony on January 31, 2016, 02:06:05 PM

I have a node is Windows 2012 R2,install netxms agent version 2.0.1. I defined a Object Tools,type is Agent Command, This command is PowerShell Script that on operator system execute is normal.but via node agent execute hint me timeout. I have on the node set " ExecTimeout = 2000000 "and on netxms server set "AgentCommandTimeout = 2000000",and restart both.
Windows 2012 R2 node nxagnetd.conf file as follow:

Code Select


MasterServers = 192.168.137.137
EnableActions = yes
ActionShellExec = pullinfo:powershell.exe c:\getinfo.ps1
ExternalParametersProvider=C:\getinfo.ps1:5
ExecTimeout =  2000000
ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
#LogFile = {syslog}
LogFile = c:\NetXMS\nxagentd.log
FileStore = C:\NetXMS\var
SubAgent = ecs.nsm
SubAgent = filemgr.nsm
SubAgent = ping.nsm
SubAgent = logwatch.nsm
SubAgent = portcheck.nsm
SubAgent = winperf.nsm
SubAgent = wmi.nsm
SubAgent = ups.nsm
[filemgr]
RootFolder = C:\test

the "ExternalParametersProvider=C:\getinfo.ps1:5" and "ExternalParametersProvider=powershell.exe C:\getinfo.ps1:5" same not working. this powershell script is period get system disk space usage and generate report file. How to can be as Linux system normal Work?

moreover,Windows 2012 R2 system have other network interface as "isatap.localdomain" and "isatap.{34F1D761-B32C-4AF0-936A-9C64598A8529}".this why? and when I try more than one agent command as above.The Windows nxagent service is cash,and I try start nxagent that throw error as screenshost.

Title: Re: Agent on the Windows server 2012 Problem
Post by: Marco Incalcaterra on February 26, 2016, 12:07:21 PM

Quote from: hzdtony on January 31, 2016, 02:06:05 PM
moreover,Windows 2012 R2 system have other network interface as "isatap.localdomain" and "isatap.{34F1D761-B32C-4AF0-936A-9C64598A8529}".this why?

ISATAP defines a method for generating a link-local IPv6 address from an IPv4 address, and a mechanism to perform Neighbor Discovery on top of IPv4:

https://en.wikipedia.org/wiki/ISATAP

Title: Re: Agent on the Windows server 2012 Problem
Post by: Marco Incalcaterra on February 27, 2016, 06:48:05 PM

You can filter "isatap" interface as per suggestion in this post:

https://www.netxms.org/forum/configuration/how-to-automatically-unmanage-'unwanted'-interfaces/msg19307/#msg19307

Regards,
Marco

NetXMS Support Forum

English Support => General Support => Topic started by: hzdtony on January 31, 2016, 02:06:05 PM