troubleshooting Question

Splunk and Exchange Server 2013 log gathering

Avatar of Tim Nelson
Tim Nelson asked on
ExchangeSecurityPowershellNetwork Security
4 Comments1 Solution291 ViewsLast Modified:
I've got a question here related to Splunk logging of Exchange Server data that I hope someone can help with. We've got several on-prem Exchange servers in a DAG that are running 2013, and some in our parent company that are on an earlier version - 2010 to be exact. Before Exchange 2013, some other roles and features were available such as CAS server and hub transport, but many of these features have been folded or changed. As a result, the Splunk monitoring utility that my company uses only works properly on our Exchange 2010 servers in our parent company's office.

I know nothing about Splunk, but apparently its looking for powershell scripts to run, but these have been moved or renamed. Corporate Security told me:  "It supports collection of data from Exchange Server 2007 and Exchange Server 2010. Exchange Server 2013 does not have this role, as it has been integrated into the Client Access and Mailbox Server roles.” Because of this fields seem to be “off”, more or less the same data is there but under new names / sourcetype. (New sourcetype=MSExchange:2013:MessageTracking).

The scripts it is looking for exist in Exchange 2010 but cannot be found by Splunk in 2013; does anyone have any insight how how to make Splunk work with Exchange 2013?

[script://.\bin\exchangepowershell.cmd v15 get-mailboxstats_2010_2013.ps1]
source=Powershell
sourcetype=MSExchange:2013:Mailbox-Usage

[script://.\bin\exchangepowershell.cmd v15 get-folderstats_2013.ps1]
source=Powershell
sourcetype=MSExchange:2013:Folder-Usage

[script://.\bin\exchangepowershell.cmd v15 get-folderstats_2013.ps1]
source=Powershell
sourcetype=MSExchange:2013:Topology

[script://.\bin\exchangepowershell.cmd v15 get-databasestats_2013.ps1]
source=Powershell
sourcetype=MSExchange:2013:Database-Stats

[script://.\bin\exchangepowershell.cmd get-publicfolderstats.ps1]
source=Powershell
sourcetype=MSExchange:2013:PublicFolder-Stats

[script://.\bin\exchangepowershell.cmd v15 read-audit-logs_2010_2013.ps1]
source=Powershell
sourcetype=MSExchange:2013:AdminAudit

[script://.\bin\exchangepowershell.cmd v15 read-mailbox-audit-logs_2010_2013.ps1]
source=Powershell
sourcetype=MSExchange:2013:MailboxAudit

[script://.\bin\exchangepowershell.cmd v15 get-inboxrules_2010_2013.ps1]
source=Powershell
sourcetype=MSExchange:2013:InboxRules

[script://.\bin\exchangepowershell.cmd v15 get-distlists_2010_2013.ps1]
source=Powershell
sourcetype=MSExchange:2013:DistributionLists
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 4 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros