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 Console (Version 3.0.76.0000)

From Tanium Knowledge Base
Jump to navigation Jump to search

Thank you for choosing Tanium. This document is intended to document changes between releases of Tanium Console

Tanium Console 3.0.76.0000

General Availability Release Date: March 15, 2022

Requirements

The following Product Version or greater are required for Console 3.0.76.

  • Asset 1.17.155
  • Client Management 1.7.191
  • Comply 2.10.900
  • Connect 5.2.6
  • Deploy 2.8.174
  • Discover 4.4.126
  • End User Notifications 1.8.38
  • Enforce 1.8.197
  • Health Check 1.12.18
  • Integrity Monitor 2.9.542
  • Interact 2.8.105
  • Map 3.5.32
  • Patch 3.1.66
  • Performance 1.10.57
  • Platform 7.5.2.3505
  • Reputation 6.1.32
  • Reveal 1.4.0
  • Threat Response 3.4.357
  • Trends 3.7.303

These solutions should be upgraded to the required minimum version or removed prior to upgrade to Console 3.0. If the required minimum version is not present after the platform upgrade an error banner will be displayed for all users indicating which unsupported solutions are present. Users with access to Tanium Solutions will be directed to the Solutions page to either Upgrade or Remove the impacted solutions.

The Protect and Network Quarantine Solutions (NQS) are not supported by Console 3.0. These solutions no longer appear in the manifest or in the Tanium Solutions page. If either Protect or NQS are present after upgrade to Console 3.0 they can be removed via an uninstall link in the error banner on the Tanium Solutions page.

Important Notes

  • The language select option in user preferences was removed pending the completion of a full translation of the Console.
  • RBAC Deny Permission restrictions are limited to Administration and Platform Content Permissions. Deny restrictions can not be applied to Module Permissions.

Resolved Issues

  • Fixed an issue where content sets could not be added to Endpoint Configuration permissions.
  • Fixed an issue where the deploy action page could become unresponsive if a user had write action but not read sensor on a content set.
  • Fixed an issue where permissions provided by User Groups and User Group membership were not always displayed when viewing a user.
  • Fixed an issue when using multiple browser tabs where an idle tab reaching the console idle timeout would sign out all open tabs even if they were currently in use.
  • Fixed an issue where permissions assigned to a user by user group might not be visible when viewing the user’s permissions.
  • Fixed an issue for new installations where the user initialing the recommended solution import and configuration could be prematurely logged out resulting in a partially configured system.

Known Issues

  • Platform Services 1.3.339 will erroneously show as out of sync in the solutions page.
  • Cloned packages do not retain the verification query from the original package.
  • The associated actions are not displayed when editing an action group.
  • It isn’t possible to remove a Verification Query from a package.
  • Sensor editor is not highlighting script syntax.
  • Sensor preview is not returning expected results when editing or creating a sensor.
  • Moving Filtered Items in Content Set Moves ALL Items of Selected Type in Content Set.
  • Deploying Action from Question Results in Error: Status Code: 431 Request Header Fields Too Large. As a workaround, set these two Local Settings. This will increase the limit and allow customers with large numbers of computer groups to deploy actions. These can be created or updated on the "Platform Settings Page":
HTTP2MaxHeaderFieldSize = 12000  
HTTP2MaxHeadersSize = 16384 

Additional Information

This version of Console can be installed with Release_Notes_(Version_7.5.2.3552)

Product Documentation and Resources