Getting Data In

After updating our universal forwarders from Splunk 6.1.2 to 6.2.8, why is the Account_Name field not populated for Windows Security logs?

saulverde
Path Finder

After updating our universal forwarders from 6.1.2 to 6.2.8 Windows Security logs are coming in without the Account_Name field populated. The SID is populated but that isn't nearly as useful as the username.

0 Karma

javiergn
Super Champion

Have you tried forcing your inputs.conf stanza to resolve the ad names?
Maybe another app is now disabling that.
Try adding the following:

evt_resolve_ad_obj = 1
0 Karma

saulverde
Path Finder

We are currently evaluating the impact of adding that stanza to the inputs.conf. I'll update when we have it implemented.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...