Update Assets Discovery

Follow these steps to update Discovery and the Collector.

Before you begin

• Create a backup of your Discovery folder.
• If you're using Discovery on Linux, stop cron tasks before updating.
• Note that once you start the update process, the Discovery or the Collector services will be stopped on Windows systems. They'll be restarted once the update process finishes.
• Note that the Discovery and Discovery Agent version should match.

Upgrade notes

Upgrading to Discovery Tool 7.0.0-Cloud/7.0.0

With the introduction of a new encryption algorithm in Discovery Tool 3.1.5-Cloud/6.1.5, we removed the old encryption algorithm in Discovery Tool 7.0.0-Cloud/7.0.0. For a smooth upgrade, follow the below upgrade paths:

• If you’re on a version below 3.1.5/6.15, upgrade to 3.2.1/6.2.1 before you upgrade to version 7.0.0 or above. We recommend that you convert your credentials to the new encryption algorithm in 3.2.1.
• If you’re on version 3.1.5 or later, you can directly upgrade to version 7.0.0 or later.

We also changed the deserialization method for agent communications. To scan data through agents, you’ll need to update all agents to the latest version as the Discovery Tool cannot communicate with agents on versions below 7.0.0.

Upgrading to Discovery Tool 3.2.1-Cloud/6.2.1

In Discovery Tool 3.2.1-Cloud/6.2.1, we removed the JustUseFirstIP setting for Agents. You’ll need to use other settings for network interface communication. Learn how to set up Discovery Agents

Upgrading to Discovery Tool 3.2.0-Cloud/6.2.0

In Discovery Tool 3.2.0-Cloud/6.2.0, we added an Agent Token to secure the communication between the Discovery application and Discovery Agents.  You’ll need to update all scanned Discovery Agents manually to the same version as the Discovery Tool and configure the Agent Tokens. You’ll also need to update the password in SFTPSettings so it can be encrypted again.

For detailed upgrade notes, see Updating Discovery to 3.2.0-Cloud/6.2.0.

Upgrading to Discovery Tool 3.1.11-Cloud/6.1.14

In Discovery Tool 3.1.11-Cloud/6.1.14, we’ve modified the naming pattern of the download zip file from Discovery_X.Y.Z.zip to assets-discovery-X.Y.Z.zip. When you’re upgrading from a version below 3.1.11-Cloud/6.1.14 to 3.1.11-Cloud/6.1.14 or later, rename the download zip to the previous format.

Upgrading to Discovery Tool 3.1.5-Cloud/6.1.5

In Discovery Tool 3.1.5-Cloud/6.1.5, we’ve changed the encryption mechanism. When you upgrade, we’ll use the new encryption algorithm for secure data you’ve saved before the upgrade. You’ll need to update all scanned Discovery Agents manually to the same version as the Discovery Tool.

Upgrading to Discovery Tool 3.0.0-Cloud/6.0.0

If you're on a version below 3.0.0, refer to Updating Discovery to version 3.x.

Update Discovery and the Collector

To update Discovery and the Collector to the latest version:

1. Run Discovery in settings mode (Discovery.exe -s).
2. Navigate to the Update tab.
   This tab contains details of the latest version.
3. Select Update now to run the update service, which downloads and installs the latest version from Atlassian Marketplace.

To update Discovery and the Collector to the latest version manually or to a version below the latest version:

1. Download the installer package from the Atlassian Marketplace.
   It is a .zip archive, which contains 2 installers (one for Discovery/Collector and one for Agent).
2. Unzip assets-discovery-XYZ.zip archive.
3. If you're using Linux, you'll need an additional package to unpack MSI.
4. Run the installer and select the path to the previous install directory.
   If you want to use the default path, C:\Program Files\Atlassian\Discovery Tools, you'll need to copy configs and auto generated files such as credentials store, credentials.known, and ObjectHashSettings.
5. Select Next to complete the installation.

Install a new Discovery Agent

To install a new Discovery Agent:

1. Download the latest assets-discovery-x.x.x.zip from the Atlassian Marketplace and unpack it.

2. Run the Discovery_Agent_Setup.msi installer package.

3. Follow the installer steps to finish the installation.

Uninstall your Discovery Agent

To uninstall your Discovery Agent:

1. Go to Programs and Features.

2. Uninstall the Discovery Agent Service.

Upgrade your Discovery Agent

If you have Discovery Agents installed on a remote scanned server, the Agent installer from the upgraded version needs to be copied over to each of those Agents and upgraded as well.

To upgrade your Discovery Agents:

1. Go to the agent installation path (by default it's C:\Program Files\Atlassian\Discovery Agent).
   Back up configuration files Agent.cfg and the pattern files if the default patterns were changed. If new patterns were created, they will remain.
   Backed up files should be used to restore your configuration if needed.

2. Download latest assets-discovery-x.x.x.zip from the Atlassian Marketplace and run Discovery_Agent_Setup.msi installer package.

3. Follow the installer steps to finish the installation. 

4. Previous Agent configuration should be applied automatically after the upgrade. If not, follow next steps: 

   1. Stop the Agent Service sc stop Discovery Agent Service.

   2. Copy backed up Agent.cfg and patterns to installation folder.

   3. Start Agent service sc start Discovery Agent Service.

If you face any issues with the installation, try to remove the current Discovery Agent and Discovery Agent Service via Programs and Features first and install the latest version again.

Known issues and troubleshooting

.NET Framework config

If you’re having trouble loading DLL’s from remote source, add the following machine.config configuration to your .NET framework policies:

• 32-bit: %windir%\Microsoft.NET\Framework\[version]\config\machine.config
• 64-bit: %windir%\Microsoft.NET\Framework64\[version]\config\machine.config

After the update, you change modify this back to the previous settings.

Service instance ID changed

We've noticed that in some versions, the Instance ID for the running service is different than the one shown in the UI. If you encounter this problem, you can fix it by following these steps:

1. Open services and find the service for the Discovery or Collector.
2. Open the command prompt with admin privileges.
3. Run sc stop Discovery-Service-<ID> or sc stop Collector-Service-<ID>.
4. Run sc delete Discovery-Service-<ID> or sc delete Collector-Service-<ID>.
5. Refresh the services and make sure the service has been removed.
6. Update Discovery to the latest version.
7. Install the service with discovery -i or collector -i.