On October 22 2021, the Splunk App for Microsoft Exchange will reach its end of life. After this date, Splunk will no longer maintain or develop this product. The functionality in this app is migrating to a content pack in Data Integrations. Learn about the Content Pack for Microsoft Exchange.
This documentation does not apply to the most recent version of Splunk® App for Microsoft Exchange (EOL).
For documentation on the most recent version, go to the latest release.
Release Notes for the Splunk Add-ons for Microsoft Exchange
The latest version of the Splunk Add-ons for Microsoft Exchange was released on January 17, 2017.
Known issues
Version 3.4.1 of Splunk Add-ons for Microsoft Exchange has the following known issues:
| Report Date | Issue Number | Description |
|---|---|---|
| 2016-11-23 | EXC-2042 | get-databasestats_2013.ps1 reports a format error. |
| 2016-12-13 | EXC-2049 | MailboxResolvedOwnerName is wrongly exctracted/decoded if the name contains special characters. |
| 2016-12-30 | EXC-2052 | read-audit-logs_2010_2013.ps1 failure. The search command search-adminauditlog used in read-audit-logs_2010_2013, does not work in PowerShell for the 2016 Exchange Server product. The MSExchange:2013:AdminAudit sourcetype will not display in Splunk platform searches.
|
Fixed issues
| Publication Date | Defect Number | Description |
|---|---|---|
| 2017-01-17 | EXC-756 | TA-Exchange-2010-HubTransport is not fully CIM compliant. |
| 2017-01-17 | EXC-2016 | TA-Exchange-Mailbox - Method invocation failure. |
| 2017-01-17 | EXC-2024 | Audit log collection failures. |
| 2017-01-17 | EXC-2030 | Manually running get-inboxrules_2010_2013.ps1 spits out an error. |
Last modified on 06 February, 2017
| About the Splunk Add-ons for Microsoft Exchange | Overview of TA-Exchange-ClientAccess |
This documentation applies to the following versions of Splunk® App for Microsoft Exchange (EOL): 3.4.1
Download manual
Feedback submitted, thanks!