Use software packages to install, update, or remove software on a set of target computers. Use software bundles to specify a sequenced list of software packages to deploy. Deploy also provides a gallery of common software packages in the Predefined Package Gallery.
The Predefined Package Gallery page lists predefined software package templates that you can import. Use the Predefined Package Gallery to import third-party software package templates to install, update, or remove software on a set of target computers.
Tanium does not repackage or redistribute third-party software installers. The Tanium software package templates provide you with the remote file paths to directly download the software installer from the third-party vendor. You must review any applicable third-party End User Licensing Agreement (EULA) before you import third-party software to the Tanium software package catalog. Tanium is not responsible for accepting, nor does it accept, any EULAs from third-party software vendors on your behalf.
For applicability checks and command-line operations, make sure that all endpoints have the required system environment variables defined. For more information, see Windows System environment variables.
- From the Deploy menu, go to Software and then click Create Software Package.
- In the Package Files section, click Add Package Files to add a local file
, remote file, or remote folder.
These are the files that are needed to install an application on a managed device. They include, but are not limited to, MSI or EXE installers, resource files or folders, package files, configuration files, custom scripts, custom registry files, or license keys.
You can select multiple files at once, but you cannot upload entire folder structures as a local file. To use an entire folder, first compress the folder contents into a compressed archive file (such as a ZIP file), then add the compressed file to the software package. For information about using Deploy to extract a file, see File/Folder actions.If you select a remote file or remote folder, ensure that the Tanium Module Server service account can access the remote location and has sufficient permissions.
- Windows Module Servers: Use a domain-joined account for seamless access to remote shares.
- Appliance Module Servers: Add an authentication user. For more information, see Tanium Appliance Deployment Guide: Add an authentication user for TDownloader.
- In the Package Details section, provide the general product information, select the OS platform, and click Choose Icon to upload an icon for self service deployments.
- If the package files include one or more Windows Installer packages (MSI file format), you can click Inspect MSI to Populate Fields to extract information from the .msi file and verify the pre-populated information. Using this feature does not overwrite any information that you previously entered manually.
- The account that is set for the Deploy service account must have access to execute PowerShell on the Tanium Module Server.
If the package files include one or more Windows Installer packages (MSI file format), you can click Inspect MSI to Populate Fields to extract information from the .msi file and verify the pre-populated information. Using this feature does not overwrite any information that you previously entered manually.
Specify an operating system platform. If the software package should only be run on certain versions of the platform, click Restrict Operating Systems in the System Requirements section.
- In the System Requirements section, provide the minimum system requirements for the software package to run on the endpoint.
Disk Space Required
Configure the minimum available system disk space required. For best results, specify at least three times the total size of the package files.
Configure the minimum physical RAM required.
Configure the allowed architectures for the software package based on the platform. On endpoints where the architecture does not match, the software package will show a status of Not Applicable.
(Windows) Select x86 for software that cannot be installed on 64-bit Windows systems. Select x64 for software that can be installed on 64-bit Windows systems. Select Select All for x86 software that can be installed on 64-bit Windows.
(macOS) Select x64 for software that should only be installed on Intel-based Mac endpoints. Select ARM64 for software that has only a native ARM64 binary. Select Select All for software that has a universal binary, does not install a binary, or can run using Rosetta.
ARM64 macOS software packages are not supported by Tanium Client 22.214.171.1249 and earlier, which runs using Rosetta 2 on Apple-silicon Mac endpoints. Deploy treats those endpoints the same as Intel-based Mac endpoints. To configure software packages for Apple-silicon Mac endpoints running Tanium Client 126.96.36.1999 and earlier, select the x64 architecture. To avoid targeting Mac endpoints with software packages that are intended only for a specific CPU architecture, use the CPU Architecture sensor
from Tanium Core Content 1.4.16 or laterin any deployment targets.
(Linux) Select x86, x64, or ARM64 based on the platform for which the software is compiled. Select any combination of the three options for software packages that do not install compiled code or that do so in a platform-agnostic fashion.
Restrict Operating Systems
Click Restrict Operating Systems and then select the supported operating systems on which to allow Deploy to install or update the software package. The software package will still be considered installed if the Install Verification criteria are met on non-restricted operating systems. Specific operating systems can be targeted for deployments and self service profiles without making a selection in the software package.
Specify an operating system only if the software package should never be installed or updated on other operating systems. If you need an operating system that is not available, you can add one in Deploy settings. For more information, see Create a custom operating system.
- In the Deploy Operations section, select which operations you want to enable: Install, Update, or Remove, and add conditional commands for any of the Deploy operations that you enabled for this package. For each operation, select the Require Source Files option if any of the files in the Package Files section are required to perform the operation. If you do not select this option, the package files are not downloaded. (Windows) For more information, see Variables for Windows applicability scans and command-line operations.
If you chose to inspect the MSI, some operations are already enabled and information is pre-populated. You can verify or update any of the pre-populated information.
Check for Running Processes
Specify a process name, for example, Chrome.exe, and select either Terminate process or Pause until process is no longer running. If you choose to pause the process, the wait time is five minutes.
Specify an install, update, or remove command to run and choose whether to run the command as the System or the Active User. If any part of the path in a command contains a space, use double quotation marks, even if you use variables.
Extract a compressed file, copy a file or folder, create a folder, delete a file or folder, or rename a file or folder. For more information, see File/Folder actions.
Tanium Client File Request
Specify an HTTP(S) address or a UNC file path and file name. Any URI that you enter must be allowed on the Tanium Server. For more information, see Tanium Platform User Guide: Managing allowed URLs.
To use any of these actions with a file attached to this software package, enter the file name in the source field.
To extract or copy a file or folder to the working directory used for running this software package, enter a period in the destination field. If the file or folder should go to a different location, specify the fully qualified path, such as "C:\Program Files" or /opt/Tanium.
Variables are not supported in File/Folder commands.
- In the Installation Requirements section, add a list of detection rules for prerequisite software. (Windows) For more information, see Variables for Windows applicability scans and command-line operations and WMI queries.
- (Optional) If the Update operation is selected, add a list of detection rules for previous versions. (Windows) For more information, see Variables for Windows applicability scans and command-line operations and WMI queries.
- In the Install Verification section, add a list of detection rules for installation verification. For more information, see Variables for Windows applicability scans and command-line operations and WMI queries.
- Click Create Package. You can also click Save and Finish Later to finish creating the package later.
When you create a Windows software package, you can use ||PROGRAMFILES32BIT||, ||PROGRAMFILES||, ||ACTIVEUSERPROFILE||, or ||ACTIVEUSERREGISTRY|| as variables for applicability scans and command-line operations. For the Requirements, Update Detection, and Install Verification sections, you can use these variables if you select the Registry Path, Registry Data, File Path or File Version filter fields.
|32-bit on 32-bit endpoint||||PROGRAMFILES32BIT||||
Path to Program Files folder
(example: C:\Program Files)
|32-bit on 64-bit endpoint||||PROGRAMFILES32BIT||||C:\Program Files (x86)|
|64-bit on 32-bit endpoint||||PROGRAMFILES||||C:\Program Files|
|64-bit on 64-bit endpoint||||PROGRAMFILES||||C:\Program Files|
Profile directory of the active authenticated user
Registry hive of the active authenticated user
Use double quotation marks (") if any part of the path in a command contains a space, even if you use variables.
You can use a Windows Management Instrumentation (WMI) query to query information from WMI classes for any of the detection rules within a software package. If you use a WMI query, you cannot query against the Win32_Product WMI class.
For more information, see [Microsoft Documentation]: Win32_Product class.
You can perform the following actions for files and folders.
Do not use quotation marks in the folder path or file name in File/Folder actions.
- Copy File/Folder: Specify the fully qualified path and file name. If the destination is a folder, Deploy copies the source to the destination folder; it does not replace an existing folder. For example, a command to copy firefox.app to /Applications/firefox.app with overwrite enabled produces the following results, depending on whether /Applications/firefox.app is an existing folder:
- If /Applications/firefox.app is not an existing folder, Deploy creates /Applications/firefox.app.
- If /Applications/firefox.app exists, Deploy creates /Applications/firefox.app/firefox.app.
To always replace /Applications/firefox.app, set the destination to /Applications instead of /Applications/firefox.app.
- Create Folder: Creates a folder. If you specify a parent folder path that does not exist, it is created. For example, c:\temp\myfiles creates c:\temp folder and myfiles subfolder.
- Delete File/Folder: Any subfolders of the folder that you specify are also deleted.
- Extract File/Folder: Supported file types for extracting a file are 7Z, TAR, ZIP, BZIP2, GZIP, XZ, and Z. You can specify the following options for extract commands.
- Specify whether to overwrite existing files. If there is an existing file, however, you must also select Continue in the On Failure or Error section; otherwise, the extract command fails and Deploy retries the software package operation.
- Specify a Command Timeout in minutes. The extract operation will time out after the number of minutes you specify. For best results, specify 1 minute for each 50 MB of file size. For example, if your file is 1 GB, specify a Command Timeout value of 20 minutes.
- In the Extract To section, specify an option. Root of Destination extracts the contents of the compressed file in the specified destination. Folder within Destination creates a folder in the specified destination with the same name as the compressed file, and then extracts the file to the newly created folder.
- As an example, to use the contents of an attached package file example.zip in a software package, specify example.zip as the Source and . as the Destination. Select Root of Destination and Overwrite Existing Files. Then, if example.zip contains a Setup.exe file that should be executed in this software package operation, add a Run Command step with Setup.exe at the start of the Run Command.
- Rename File/Folder: Specify the existing (source) and new (updated) fully qualified path and file names.
You can export a software package so that you can later import the package on a different server or recreate a deleted package.
- From the Deploy menu, go to Software.
- Click the name of your package and then click Export .
The ZIP file is available in your downloads folder.
You can import a previously exported software package on a different server or recreate a deleted package.
Tanium as a Service does not support importing a package that references a remote file. If a previously exported software package file contains a reference to a remote file, you cannot import that package.
- From the Deploy menu, go to Software and then click Import Package.
- Browse to the previously exported ZIP file and click Import.
- Click (Download File) for any required files.
Tanium as a Service does not support importing a package that references a remote file.
- Click Import or Import Duplicate if you are importing a duplicate package.
For a complete list of the software packages available in the Predefined Package Gallery, see Predefined Package Gallery.
- From the Deploy menu, go to Software and then click Predefined Package Gallery.
- Click Import for the package you want to import.
To import multiple packages simultaneously, select the packages that you want to import and click Import.
After you import a package and distribute the catalog, you can deploy, edit, delete, or export the package.
If you import the Oracle Java 8 package and want to remove previous versions of Java, you can add REMOVEOUTOFDATEJRES=1 to the end of the run command in the Update Command field of the software package.
After you create or edit a software package, the updated software package catalog must be distributed to the endpoints. When the endpoints receive the updated software package catalog, you can view the package applicability.
If you upgraded from Deploy 2.1.9 or earlier and want the software package catalog to be automatically distributed, you must enable the Auto-Distribute Catalog option in the Configuration Settings tab of the Deploy Settings . If you do not enable this option, you are prompted to distribute the software package catalog each time an update is detected, and must click Distribute Catalog.
If a software package that is being imported already exists in the software package catalog, you are presented with two options prior to importing again. If you want to replace the existing package, select Replace existing. If you want to import the package, but also keep the existing one, select Save as another software package. You must then update at least one of the fields to create a unique record in the software package catalog.
- From the Deploy menu, go to Software and then expand a package.
You can also view the software package applicability by additionally clicking your package name.
- For more details about a specific applicability state, click the link that corresponds to the number and percentage of endpoints in that applicability state.
- To view the applicability details for the endpoints, click Full Report.
For information about configuring applicability scans, see Applicability scans.
When determining software package applicability, Deploy checks the criteria specified in the software package in the following order, stopping at the first section with matching criteria.
System architecture on the endpoint: If the architecture does not match any of the architectures defined in System Requirements, Deploy marks the software package as Not Applicable and moves on to the next software package.
Install Verification criteria: If those criteria match, Deploy marks the software package as Installed and moves to the next software package.
Update Detection: If an Update operation exists, Deploy then checks the Update Detection criteria. If those criteria are met, Deploy checks System Requirements:
If System Requirements match, Deploy marks the software package as Update Eligible and moves to the next software package.
If System Requirements do not match, Deploy marks the software package as Update Ineligible and moves to the next software package.
Installation Requirements criteria: If Installation Requirements criteria do not match, Deploy marks the software package as Not Applicable and moves on to the next software package. If Installation Requirements criteria match, Deploy then checks System Requirements:
If System Requirements match, Deploy marks the package as Install Eligible and moves on to the next software package.
If System Requirements do not match, Deploy marks the package as Not Applicable and moves on to the next software package.
Keep the following clarifications in mind as you review software package applicability:
Installation Requirements affect only Install operations, not Update operations.
If you do not specify Installation Requirements, then the software package is marked Install Eligible if the endpoint meets System Requirements criteria for the software package.
Deploy evaluates Installation Requirements criteria, even if the software package does not contain an Install operation. As a result, Deploy marks a software package as Install Eligible even if it cannot be installed. To prevent this behavior, add a rule that cannot be true; for example, add the following Registry Path check to the Installation Requirements: HKLM\Software does not exist.
- From the Deploy menu, go to Software and then click Software Bundles.
- Click Create Software Bundle.
- In the Bundle Details section, specify the bundle name and optionally a description.
- In the Bundle Workflow section, select software options.
- Click Add to select the software packages to add to the bundle.
You can filter packages by typing the platform, vendor name, or package title.
- Select a specific version, or choose Latest Applicable to automatically select the latest available version for each endpoint.
- Select the operation: Install Or Update, Install, Update, or Remove.
- Select whether you want the bundle to exit or continue or if the package fails.
You can change the order of the packages by dragging the package.
- Click Add to select the software packages to add to the bundle.
- Click Create Bundle.
To edit a package or bundle, click the name of your package or bundle and then click Edit.
When a software package or bundle is edited and saved, the version number of the package or bundle is incremented. All existing deployments continue to use the version that is specified at the time of deployment until the updated software package catalog is distributed.
To copy a package or bundle, click the name of your package or bundle and then click Copy.
When a software package or bundle is copied, the name is automatically prepended with Copy - .
To delete a package or bundle, click the name of your package or bundle and then click Delete .
To delete multiple packages simultaneously, select the packages from the Software Packages page and then click Delete.
You can delete a software package or bundle only if it is not referenced in an active deployment.
Last updated: 5/19/2022 10:17 AM | Feedback