Release Notes Trace (Version 1.2.1)
Thank you for choosing Tanium. This document is intended to document changes between releases of Tanium Trace.
Tanium Trace 1.2.1.36
Release Date: July 14, 2016
Enhancements
- Added Event ID field to Security tab searching.
Bug Fixes
- Fixed issue that could cause query processes to stack up when executing enterprise wide questions.
- Fixed issue where the wrong command line and hash were sometimes being recorded for a process.
- Fixed issue where network filters where not available when creating a new group configuration.
- Fixed issue where the endpoint database size monitor scheduled action was not added when upgrading Trace.
- Fixed issue where sometimes the Trace service would not start after being installed.
- Fixed issue where upgrade migrations were causing an error if Initialize Endpoints had not been already done.
- Fixed issue where the drop down date filter was no long present
- Fixed issue where the recorder was deleting network/file/registry events on restart.
- Fixed issues where certain timestamps where being returned incorrectly by the endpoint database schema.
- Fixed issue where the Distribute Tanium Trace Tools package was not installing the default filters on the endpoint.
- Fixed issue where the Trace windows service was not displaying the correct name.
- Fixed issue where the Trace windows service was not using a Tanium signed executable.
- Fixed issue where the Trace Swagger API document was invalid.
- Upgraded prerequisites to address potential security vulnerabilities.
Additional Information
This release includes a new version of the Trace endpoint recorder which fixes a potential data loss issue on Tanium Client restart. In order to avoid data loss, it is necessary that this new recorder version be pushed to endpoints as soon as possible after upgrading Trace. To do this, simply go to the Trace workbench and press the Initialize Endpoints button or go to the console and deploy the Distribute Tanium Trace Tools package to the Trace Setup action group after upgrading Trace. To verify the new recorder has been deployed, use the Trace Status sensor to check the recorder version which should be 1.0.15.42.
Known Issues and Workarounds
- None