Getting Data In

Universal forwarder is not collecting events on Forwarded Folder of windows server

AKG
Path Finder

Hi All I am new to Splunk and having some issue...

we have a windows 2008r2 server setup as an event collector for windows servers. Event logs from windows server is being forwarded to this server and goes on to "Forwarded Events" folder.

Now I installed universal forwarder on this server with only "Forwarded Events Log" selected. When i go to splunk server, I can't see any events coming.

if I install with other option selected(e.g. Application Log), I can see application log of that server appearing on splunk server.

I was wondering if i am missing something and will appreciate if some one can guide me.

Note:- we have decided not to install splunk agents in every server and not to use wmi as the number of windows we have is lot(in hundreds).

Thank you in Advance.

1 Solution

rovechkin_splun
Splunk Employee
Splunk Employee

the is a slight bug in default configuration. The issue is that "Forwarded Events" have a space between them, while Windows ForwardedEvents event log doesn't. The workaround is to find all occurrences of "Forwarded Events" in *.conf stanzas and remove space, e.g.

Splunk\etc>find /s "Forwarded Events" *.conf

inputs.conf: [WinEventLog:Forwarded Events]

replace with [WinEventLog:ForwardedEvents]

reboot Splunk.

View solution in original post

kmjackson788
Engager

That fixes it.

%SystemRoot%\System32\Winevt\Logs\ForwardedEvents.evtx

The space [WinEventLog:Forwarded Events] does not work. Hopefully they fixed the documentation. ( I sent a documentation fix)

http://docs.splunk.com/Documentation/Splunk/5.0.1/admin/Inputsconf

I dont have enough credit to upvote the above answer.

kmjackson788
Engager

They fixed the docs on inputs.conf. @rovechikin Should of submitted a change on the docs inputs.conf page to save people the frustration.

0 Karma

rovechkin_splun
Splunk Employee
Splunk Employee

the is a slight bug in default configuration. The issue is that "Forwarded Events" have a space between them, while Windows ForwardedEvents event log doesn't. The workaround is to find all occurrences of "Forwarded Events" in *.conf stanzas and remove space, e.g.

Splunk\etc>find /s "Forwarded Events" *.conf

inputs.conf: [WinEventLog:Forwarded Events]

replace with [WinEventLog:ForwardedEvents]

reboot Splunk.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...