<![CDATA[Windows Registry]]>I can't find any native way of reading a registry key value.
Doing so with the "reg" shell is awkward as it returns more information than just the value.
This can be done with WMI, but a native way will be so much nicer.

Dan

]]>https://forum.netxms.org/topic/1362/windows-registryRSS for NodeFri, 13 Nov 2026 08:59:10 GMTFri, 16 Sep 2011 09:04:12 GMT60<![CDATA[Reply to Windows Registry on Mon, 03 Oct 2011 07:51:37 GMT]]>Hi Victor,

Don't worry about it, it can happen to all of us 🙂
BTW, you suggested I could test an Event Log related error by providing me a debug version for me to use. If you can provide me with information to where I can grab it, I would be more than happy to test is.

Regards,

Dan

]]>https://forum.netxms.org/post/6058https://forum.netxms.org/post/6058Mon, 03 Oct 2011 07:51:37 GMT<![CDATA[Reply to Windows Registry on Mon, 03 Oct 2011 07:45:41 GMT]]>Hi!

Sorry, it's my failure 😞 I completely forgot about it. I'll made a patch for agent.

Best regards,
Victor

]]>https://forum.netxms.org/post/6057https://forum.netxms.org/post/6057Mon, 03 Oct 2011 07:45:41 GMT<![CDATA[Reply to Windows Registry on Sun, 02 Oct 2011 08:01:11 GMT]]>Hi,

After upgrading to 1.1.5 I don't see a DCI for registry inquiry. WinNT and WinPerf and WMI subagent are loaded.
What am I doing wrong?

Regards,

Dan

]]>https://forum.netxms.org/post/6053https://forum.netxms.org/post/6053Sun, 02 Oct 2011 08:01:11 GMT<![CDATA[Reply to Windows Registry on Fri, 16 Sep 2011 10:31:10 GMT]]>Hi!

I could implement it easily, I just never thought about that. Will do this for 1.1.5 agent.

Best regards,
Victor

]]>https://forum.netxms.org/post/5970https://forum.netxms.org/post/5970Fri, 16 Sep 2011 10:31:10 GMT