Upgrading from previous versions of Discover

If you installed previous versions of Discover, make sure that you complete any required migration activities.

Upgrade Discover

Discover 2.8 updates the Discover database schema, which might take some time if you have a large database. If you have an Active-Active cluster for your Tanium Servers, complete the entire upgrade process on the first Tanium Module Server before you upgrade the other servers. Review the banner on the Discover home page to see a completion of the database migration before proceeding.

  1. From the Main menu, click Tanium Solutions.
  2. In the Discover section, click Upgrade to Version.
  3. Review the list of Saved Actions, Packages, and Sensors. Most are overwritten during the upgrade process. Click Proceed with Import.
  4. To confirm the upgrade, return to the Tanium Solutions page and check the Installed version for Discover.
  5. Reconfigure the service account.
    Prior to Discover 2.9: The user name and password is not preserved after Discover 2.x upgrades. From the Discover home page, click Settings . Update the service account settings and click Save Changes.
    Discover 2.9 and later: You do not need to reconfigure the service account after upgrading.
  6. The Discover actions get re-created during upgrade. If you have action approval enabled, you must approve these actions again. From the Main Menu, click Actions > Actions I Can Approve. For more information, see Using action approval.

Upgrade the Discover Client Deploy solution

  • In Discover 2.0 and later, you must import the Discover Client Deploy solution after you install the Discover solution. For more information, see Install Discover Client Deploy solution.
  • If you are upgrading from Version 1.1 or earlier, Tanium Connect is no longer a requirement for Client Deployment. Discover Version 1.2 adds a new user interface for configuring and deploying the Tanium Client. For more information, see Deploying Tanium Client to unmanaged endpoints.
  1. From the Main Menu, click Tanium Solutions.
  2. In the Tanium Content section, select Discover Client Deploy and click Upgrade Solution.
  3. Review the list of Saved Actions, Packages, and Sensors. Most are overwritten during the upgrade process. Click Proceed with Import.
  4. To confirm the upgrade, return to the Tanium Solutions page and check the Installed version for Discover Client Deploy.
  5. (Optional) In Discover 2.0 and later, PsExec is no longer installed and configured by default. For more information about configuring PsExec to deploy the Tanium Client, see (Optional) Set up PsExec on Tanium Module Server.

Review changes to the Nmap discovery method after upgrading to Discover 2.5

In Discover 2.5, the Npcap library replaced the WinPcap library for the Nmap discovery method.

If you used the Nmap discovery method and are upgrading from a previous version of Discover, both WinPcap and Npcap are installed on your endpoints. If WinPcap is being used only to support the Nmap discovery method, you can remove WinPcap from your endpoints.

The Discover upgrade process does not remove WinPcap. Contact your TAM for assistance with uninstalling WinPcap.

For more information about the Nmap discovery method, see Nmap scan discovery.

Remove unmanaged assets and Discover artifacts from Version 1.0

If you used Discover Version 1.0, you might want to clean up your endpoints by removing unmanaged assets or Discover artifacts. These artifacts include scan results files, configuration files, and the scanner utility.

Clean up unmanaged interfaces artifacts

  1. Ask the question: Get Has Legacy Unmanaged Assets Artifacts from all machines
  2. Run the following actions against the systems that report true:
    • Remove Legacy Unmanaged Assets from Endpoints
    • Remove Legacy Unmanaged Assets from Endpoints for Non-Windows

    These actions remove the following files:

    Tanium Client\Tools\oui.txt
    Tanium Client\Tools\unmanaged_assets_Linux_Mac.sh
    Tanium Client\Tools\Scans\uaresults.txt
    Tanium Client\Tools\Scans\uaresultsreadable.txt
    Tanium Client\Tools\Scans\maresults.txt
    Tanium Client\Tools\Scans\maresultsreadable.txt
    Tanium Client\Tools\Scans\Names.dat
    Tanium Client\Tools\Scans\WakeResults.dat
    Tanium Client\Tools\Scans\WakeResultsReadable.dat
    			

Clean all the endpoints of Discover artifacts

  1. Ask the question: Get Has Discover Artifacts from all machines
  2. If any endpoints report back as true for having Discover artifacts, run two actions against that answer:
    • Remove Discover from Endpoints
    • Remove Discover from Endpoints for Non-Windows

When the action runs, any Discover artifacts are removed from the endpoint. The action looks for the following directory:

Tanium Client\Tools\Discover

Disable scheduled asset tracking actions from Discover Version 1.0

If you upgraded from Discover Version 1.0, you must remove the scanning actions that you previously configured and add a new scanner configuration.

  1. From the Main Menu, click Actions > Scheduled Actions.
  2. Verify that the following Unmanaged Asset Tracking actions are disabled:
    • Unmanaged Asset Tracking - Run Scan Non-Windows
    • Unmanaged Asset Tracking - Run Scan
    • Unmanaged Asset Tracking - Deploy Scan Tools and Scan - Non-Windows
    • Unmanaged Asset Tracking - Deploy Scan Tools and Scan

Last updated: 9/18/2018 2:03 PM | Feedback