Release Notes Deploy (Version 2.21)

Tanium Deploy 2.21.150

Release Date: 25 July 2023

Significantly improved the performance of the Deploy service, content and workbench in environments with many packages.
Tanium Deploy now supports Tanium Core Platform 7.6.1.
The End-User Self Service endpoint tool is no longer a required dependency for the Deploy endpoint tools.
Improved logging and software package applicability reasons for File Path, Version, Size, and Hash applicability rules.
Multi-package deletion now runs significantly faster.
The Deploy service now auto-restarts when a service down event is detected.
Improved log verbosity for Deploy endpoint tool installation failures.
The Modified On column is no longer used to indicate if a software package is Tanium Managed. A Tanium Managed column has been added to the Software Packages page.
Tanium Reporting Service 1.16.58 is now a Deploy dependency.
When the Deploy service fails to cache a remote package file, the Deploy workbench presents a message to the Deploy operator to use a local file instead.
Maintenance windows and self service profiles can now be targeted by filter question.
Removed unnecessary WMIC calls.
The Deploy content now recovers when the software management database is malformed.
Added Red Hat Enterprise Linux 9 and derivatives to supported operating systems.
Package gallery homepage charts now show links to the package details.
Log verbosity is now reduced during software package scanning to prevent excessive log rolling.
Upgraded various third-party libraries to new versions.

Fixed an issue that could cause progress bars in the Deploy workbench to display data out of order.
Fixed an issue that caused Deploy applicability data to become incorrect after changing the Deploy action group.
Fixed an issue that could cause post-deployment RPM scans to fail due to RPM database lock errors.
Fixed an issue that prevented the Deploy operator from being able to change the default deployment template in the Deploy workbench.
Fixed an issue that caused the wrong software package applicability result if a File Size rule path found a directory.
Fixed an issue that could cause deployments to stop after pre-notification or mid-software package if the maintenance window had closed.
Fixed an issue that could cause the Deploy service to unnecessarily sync all software packages when running distribute catalog.
Fixed an issue that could cause jobs to temporarily fail shortly after the Deploy service started.
Fixed an issue that could cause user file uploads to fail to correctly update the software package, leading to invalid package definitions.
Fixed an issue that caused the Created On or Modified On filter drop-down to be empty on the Self Service Profiles page.
Fixed an issue that could cause a software package to incorrectly show as not in use when included in a self service profile.
Fixed an issue that could cause bundle deployments to fail with the error “'NoneType' object has no attribute 'get'”.

Software package deployments with a reboot and no post-notification will not rerun 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 a mix of packages for different operating systems (for example mixing Windows and MacOS packages in a bundle) the deployment will neither run or report status.