Recommended information

Discovery system requirements

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Here's some best practices and recommended information for using Discovery.

Do not use the Discovery/scans folder as import folder

If you are using the Discovery Tool on the same server that is running your Jira/Insight service (we also not recommend that!)

then please do not use the scans folder of the Discovery Tool as the import folder.

The import function will create sub folders and handling the imported files in the import folder, which will get in conflict with the Discovery-Tool logic.

Simply create a separate import folder on the server and let the Discovery copy the result files to that folder.

Error messages when setting up Discovery or Collector

Error MessageThis implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
Cause

This problem occurs because the MD5 algorithm is not FIPS compliant. The MD5 algorithm uses Windows Communication Foundation to obtain a hash value. The hash value generates a unique name for a data contract.

Resolution

To correct this behavior:
1. Disable the "Local Security Setting System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" policy in Windows.

1. Go to Start > Control Panel > Administrative tools > Local Security Policy. The Group Policy dialog appears. Under the "Local Policies" heading, select "Security Options" and look for the entry, "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing." If this entry is enabled, disable it. 

3. Open the registry editor and browse the following path. Make sure this registry subkey is set to 0: 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy


The interface is unknown. (Exception from HRESULT: 0x800706B5)

  • If the machine hosting your Discovery installation is running Windows Server 2008 R2, the likely explanation for the problem is the absence of this patch on your Discovery server. Windows Server 2008 R2 has some known issues. Make sure Service Pack 1 is installed and the aforementioned patch is applied as well.
  • If the machine hosting your Discovery installation is not running Windows Server 2008 R2 and the scanning errors are limited to specific Windows computers, it is also possible that WMI (Windows Management Instrumentation) is corrupt on those client machines. Follow the instructions on the destination server to fix that issue:
    • Run repairwmi.cmd on the client machine that's generating the WMI corruption errors. It recompiles all .mof WMI files found in the %windir%\System32\Wbem\Repository folder.
    • Execute the commands below on the client machine that's generating the WMI corruption errors.
      Winmgmt.exe /standalonehost
      Winmgmt.exe /resetrepository
  • If the script shows that wmidiag is missing then you can get it here Microsoft WMIDIAG Download

Missing Product results from Windows Server 2003

In Windows 2003 Server, Win32_Product is not enabled by default, and must be enabled as follows:

  1. In Add or Remove Programs, click Add/Remove Windows Components.
  2. In the Windows Components Wizard, select Management and Monitoring Tools and then click Details.
  3. In the Management and Monitoring Tools dialog box, select WMI Windows Installer Provider and then click OK.
  4. Click Next.

Usage of parallel threads

You will get the best scan performance by using two threads per CPU-Core.

For example 2 Cores = 4 Threads, 4 Cores = 8 Threads and so on.

Using more then two threads per core will not increase the scan performance.

Multiple Discovery Instances

It is possible to use multiple Instances of the Discovery-Tool, but it is not recommended.

If the instances executing scans at the same time it can affect the performance of the scans.

Also it is possible to create memory leaks and affect the system performance.

It will be more effective to use one instance with multiple scan settings and using parallel threads.

Overlapping Scheduled Scan-Settings

Scan-Settings can not overlap.

If one Setting is executing and another Setting reaches the scheduled time it will start after the running Setting is finished.

Scanning huge amount of destination Systems

If you reaching the maximum of scannable systems with all possibility's of

split up Scan-Setting over the day and using 2 threads per CPU-Core

then you need to create another discovery server to spread the "load" to different scan-systems.

(Do not create multiple Discovery Instances on the same server)

Maximum amount of "scannable" systems per day

As the required time for a scan depend on many various factors

(e.g. WMI needs more execution time, how many applications are installed, custom pattern, available CPU-Cores, etc.)

that we can just provide some example calculations and you need to figure out what are your limits in your environment.

The following calculations are based on the experience of average required time for:

System Type

Average time

Windows Client

(20 Applications)

85 seconds
Windows Server45 seconds

Linux Client/Server

20 seconds

Mac OS100 seconds
SNMP Devices2 seconds


Rough calculations for example environments:

Windows Clients

Windows Server

Linux Clients/Server

Mac OS

SNMP Devices

Average Time

Example Discovery Setup

Windows Clients

Windows Server

Linux Clients/Server

Mac OS

SNMP Devices

Average Time

Example Discovery Setup

5020

55160 seconds

1 Scan-Server

1 CPU-Cores

2 Threads

505050
207540 seconds

1 Scan-Server

1 CPU-Cores

2 Threads

200150100305029950 seconds

1 Scan-Server

2 CPU-Cores

4 Threads

300500150502056040 seconds

1 Scan-Server

2 CPU-Cores

4 Threads

100100500

23000 seconds

1 Scan-Server

2 CPU-Cores

4 Threads

50015001500

140000 seconds

1 Scan-Server

4 CPU-Cores

8 Threads

100020002500300100255200 seconds

2 Scan-Server

2 CPU-Cores

4 Threads

200020004000

340000 seconds

2 Scan-Server

4 CPU-Cores

8 Threads

1000300050001000500421000 seconds

2 Scan-Server

4 CPU-Cores

8 Threads

400070004000
2000739000 seconds

3 Scan-Server

4 CPU-Cores

8 Threads

Last modified on Sep 8, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.