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 Tanium Server (Version 7.6.2.1228)
Thank you for choosing Tanium. The following Release Notes document changes between releases of the Tanium Server.
This platform release includes the release of both a Windows and Linux Tanium Server.
The previous version can be found here: Release Notes Tanium Server (Version 7.6.2.1222)
Tanium Server for Windows and Linux v7.6.2.1228
- Tanium Cloud availability date: N/A.
- On-premises availability date: June 18, 2024.
Special Notes
- The Tanium Server now uses Console (Version 3.7.13.0000).
- Tanium discourages new installations of this software version on Windows 2012 and 2012-R2 given its End-Of-Life on
2023-10-10.
Security Updates
- N/A.
Improvements
- Ensures that all Pyhon v3.8 binaries delivered to the Tanium Client are signed.
Bug Fixes
- Fixes an incorrect user ownership and permission settings on the
fips.logfile deployed by the Tanium Module Server installer which would result in the error "Failed to open file "/opt/Tanium/TaniumModuleServer/fips.log": EACCES: Permission denied" when upgrading a server running in FIPS-enabled mode.
Known Issues and Workarounds
- The Tanium Server has a problem in the unlikely event that different package files that happen to share identical chunks, leaving clients unable to download one or more of these files.
Workaround: A definitive fix is being prepared to be made available in an upcoming SAR update, and in the meantime it has been established that a restart of the Tanium Servers in a deployment will clear up this condition.