<![CDATA[Unsupported DCIs change to disabled]]>I have a situation where a DCI  becomes disabled on many nodes due to an unsupported value, because I am pushing out an updated script.  Up to this point, I have been using the management console to re-enable the DCI on each node, which resolves the issue, but is very time consuming because I have to drill down into each node.  Is there a way to have a node recover from an unsupported value on it's own (automatically re-enable the DCI), or be able to select many nodes at one time and re-enable the DCI?  Thanks, Andrew

]]>https://forum.netxms.org/topic/4767/unsupported-dcis-change-to-disabledRSS for NodeFri, 13 Nov 2026 14:04:41 GMTThu, 20 Oct 2016 16:21:17 GMT60<![CDATA[Reply to Unsupported DCIs change to disabled on Fri, 21 Oct 2016 11:44:33 GMT]]>Hi,

actually server will periodically (every 10th poll) check unsupported DCIs and re-activate them if agent responds. You can also write nxshell script to walk all nodes and re-activate all unsupported DCIs.

Best regards,
Victor

]]>https://forum.netxms.org/post/21237https://forum.netxms.org/post/21237Fri, 21 Oct 2016 11:44:33 GMT