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 Initial Content (Version 7.1.2)
Thank you for choosing Tanium. This page documents changes between releases of Tanium Initial Content.
Tanium Initial Content 7.1.2.0102
- Tanium Initial Content AD 7.1.2.0034
- Tanium Initial Content FileSystem7.1.2.0034
- Tanium Initial Content Hardware 7.1.2.0034
- Tanium Initial Content MSSQL 7.1.2.0034
- Tanium Initial Content Network 7.1.2.0035
- Tanium Initial Content OS 7.1.2.0035
- Tanium Initial Content Registry 7.1.2.0034
- Tanium Initial Content Security 7.1.2.0034
- Tanium Initial Content Software 7.1.2.0037
- Tanium Initial Content Tags 7.1.2.0036
Release Date: September 5, 2017
The previous version can be found here: Release Notes Initial Content (Version 6.5.11)
Enhancements:
- Improved handling of international character sets for all non-Windows sensors.
- Complete support for UTF-8 characters on Non-Windows platforms requires deployment of Tanium Python for Endpoints
- Improved most Linux sensors' handling of Linux distribution differences
- Improved handling of Linux sensors when default language of distribution is non-English
- Improved handling of commands that may only be optional in minimal distribution installs, and therefore might not be available
- Upgraded version of Tanium Exec Wrapper to latest available
- 'Tanium Client Core Health' on Windows now reports if the PATH variable does not have standard and required Windows directories included
- Performance sensors use new algorithms to generate more accurate data results
- Continued improvement of handling international data in all sensors
- Improved use of common library code across all sensors and packages
- Moved some sensors from "Base" content set to "Reserved" content set
Bug Fixes:
- Resolved issue with several AIX sensor implementations that were using bash shell interpreters, which may not be available in a default AIX installation
- Resolved issue with 'Custom Tag Exists' sensor on non-Windows platforms where a non-exact search for a tag would return False if more than one tag matched the search parameters. The sensor now correctly returns 'True' if one or more tags match the search criteria
- Resolved issue with 'In Subnet' sensor on Windows where it would not return 'True' for an exact /32 CIDR match
- Resolved issue with 'In Subnet' sensor on non-Windows platforms where an incorrect 'False' would be returned for a valid CIDR expression
- Corrected 'Workgroup' sensor description, that it will only return a value if the machine is part of a Workgroup, and will return no value if the machine is in AD
- Resolved issue with 'Packet Loss' sensor returning misleading result if the packet loss for the machine was 0, or no packet loss detected
- Resolved issue with 'Monitor Details' returning empty result sets when the data should have been available
- Resolved issues with 'Tanium Client Subnet' across non-Windows platforms, making sensor results more reliable under multiple network configurations
- Resolved issue with 'Total Memory' incorrectly summing all installed memory
- Resolved issue with 'Folder Exists' on AIX returning incorrect results
- Resolved issue with 'Predicted Disk Failures' on Windows failing in some S.M.A.R.T. drive response scenarios
- Resolved issue with 'User Sessions' and 'Reset User Session' sensor / package pair not working correctly in Tanium 7.0 and higher
- Resolved issue with 'Tanium Action Lock Status' on Windows not verifying that the registry entry was a proper DWORD type
- Resolved issue with 'Network Link Speed" on Solaris using the wrong separator character
- Resolved issue with 'Registry Key Exists' on Windows returning an incorrect 'True' value in situations where WMI has been corrupted
- Resolved issue with 'File Exists' on Solaris 10 returning incorrect results
- Resolved issue with 'IPv6 Address' on Linux including the loopback adapter
Added Sensors or Sensor Implementations:
- OS Platform: This sensor was added as an optional targeting sensor to be used instead of using the 'Is {OS}' sensors. It returns the platform type of the endpoint.
- DNS Server: Added AIX implementation
- Windows OS Major Version: Added to allow targeting to all Windows OSes of a given generation
- Windows OS Release ID: Added to allow targeting to specific releases of Windows 10
- Virtual Platform: Added Linux implementation
- Network IP Gateway: Added all non-Windows implementations
- Tanium Client Neighborhood: Added AIX and Solaris implementations
Removed Sensors or Content:
- Non-Approved Established Connections: This sensor, with associated dashboards and saved questions, has been moved from Initial Content to IR solution because the non-approved configuration files are managed within the IR solution
- Network Drives Accessed: This sensor was removed because it only returned SYSTEM level access connections, and not connections within the individual user session context. A version of this sensor which does return this information within the user's context is available in User Session Tools content pack.
- Default Printer: This sensor was removed because it only showed if there was a system wide default printer, and did not display the default printer within the individual user session context.
- Installed HotFixes: The Windows implementation of this sensor was removed. Use Tanium Patch for identification of installed Windows hotfixes.
- User Profile Directory Details: The Windows implementation of this sensor no longer calculates the total size of the profile, as that calculation may take too much time for a sensor evaluation
Additional Information
Known Issues and Workarounds
- Because the behavior of 'Custom Tag Exists' has changed, saved questions and scheduled actions depending on 'Custom Tag Exists' will need to be recreated. Please consult your TAM for assistance in moving to the new sensor format.
- Because the archiving of Saved Questions within Initial Content has been disabled, users who wish to continue the archiving of these questions should re-enable archiving after import.
- With the addition of a default value from the Custom Tags sensor when there are no tags set, users can now target machines without tags directly. However, caution should be taken to make sure that this new result value does not bring any unintended machines into action targeting.
Additional Information
This release is a parallel release of combined content for 6.5, which can be found here: Release Notes Initial Content (Version 6.5.12)