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 Asset (Version 1.5)
Tanium Asset 1.5.4.0012
Release Date: December 18, 2018
Bug Fixes
- Fixed data load issue that could cause duplicate computers in the Asset database.
- Fixed Internet Explorer 11 issues in the Asset workbench.
- Fixed ServiceNow export to improve performance for exporting "Software Instances".
- Fixed issue where a report with a duplicate attribute would cause all reports to be unavailable.
Tanium Asset 1.5.3.0010
Release Date: December 4, 2018
Bug Fixes
- Fixed issue that prevented a view from being saved when it contained a colon in the filter definition.
- Fixed issue with Asset API which could cause the service to become unavailable when using large batch sizes and when returning large JSON results with a single request; additional monitoring has been included to log potential throughput problems.
- Fixed issue with sensors which return numeric values in excess of the maximum integer size; may cause load process to fail.
- Fixed issue with Asset UUID sensors for both Solaris and AIX.
- Fixed issue with Asset Computer Serial Number sensor for AWS linux; it will return the AWS serial number when available.
Tanium Asset 1.5.2.0009
Release Date: November 6, 2018
Bug Fixes
- Fixed intermittent TanOS upgrade issues caused by service files not being deleted when upgrading Asset.
- Fixed the Asset CPU sensor for Linux; the sensor now returns the average CPU speed when there are multiple CPU's.
- Fixed the Asset Network Adapter sensor for Linux; the sensor will only return a single IP address per NIC.
- Fixed issue with the Flexera destination database creation script; the script now uses truncate to clear the tables before load.
- Fixed issue with load where computers may be duplicated with empty computer name, serial number, and computer id.
- Fixed issue with Asset Logical Disk sensor; it will no longer include network mounted drives.
Known Issues and Workarounds
- The modified sensors will take between 10 minutes and 24 hours to fully take effect, due to sensor caching.
Tanium Asset 1.5.1.0011
Release Date: October 30, 2018
Feature Improvements
Support for ServiceNow Software Asset Management Pro (SAM Pro) has been added to the ServiceNow destination. When adding a new destination Asset will check your ServiceNow destination for the existing of SAM Pro and create the appropriate mappings.
Bug Fixes
- Fixed default connections batch size with creation of Flexera destination; the default and recommended batch size is 100.
- Fixed issue with filter by text option; it now merges the report and text filters vs override the report filters.
- Fixed issue with report column order; reports will now reflect the order specified in report editor.
- Fixed issue with "All Users" report drilldown on user; previously the user would receive a "Failed to get the users" error message.
Tanium Asset 1.5.0.0168
Release Date: October 23, 2018
Feature Improvements
- Asset Views:
- Filters have been improved; provided for limiting computers and related items included in the view.
- Checking the "Must have" option for reference attributes will limit computers that contain reference items.
- System views, Asset service created views are created by Asset and may not be edited.
- Views may be copied from existing system and custom views.
- ServiceNow Destination:
- Exported computers and related items are specified through selection of an Asset View.
- The Flexera Destination:
- Exported computers and related items are specified through select of an Asset View.
- Data Retention Settings allow purging of old or stale computer data.
- Enhanced database maintenance tasks and configuration aim to limit growth of the Asset database and ensure optimal performance.
- Asset now supports Amazon Linux.
Bug Fixes
- Fixed issue with Flexera destination where unique constraints on SQL Server tables could result in the connection run failure. The schema has been updated and the shipped database creation script should be run to replace the SQL Server database.
- Fixed issue with a user details drill down on reports. The link is now only available when the asset ID and username field are present in a report.
- Fixed issue with ambiguous error message when editing a report where the user does not have permission to edit.
- Fixed issue with ServiceNow destination; when exporting a batch of computers where more than one computer has the same name the batch would be skipped. Now the second computer will be removed from the batch and will not be synched to ServiceNow.
- Fixed issue with Report export feature where user would receive a "Failed to export the report" message. The report should now export correctly.
- Fixed issue with external database source, previously comparison of values for matching records was case sensitive; now it is case insensitive.
Known Issues and Workarounds
- The report "Text Filter" may result in any existing "Filters" being ignored. To work around is to add the text filter as a normal filter.
- Exporting a report with a significant number of rows may timeout; silently fail to export the report. To work around this issue use Connect to export large reports.
- Minor UI issues may exist, e.g. missing icons, when using Internet Explorer. For a workaround please contact your TAM.
- The user drill down for the All Users report may fail in some instances. There is currently no workaround for this issue and it will be included in the next maintenance release.
- When creating a new Flexera destination, the SQL Server and Exchange Connections created in connect must be manually edited / saved before running the destinations.
- Fixed with v1.5.1 - When creating a new Flexera Destination, the Connect connections are created with a batch size of 5,000; this batch size is too large and may put unnecessary load on connect. Please update newly created connections to use a batch size of 100.
Security Update
This release includes security updates. Details of the issue, including affected versions, and mitigation information, can be obtained within Tanium's Support Portal, or by contacting your TAM.
Supported Tanium Platforms
Tanium Server 7.0, 7.1, 7.2, 7.3