• Products
  • Get started
  • Documentation
  • Resources

Update Assets Discovery and the Assets Discovery collector

Before you begin

  • You must have Jira Admin permissions as well as administrator permissions on your Windows or Linux system to install Assets Discovery.

  • Please make a backup of your Discovery folder to be on a safe side if something happens during the update process.

  • If you are using the Assets Discovery or Collector Tool on a Linux Environment please make sure that you have stopped configured cron tasks before updating

    *Only available by using the Discovery Tool on a Windows Environment.

The update process automatically stops the running Discovery or Collector Service(s) when running. After the update the Service(s) that has been stopped for the update process will be restarted.

Upgrade notes

  • 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.

  • 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.

  • 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.

Updating Assets Discovery and the Collector

To update Assets Discovery and the Collector to the latest version:

  1. Uninstall Discovery-Service-XXX (Discovery.exe -u) and Discovery-Collector-Service-XXX (Collector.exe -u) if they were installed. (XXX stands for a unique value auto-generated for you.)

  2. Run Discovery in settings mode (Discovery.exe -s).

  3. Navigate to the Update tab.
    This tab contains details of the latest version.

  4. Select Update now to run the update service, which downloads and installs the latest version from Atlassian Marketplace.

  5. Reinstall Discovery-Service-XXX (Discovery.exe -i) and Discovery-Collector-Service-XXX (Collector.exe -i) if they were uninstalled in step 1.

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

  1. Uninstall Discovery-Service-XXX (Discovery.exe -u) and Discovery-Collector-Service-XXX (Collector.exe -u). (XXX stands for a unique value auto-generated for you.)

  2. Download and copy the new version (e.g. Discovery_<version>.zip) to the update subfolder in your Discovery folder.

  3. Run update.exe.

  4. Choose if you want to update your ObjectHashSettings.xml file (it won't be updated by default).

    • If you didn't make any changes to the file, select Yes to get the updates.

    • If you made changes to the file, select No, and apply your changes manually to the new file.

  5. Reinstall Discovery-Service-XXX (Discovery.exe -i) and Discovery-Collector-Service-XXX (Collector.exe -i) if they were uninstalled in step 1.

Updating to version 3.x

You can also try out the beta release of Discovery 3.x. See Updating Discovery to version 3.x.

Uninstall 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. Stop the Discovery-Agent service Discovery Agent Service. You can also use the command line "sc stop Discovery Agent Service".

  2. Go to the agent installation path (by default it's C:\Program Files (x86)\Atlassian\Discovery Agent Installer). Back up the pattern files if the default patterns were changed. If new patterns were created, they will remain.

  3. Go to the Discovery installation directory from the same version as the Discovery Agent (if the Agent is on version 3.1.4, you’ll need to use the Discovery 3.1.4 installer).

    1. Double-click on the Discovery installer (Discovery_Agent_Setup_x86 or Discovery_Agent_Setup_x64) depending on your OS.

    2. Select Remove Discovery Agent Installer. As a result, all DLL files will be removed from the Agent directory, but the following directories will remain: logs, pattern (only if there are custom pattern files), scans, Agent.bak (it holds the previous configuration).

Install a new Discovery Agent

  1. From the Discovery_Agent_Setup.msi Installer package, open the new version of Discovery_x.x.x.zip and select Install

  2. If you made changes either with custom patterns or with the Agent.cfg file, change it in the target folder and add the path where the Discovery Agent was installed before.

  3. Go to the Agent directory again and remove the Agent.cfg file, which was created by the installer and holds the default configuration.

    • If customers had made some changes in previous version, we need to remove it.

    • Bear in mind, we still have the Agent.bak file which contains previous configuration.

  4. Stop and start the Discovery Agent Server service. A new Agent.cfg file should have been created based on the *.bak file.

If you need to restore the file, you must stop the Discovery Agent service first, restore the file, then start the service 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:


1 %windir%\Microsoft.NET\Framework\[version]\config\machine.config


1 %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 is removed.

  6. Update Discovery to the latest version.

  7. Install the service with "discovery -i" or "collector -i"

Additional Help