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 Impact (Version 2.1)

From Tanium Knowledge Base
Jump to navigation Jump to search

Tanium Impact 2.1.65

Release Date: 5 December 2023

Fixes

  • Gave Impact service account read sensor to all content sets.

Tanium Impact 2.1.57

Release Date: 15 August 2023

Fixes

  • Fixed the Impact Tools version.
  • Fixed scheduled tasks the could run again instead of at the correct interval.
  • Fixed the hop number displayed on the asset details page.
  • Fixed configuration of Trends reports on new installations.
  • Fixed logging errors when configuring Trends if the sources are disabled.

Tanium Impact 2.1.48

Release Date: 18 July 2023

Fixes

  • Fixed changing tabs on the asset details page.
  • Fixed title of Hop column on asset details tables.
  • Fixed asset search bar so the icon is not always loading.

Known Issues

  • Impact Tools version is incorrectly set to 1.5.0.

Tanium Impact 2.1.21

Release Date: 18 April 2023

Fixes

  • Fixed an impact-service-invoker error preventing new installations.
  • Fixed an installation error that can occur with the Connect plugins on Windows systems.
  • Fixed versioning information: The Impact version displayed will now show the service and workbench versions separately.
  • Fixed an issue that could cause impossible sync schedule cron expressions to stop the service. Moving forward, bad sync schedule cron expressions will just stop the sync schedule and not the service.