<![CDATA[How to automatically unmanage "unwanted" interfaces]]>Hi,

In most of Windows installation NetXMS discover the "isatap.*" interface, since I'm not interested in monitoring those interfaces I manually put them into unmanaged state but doing this for hundreds nodes is a boring task.

Has anyone a suggestion on how to automatically set to unmanage some nodes interfaces that meets specific requirements in the name?

Regards,
Marco

]]>https://forum.netxms.org/topic/4329/how-to-automatically-unmanage-unwanted-interfacesRSS for NodeFri, 13 Nov 2026 20:48:23 GMTSat, 27 Feb 2016 14:30:58 GMT60<![CDATA[Reply to How to automatically unmanage "unwanted" interfaces on Sat, 27 Feb 2016 15:38:26 GMT]]>It works fine! 🙂

Thank you very much!

Marco

]]>https://forum.netxms.org/post/19308https://forum.netxms.org/post/19308Sat, 27 Feb 2016 15:38:26 GMT<![CDATA[Reply to How to automatically unmanage "unwanted" interfaces on Sat, 27 Feb 2016 14:59:20 GMT]]>I use a Hook script to not create these interfaces

"Hook::CreateInterface":

//
// $node is current node object and $1 the interface
// return false blocks interface creation
// needs NetXMS >= V2.0

// no Teredo, isatap, Bluetooth interfaces
if ($1->name ~= "(?i).*Teredo.*|.*isatap.*|.*Bluetooth.*|sit0") {
   return false;
} else {
   return true;
}
]]>https://forum.netxms.org/post/19307https://forum.netxms.org/post/19307Sat, 27 Feb 2016 14:59:20 GMT