IMPORTANT: This site is planned to be decommissioned in 2026. Visit the Tanium Resource Center for all Tanium release notes, user guides, and support information. To view release notes in the Resource Center, see Tanium Release Notes.
IMPORTANT: If you are using semi-annual releases for on premises, see the Release notes for 2024H1 semiannual release, Release notes for 2024H2 semiannual release, or Release notes for 2025H1 semiannual release on the Tanium Resource Center.
Effective October 15, 2024: On prem release notes on the Tanium Knowledge Base are frozen. For release notes related to 7.4 or 7.5 Server and Solutions, see the Monthly updates for Tanium Version 7.4 and 7.5 Server and Solutions on the Tanium Resource Center.
Release Notes (Version 6.5.314.4425)
Thank you for choosing Tanium. The following Release Notes document changes between releases of the Tanium Server.
The previous version can be found here: Release Notes (Version 6.5.314.4410)
Tanium Server Version 6.5.314.4425
Limited Availability Release Date: December 2016
Functionality Improvements
- Added ability to enforce max session count and keep alive max.
- Improved question loading time in console.
- String cleaning functionality is enabled by default. String caps are auto-configured based on the amount of memory in the Tanium Server. This functionality can be disabled by adding the following global setting - enable_string_cap = 0 (Server Setting, Numeric)
Bug Fixes
- Fixed issue with session count value being incorrectly tabulated in Active-Active setups.
- Fixed issue with deleting expired SOAP sessions from database.
- Fixed bug where network reset could cause server crash.
- Fixed bug where a long running handler could cause a server crash when being recycled.
Known Issues and Workarounds
- Module Server Installation—If you're installing the Tanium Server to the default location, your Module Server will also be placed in the default "C:\Program Files\Tanium\Tanium Module Server" location. To change this, uninstall the Module Server after you install your Tanium Server, and use the standalone Module Server installer (ask a Technical Account Manager).
- trusted.crt recreated on Module Server Installation—On the migration of the Module Server to the new version, the trusted.crt file currently in use will be recreated, and the original version deleted. If using a non-self-signed certificate, this may mean that the trusted.crt will need to be recreated manually. To avoid this, save a backup copy of the trusted.crt to another location before beginning the upgrade. After the upgrade, the trusted.crt file can be replaced in the Module Server root directory. For additional information regarding certificate creation, visit the Create Trusted Certificate Chain article.
- Input escaping for Sensor-sourced Packages—Sensor-sourced Packages should now expect that their inputs are escaped. Tanium-developed content has been updated. Please contact your Technical Account Manager for content updates or questions pertaining to any custom Sensor-sourced Packages that need to be updated.
- File Distribution Failure—The Tanium Client installed on the Tanium Server can encounter an issue in which the Tanium Client could disrupt file distribution if the agent is part of a local ring or “neighborhood.”
- To prevent this issue, configure the Tanium Client installed on the server using the Isolated Subnets feature so that the agent communicates with only the Tanium Server itself. Within the Notepad editor, create a new file and enter the IP Address of the Tanium Server in the CIDR format, for example: 192.168.100.102/32. Save the file as IsolatedSubnets.txt to the Tanium Server's installation folder. Restart the Tanium Server service, Tanium Server (TaniumReceiver.exe).
- Estimated Total field dropping to 0—There is a known issue where GetResultsInfo API calls will have an incorrect value of "0" for the estimated total field. If the estimated total field is needed, the current workaround is to programmatically ignore the report when "0" is seen and request another report.