Release Notes Deploy (Version 2.26)

Tanium Deploy 2.26.1218

Release Date: 04 June 2024

Improvements

• Optimized backend storage of deployment notification icons
• Updated Deploy - Coverage Status and Deploy - Coverage Status Details sensors to check for Software Management Tool installation.

Resolved Issues

• Fixed an issue with API route concurrency
• Fixed an issue with unnecessary CPU and disk writes caused by idle deployments

Known Issues

• Software package deployments with a reboot and no post-notification will not re-run if the software package operation becomes applicable again. For best results, always include a post-notification on any deployment that includes a reboot.
• Changes to software bundles will not affect existing deployments of those bundles. Any existing bundle deployments must be stopped and reissued to deliver the updated bundle. Edits to software packages and new Latest Applicable packages do affect existing bundle deployments.
• In all versions of Deploy, configuring a Windows software package with a restricted operating system that uses a workstation type (such as Windows 10 & 11 - All Versions) will cause that software package to be Not Applicable on Windows Enterprise for Virtual Desktops operating systems used for Microsoft Azure virtual desktops.
• Deploying multi-platform bundles is not supported. If you deploy a bundle that has packages for different operating systems (for example, Windows and macOS packages in one bundle), the deployment does not run or report status.

Tanium Deploy 2.26.196

Release Date: 08 May 2024

Improvements

• Stability improvements

Known Issues

• Software package deployments with a reboot and no post-notification will not re-run if the software package operation becomes applicable again. For best results, always include a post-notification on any deployment that includes a reboot.
• Changes to software bundles will not affect existing deployments of those bundles. Any existing bundle deployments must be stopped and reissued to deliver the updated bundle. Edits to software packages and new Latest Applicable packages do affect existing bundle deployments.
• In all versions of Deploy, configuring a Windows software package with a restricted operating system that uses a workstation type (such as Windows 10 & 11 - All Versions) will cause that software package to be Not Applicable on Windows Enterprise for Virtual Desktops operating systems used for Microsoft Azure virtual desktops.
• Deploying multi-platform bundles is not supported. If you deploy a bundle that has packages for different operating systems (for example, Windows and macOS packages in one bundle), the deployment does not run or report status

Tanium Deploy 2.26.193

Release Date: 26 March 2024

Improvements

• Many improvements to the Deployments pages, including a new look and feel for editing and creating deployments.
• Audit logs for the creation, modification and deletion of Deploy objects can now be downloaded in the Deploy workbench and Deploy service API.
• Improves auditing capabilities of Deploy by surfacing the Tanium user who last modified a given deployment, deployment template, or maintenance window.
• The Deployments page now displays the user that stopped a deployment and when the deployment was stopped for stopped deployments.
• Adds the ability to filter by the Last Modified By Tanium username in the workbench.
• Deploy home page charts are now scoped to the Deploy action group.
• Added time zone for Australia/Adelaide (GMT+1030).
• Added last modified audit information to Deployment, Deployment Templates and Maintenance Window confirmation pages.
• New user notification appearance option to show title bar and provide minimize option on notification popup. This functionality is dependent on Toolset Version 2.0.30 or later.

Resolved Issues

• Fixed an issue where the Created By username that appeared in the workbench was actually the Last Modified By username.
• Fixed an issue where the System Account overwrote the Tanium user history of deployments and deployment templates on update.
• Fixed an issue that could cause the Tanium Deploy solution to not complete an upgrade.
• Fixed an issue that could cause Software Management tools to not complete an uninstallation.
• Fixed an issue that could cause deployments to fail when the endpoint cannot reach the Tanium Server.
• Fixed an issue that could cause detection of the highest version of a product to be incorrect.
• Fixed an issue that could cause deployment synchronization jobs to fail after adding a target to the deployment.
• Fixed an issue that could cause the deployment workbench to crash because of bad deployment links in the Software Package page.
• Fixed an issue that could cause the support bundle collection to erroneously be available.
• Fixed an issue that prevented new deployments from being created based on a pre-notification template with post-notifications enabled.
• Fixed an issue that could cause the Deploy package file upload progress display to be incorrect.
• Fixed an issue where the content set was required to be specified on new deployments. The Deploy content set is used, if another content set is not specified.
• Fixed an issue that could cause package file upload failures to be incorrectly handled.
• Fixed an issue that caused new deployment templates to have an incorrect display setting for end-user notifications.
• Fixed an issue that could cause the Deploy service to become unresponsive when bulk-creating deployments through API automation.
• Fixed an issue that could cause the Deploy service to hang or perform poorly while removing ended deployments from ECF.
• The Details By Endpoint deployment reporting button now correctly displays applicability results limited to endpoints targeted by the deployment.
• The Is Gallery Package column in the Deploy - Software Packages sensor is now correctly defined as a String.

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.

Known Issues

• Software package deployments with a reboot and no post-notification will not re-run if the software package operation becomes applicable again. For best results, always include a post-notification on any deployment that includes a reboot.
• Changes to software bundles will not affect existing deployments of those bundles. Any existing bundle deployments must be stopped and reissued to deliver the updated bundle. Edits to software packages and new Latest Applicable packages do affect existing bundle deployments.
• In all versions of Deploy, configuring a Windows software package with a restricted operating system that uses a workstation type (such as Windows 10 & 11 - All Versions) will cause that software package to be Not Applicable on Windows Enterprise for Virtual Desktops operating systems used for Microsoft Azure virtual desktops.
• Deploying multi-platform bundles is not supported. If you deploy a bundle that has packages for different operating systems (for example, Windows and macOS packages in one bundle), the deployment does not run or report status