Upgrading Tanium Appliance software

Use TanOS to upgrade the TanOS system and the Tanium appliance role: Tanium Server, Module Server, Zone Server, and Zone Server Hub.

About Tanium Appliance software versions

The TanOS version is the version of the appliance operating system and menus. The appliance operating system is updated periodically to support new features and to support new Tanium Core Platform features.

The Tanium Core Platform version is the version of the platform server component. All components must run the same build version. The TanOS distribution includes installers for supported Tanium Core Platform versions. In Tanium Appliance deployments, support for a Tanium Core Platform release might require a TanOS upgrade.

Tanium Core Platform TanOS version required
7.4 1.5.5 or later
7.3 1.3.4 or later
7.2 1.2 or later, 1.3 recommended
Tanium Core Platform TanOS version required
7.2 or later 1.6.1 or later

Follow the upgrade paths indicated. Direct upgrade can result in unexpected behavior and is not supported.

Upgrade TanOS

TanOS 1.6.1 is the first release to support the Tanium Cloud Appliance; as such, there are no upgrade options from previous releases of TanOS. To migrate from an on-premise appliance to a Tanium Cloud Appliance, contact your TAM.

Copy the upgrade package to the /incoming directory on the Tanium Appliance, and use the TanOS menus to install the package.

Before you begin

  • Read the release notes for the TanOS versions that were released after your current version to stay informed about expected behavior.
  • Make sure the current deployment is working as expected, including all Tanium Core Platform servers and solutions.
  • Run a health check on each appliance to check the status of network services and Tanium services.
  • Obtain the TanOS upgrade package from your TAM.
  • As part of the upgrade, if you have an inactive partition, you can choose to perform a partition sync to back up the active partition to the inactive partition. Alternatively, for virtual appliances, you can create a snapshot of the virtual image before you upgrade. A normal upgrade does not require you to restore from the backups, but backups can save you work in the event you encounter issues and want to restore the appliances to a known functional state.
  • You can create a snapshot of the virtual image before you upgrade. A normal upgrade does not require you to restore from the backups, but backups can save you work in the event you encounter issues and want to restore the appliances to a known functional state.
  • During an upgrade, TanOS stops all Tanium services, and resumes any services after rebooting the appliance.

Upgrade paths

Starting from TanOS 1.3.x

  1. Use the TaniumTanOS_Upgrade-1.5.0.noarch.rpm upgrade file to upgrade to TanOS 1.5.0.
  2. Use the TaniumTanOS_Upgrade-1.6.1.noarch.rpm upgrade file to upgrade to TanOS 1.6.1.

Starting from TanOS 1.4.x or later

  1. Use the TaniumTanOS_Upgrade-1.6.1.noarch.rpm upgrade file to upgrade to TanOS 1.6.1.

Upgrade from TanOS 1.3.x

Version 1.3 does not have maintenance mode.

  1. Use SFTP to copy the TanOS upgrade file to the /incoming directory on the appliance.
  2. Log into the TanOS console as a user with the tanadmin role.
  3. Enter B to go to the Appliance Maintenance menu.
  4. Enter 3 and follow the prompts to complete the upgrade.

Upgrade from TanOS 1.4.x

TanOS 1.4 introduces a maintenance mode feature to ensure that the Tanium services that could potentially be disrupted by the upgrade operation are shut down properly before the upgrade process.

Follow these steps when upgrading from a TanOS 1.4.0 release to a later release.

  1. Use SFTP to copy the TanOS upgrade file to the /incoming directory on the appliance.
  2. Log into the TanOS console as a user with the tanadmin role.
  3. Enter Maintenance Mode:
    1. From the tanadmin menu, enter B to go to the Appliance Maintenance menu. ClosedView screen
    2. Enter C to go to the Maintenance Mode menu. ClosedView screen
    3. Enter 1 and follow the prompts to toggle on maintenance mode.
  4. From the Appliance Maintenance menu, enter 3 to go to the Upgrade TanOS menu.
  5. When prompted to back up the active partition to the inactive partition, enter Yes. ClosedView screen
  6. After partition sync has completed, follow the prompts to install the upgrade RPM. ClosedView screen

    The appliance reboots to complete the upgrade.

Upgrade from TanOS 1.5.x

TanOS 1.5 and later includes improvements to how maintenance mode is invoked during the upgrade workflow.

Follow these steps when upgrading from a TanOS 1.5.0 release to a later release.

  1. Use SFTP to copy the TanOS upgrade file to the /incoming directory on the appliance.
  2. Log into the TanOS console as a user with the tanadmin role.
  3. Enter B to go to the Appliance Maintenance menu.
  4. Enter 3 to go to the Upgrade TanOS menu.
  5. Enter the line number of the RPM file to use, and follow the prompts to perform the upgrade.
    1. If prompted to enter maintenance mode, enter Yes.
    2. When prompted to back up the active partition to the inactive partition, enter Yes.

What to do next

Perform the following steps after you upgrade TanOS to the latest version.

  1. Check to see if the firmware requires an update. For more information, see Install a firmware update.
  2. Run a health check to check the status of network services and Tanium services.
  3. Verify the installation.

If verification fails, see Troubleshooting the installation.

Upgrade Tanium server software

The server upgrade RPM files are included in TanOS installation and upgrade packages. It is possible that a server upgrade package is delivered separately. If so, copy the upgrade package to the /incoming directory on the Tanium Appliance and then use the TanOS menus to install it.

Upgrade path

Check with your TAM to understand the ramifications of direct upgrade and whether intermediate steps are recommended.

Before you begin

  • Read the release notes for all of the Tanium Core Platform versions that were released after your current version to stay informed about expected behavior.
  • All servers must have the same version number (for example, 7.4.3.1242); be prepared to upgrade all Tanium servers in your environment. The maintenance window for upgrading Tanium Core Platform servers is usually under an hour. As a best practice, complete the upgrade for all the servers in the same maintenance window. If you have a Tanium cluster, complete the upgrade for both Tanium Servers in the same window.
  • Your TAM will let you know when upgrades are advised and can assist you with the upgrade.
  • Your TAM will provide the upgrade package files.
  • Make sure the current deployment is working as expected, including all Tanium Core Platform servers and solutions.
  • Consult with your TAM if you plan to change the Tanium Server host name. Your TAM needs the new host name to update the Tanium license for you.
  • Back up the database. See Back up the Tanium database.
  • Back up the appliance. See Perform a partition sync.
  • If you have a redundant cluster configuration, complete the upgrade for all Tanium Server peers in the same window.

Order of upgrade

You must upgrade Tanium Core Platform servers in the following order:

  1. Tanium Server (see note)
  2. Module Server
  3. Zone Server Hub
  4. Zone Server

For a Tanium cluster, upgrade the primary server first, followed by the secondary server. For a Tanium cluster deployed through an Appliance Array, both servers must be running during the upgrade.

Upgrade the server software

  1. If necessary, use SFTP to copy the Tanium server RPM file to the /incoming directory on the appliance.
  2. Log into the TanOS console as a user with the tanadmin role.
  3. From the tanadmin menu, enter 1 to go to the Tanium Installation menu. ClosedView screen
  4. Enter U to upgrade Tanium software.
  5. If prompted to enter maintenance mode, enter Yes.
  6. Follow the prompts to complete the upgrade. ClosedView screen

What to do next

After you upgrade Tanium software, perform the steps listed on Verifying the installation to make sure the deployment is working as expected. If verification fails, see Troubleshooting the installation.