Managing packages and bundles

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.

Before you begin

For applicability checks and command-line operations, make sure that all endpoints have the required system environment variables defined. For more information, see System environment variables.

Create a software package

  1. From the Deploy menu, click Software and then click New Software Package.
  2. Provide package options.
    1. 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, 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.

    2. Provide the general information 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.

    3. Select Deploy operations: install, update, or remove.
    4. Provide the minimum system requirements for the package to run on the endpoint.
    5. Add a list of detection rules for prerequisite software. For more information, see Variables for applicability scans and command-line operations.
    6. (Optional) If the Update operation is selected, add a list of detection rules for previous versions. For more information, see Variables for applicability scans and command-line operations.
    7. Add conditional commands for any of the Deploy operations that you enabled for this package. For more information, see Variables for applicability scans and command-line operations.
    8. Add a list of detection rules for installation verification. For more information, see Variables for applicability scans and command-line operations.
  3. Click Create Package.
  4. Provide your password and click Confirm.

Variables for applicability scans and command-line operations

When you create a software package, you can use ||PROGRAMFILES|| or ||PROGRAMFILES32BIT|| as variables for applicability scans and command-line operations. For the Required Software, Update Detection, and Install Verification sections, you can use these variables in the file paths if you select the File Path or File Version filter fields.

Installer Architecture Variable Path
32-bit on 32-bit endpoint ||PROGRAMFILES32BIT|| 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

Export a software package

You can export a software package so that you can later import the package on a different server or recreate a deleted package.

  1. From the Deploy menu, click Software.
  2. Click the name of your package and then click Export .

The ZIP file is available in your downloads folder.

Import a software package

You can import a previously exported software package on a different server or recreate a deleted package.

  1. From the Deploy menu, click Software and then click Import Package.
  2. Browse to the previously exported ZIP file and click Import.
  3. Click Upload File for any required files.
  4. Click Import or Import Duplicate if you are importing a duplicate package.
  5. Provide your password and click Confirm.

Distribute the software package catalog

After you create or edit a software package, you are prompted to distribute the software package catalog to the endpoints. Click Distribute Catalog, provide your password, and click Confirm. When the endpoints receive the updated software package catalog, you can view the package applicability.

View software package applicability

  1. From the Deploy menu, click Software.
    You can also view the software package applicability by additionally clicking your package name.
  2. For more details about a specific applicability state, click Interact .
  3. You can also click Full Report to view the applicability details for the endpoints.

Create a software bundle

  1. From the Deploy menu, click Software and then click Software Bundles.
  2. Click New Software Bundle.
  3. Provide package options.
    1. In the Software Bundle Details section, specify the bundle name and description and select the OS platform.
    2. In the Add Software section, select which software packages you to want to add to the bundle, the deploy action, and whether you want the bundle to continue or exit 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.

  4. Click Create Bundle.

Edit a software package or 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.

Delete a software package or bundle

To delete a package or bundle, click the name of your package or bundle and then click Delete .

You can only delete a software package or bundle if it is not being referenced in an active deployment.

Last updated: 10/3/2018 3:15 PM | Feedback