Splunk® App for Microsoft Exchange (EOL)

Deploy and Use the Splunk App for Microsoft Exchange

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

This topic contains information on new features, known issues, and updates as we version the Splunk App and Technology Add-ons for Microsoft Exchange.

The latest version of the Splunk App for Microsoft Exchange was released on Tuesday, December 15, 2015.

What's new

Here's what's new in the latest version of the Splunk App for Microsoft Exchange:

Publication date Defect number Description
2015-11-13 N/A Bug fixes.
2015-11-13 TAG-3432 The app now supports search head clusters.

Current known issues

The Splunk App for Microsoft Exchange has the following known issues:

Publication date Defect number Description
2015-11-13 TAG-8511 When you access the app using version 8 of the Safari browser, the "Non-reporting servers" panel in the Host Overview dashboard displays "Invalid number." To work around the problem, use another Splunk-supported browser.
2015-11-13 TAG-8925
TAG-9474
The Exchange Server reports pages in the app display significantly different results when you upgrade from Splunk Enterprise version 6.1 to 6.2. This is due to a problem in how version 6.2 searches summary indexes.
2015-11-13 TAG-9607 The "Windows Updates and Host Downtime" dashboard incorrectly marks some hosts as always down, despite the fact that they are up.
2015-11-13 TAG-9621 A problem with one of the saved searches for performance monitor counters can cause the Performance Counters lookup file to become exceptionally large and possibly crash Splunk Enterprise on the instance that has the lookup file.
2015-11-13 TAG-9629 The "Administrator Audit" drop-down menu does not display the complete list of administrators.
2015-11-13 TAG-9910 In some cases where the fields list has been modified, the "User Behavior overview" dashboard can return erroneous results.
2015-11-13 TAG-9911 The TA-Exchange-2010-HubTransport add-on does not contain the correct counter definitions for Exchange Server 2010.
2015-11-13 TAG-10149 Some dashboards in the app can take a long time (up to 15 minutes) to populate depending on the amount of data that has been collected.

Change log (what's been fixed)

Publication date Defect number Description
2015-5-19 TAG-9344 The "Mailbox Database Overview" page now shows the correct free space of all mailbox databases, instead of only databases that have been mounted on lettered drives..
2015-11-13 TAG-9354 The "Analyze a host" dashboard now displays all roles for Exchange hosts that hold more than one Exchange Server role.
2015-11-13 TAG-9413 The read-audit-logs.ps1 script no longer fails to complete when the Error field is empty.
2015-11-13 TAG-9525 On non-English systems, the app no longer fails to send events after an upgrade to version 3.1.3.
2015-11-13 TAG-9527 The app I/O latency search now accounts for the Exchange Server 2013 data format.
2015-11-13 TAG-9560 The get-inboxrules.ps1 script now returns all available mailboxes in the Exchange Database Availability Group (DAG), rather than just the first 1000.
2015-11-13 TAG-9957 The RPC and OWA counts on the Host Performance page now display properly.
2015-11-13 TAG-10150 The "Host Overview" dashboard now shows accurate values in the "Exchange App version" drop-down menu.
Last modified on 27 February, 2016
Best practices guide   Known Issue: Disable Transport Handling and Mailbox components in Service Analyzer for Exchange Server 2007 and Server 2010 environments

This documentation applies to the following versions of Splunk® App for Microsoft Exchange (EOL): 3.2.0


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters