<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Windows Forwarded Event Source]]></title><description><![CDATA[<p dir="auto">I have a windows event collector server and I want to get the forwarded events from that server. The difference is that there is a column named computer which holds the originator pc of that event. However in event viewer I cannot see that info as source. I see the windows event collector server as source (as expected).</p>
<p dir="auto">Is there a way to set that computer field (I can get the value using %&lt;number&gt;) as source. Or I have to create duplicate events for forwarded events and put computer info in event string.</p>
]]></description><link>https://forum.netxms.org/topic/6249/windows-forwarded-event-source</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 12:51:35 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6249.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 31 Oct 2019 09:24:58 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Windows Forwarded Event Source on Mon, 04 Nov 2019 09:20:14 GMT]]></title><description><![CDATA[<p dir="auto">Another option to avoid storing double events is to remove "write to event log" option from original event.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/26867</link><guid isPermaLink="true">https://forum.netxms.org/post/26867</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Mon, 04 Nov 2019 09:20:14 GMT</pubDate></item><item><title><![CDATA[Reply to Windows Forwarded Event Source on Tue, 05 Nov 2019 10:20:57 GMT]]></title><description><![CDATA[<p dir="auto">I don't think you can change an event source after that event is received.<br />
As you indicated, you can create a new event and set the correct source for that new event though.<br />
To avoid your database doubling in size, you could run a regular cronjob/scheduled task to clean out the duplicates.</p>
<p dir="auto">Or you could use a cronjob/scheduled task to adjust the source directly inside the database at regular intervals. That wouldn't be live though.<br />
Or setup a trigger in the database to automatically perform that task in certain cases. Not sure about the performance impact on such a step though.</p>
<p dir="auto">Edit: Or simply use the inbuilt and smart way of doing it, which Victor mentioned below.  :-[</p>
]]></description><link>https://forum.netxms.org/post/26855</link><guid isPermaLink="true">https://forum.netxms.org/post/26855</guid><dc:creator><![CDATA[Tursiops]]></dc:creator><pubDate>Tue, 05 Nov 2019 10:20:57 GMT</pubDate></item></channel></rss>