Discovery client installation requirements

Discovery client is an executable program that you can install on a single machine.

This page describes the hardware and software requirements for installing discovery client. To learn how to download and install the discovery client, see the installation process.

Hardware requirements

For optimal performance, the physical or virtual machine on which you install discovery client must meet the following specifications, which depend on the number of servers in your infrastructure:

  • Up to 10,000 servers: 2 CPU core, 12 GB RAM, 30 GB free space.

The specifications of the machine where you install the discovery client and the total number of servers in your infrastructure determine the collection frequency of the scanning cycles. Using a less powerful machine than required might result in reduced performance and capabilities.

Operating system requirements

To install discovery client, your machine must run one of the following operating systems:

  • Windows Server 2016 or higher
  • Windows Desktop client version 10 or higher (64-bit)

Software requirements

Discovery client requires one of the following browsers installed:

  • Google Chrome: 2 latest versions
  • Microsoft Edge: 2 latest major versions

Connectivity requirements

For successful data collection, the discovery client must be able to access the target servers from the machine where it is installed.

If you want to upload the collected data to Migration Center, the discovery client must have access to the following URLs:

  • https://accounts.google.com
  • https://console.cloud.google.com/
  • https://www.googleapis.com
  • https://cloudresourcemanager.googleapis.com
  • https://migrationcenter.googleapis.com
  • https://iam.googleapis.com
  • https://oauth2.googleapis.com
  • https://www.gstatic.com
  • https://fonts.gstatic.com

Additional requirements might apply depending on your infrastructure configuration, as follows:

  • If you have multiple non-routable security zones, install the discovery client within each zone, domain, or VLAN to avoid firewall configuration changes.
  • If you have multiple non-routable security zones, and want to access assets across such zones using a single data collector, use the following firewall exclusions for communication between the IP of the discovery client (source) and the target assets:
    • Linux SSH: Allow TCP inbound port 22.
    • Windows WMI: Allow TCP inbound port 135 and TCP inbound dynamic ports 49152-65535 for Windows Server 2008 and later.
    • For the bulk scan option, you need to allow ICMP echo requests.
  • If you require access through a proxy server to connect to the internet, enable this from the Settings tab and specify the proxy configuration.

What's next