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.
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, click Software and then click New Software Package.
You can also click New Software Package from the Software Packages tab of the Software section in the Deploy Home page.
- In the Package Files section, click Add to add a local file
, remote file, or remote folder.
These are the files that are needed to silently 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.
If you select a remote file or remote folder, ensure that the account that runs the Tanium Deploy service has access to the remote location. By default, the Tanium Deploy service runs in the local system context. Hidden or administrative UNC shares are not supported within Tanium Deploy.
- In the General Information section, provide the general information, click Upload Icon to upload an icon, and select the OS platform.
- If the package files include one or more Windows Installer packages (MSI file format), you can click Inspect to extract the general information from the .msi file and verify the pre-populated information. Clicking Inspect 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 to extract the general information from the .msi file and verify the pre-populated information. Clicking Inspect does not overwrite any information that you previously entered manually.
- In the Deploy Operations section, select Deploy operations: Install, Update, or Remove.
- In the System Requirements section, provide the minimum system requirements for the package to run on the endpoint.
- In the 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 Deploy Operation section, add conditional commands for any of the Deploy operations that you enabled for this package. (Windows) For more information, see Variables for Windows applicability scans and command-line operations.
Check for Running Processes
Specify a process name, for example, Chrome.exe, and choose whether to kill or pause the process.
Copy a file or folder, create a folder, delete a file or folder, extract a file or folder, or rename a file or folder. For file/folder actions, the source is the folder from which the package is running. If you specify a different folder, for example, c:\temp, specify the fully qualified path. The destination requires the fully qualified path. For more information, see File/Folder actions.
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.
Tanium Client File Request
Specify an HTTP(S) address or a UNC file path and file name. Any URI that you enter must be whitelisted on the Tanium Server. For more information, see Tanium Platform User Guide: Managing whitelisted URLs.
- 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.
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 not, Deploy creates /Applications/firefox.app; if so, Deploy creates /Applications/firefox.app/firefox.app. To always replace /Applications/firefox.app, set the destination to /Applications instead of /Applications/firefox.app.
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.
Any subfolders of the folder that you specify are also deleted.
Supported file types for extracting a file are 7z, tar, zip, bzip2, gzip, xz, and Z. Specify an existing folder path or a folder path to create. For example, specify file example.zip and destination c:\temp\myunzippedfile.
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, click 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, click Software and then click Import Package.
You can also click Import Package from the Software Packages tab of the Software section in the Deploy Home page.
- 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.
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.
- From the Deploy menu, click Software.
You can also view the software package applicability by additionally clicking your package name.
- For more details about a specific applicability state, click Interact .
- To view the applicability details for the endpoints, click Full Report.
- From the Deploy menu, click Software and then click Software Bundles.
You can also click Software Bundles in the Software section of the Deploy Home page.
- Click New Software Bundle.
- In the Software Bundle Details section, specify the bundle name and description.
- In the Add Software section, select software options.
- Select the software packages to add to the bundle.
- Select a specific version, or choose Latest Applicable Version to automatically select the latest available version for each endpoint.
- Select the deploy action: Install, Update, Remove, or Install Or Update.
- 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, or by clicking the arrows next to the package number.
- 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 .
You can delete a software package or bundle only if it is not referenced in an active deployment.
Last updated: 6/30/2020 5:26 PM | Feedback