Setting up the discovery tool

VMware installation

1. Sign in to vCenter as a VMware administrator and switch to the directory where you want to download the discovery tool OVA file.

2. Download the OVA file from this URL: https://s3.us-east-1.amazonaws.com/atx.discovery.collector.bundle/releases/latest/AWS-Transform-discovery-tool.ova

Hyper-V installation

• Download the VHD file from this URL: https://s3.us-east-1.amazonaws.com/atx.discovery.collector.bundle/releases/latest/AWS-Transform-discovery-tool.vhd

1. Sign in to vCenter as a VMware administrator.

2. Use one of these ways to install the OVA file:

   1. Use the UI: Choose File, choose Deploy OVF Template, select the discovery tool OVA file you downloaded in the previous section, and then complete the wizard. Ensure the proxy settings in the server management dashboard are configured correctly.

   2. Use the command line: To install the discovery tool OVA file from the command line, download and use the VMware Open Virtualization Format Tool (ovftool). To download ovftool, select a release from the OVF Tool Documentation page. This is an example of using the ovftool command line tool to install the discovery tool OVA file.

      ovftool --acceptAllEulas --name='discovery tool' --datastore=datastore1 -dm=thin ATX-Transform-discovery-tool.ova 'vi://username:password@vcenterurl/Datacenter/host/esxi/'

      Descriptions of the replaceable values in the example:

      • The name is the name that you want to use for your discovery tool VM.

      • The datastore is the name of the datastore in your vCenter.

      • The OVA file name is the name of the downloaded discovery tool OVA file.

      • The username/password are your vCenter credentials.

      • The vcenterurl is the URL of your vCenter.

      • The vi path is the path to your VMware ESXi host.

3. Locate the deployed discovery tool in your vCenter. Right-click the VM, and then choose Power, Power On.

4. After a few minutes, the IP address of the discovery tool displays in vCenter. You use this IP address to connect to the discovery tool.

1. Copy the VHD file to the Windows Server machine that has the Hyper-V role enabled.

2. Open Hyper-V Manager.

3. Choose New, and then choose Virtual Machine.

4. Complete the setup wizard. On the Specify Generation page, select Generation 1. Generation 2 virtual machines do not support the VHD format. On the Assign Memory page, allocate at least 16384 MB. On the Connect Virtual Hard Disk page, choose Use an existing virtual hard disk and select the VHD file that you copied.

5. Start the VM. After a few minutes, check the Networking tab of the VM in Hyper-V Manager to find the IP address, or connect to the VM console and run ip addr. You use this IP address to connect to the discovery tool.

1. SSH to the discovery tool VM.

   ssh discovery@<discovery-tool-vm-ip>

2. Edit the Kerberos configuration file at /etc/krb5.conf.

   sudo nano /etc/krb5.conf

   Add the following configuration, replacing the placeholder values with your environment details.

   [libdefaults]
       default_realm = EXAMPLE.COM
       dns_lookup_realm = false
       dns_lookup_kdc = true
   
   [realms]
       EXAMPLE.COM = {
           kdc = dc01.example.com
       }
   
   [domain_realm]
       .example.com = EXAMPLE.COM
       example.com = EXAMPLE.COM

   Important

   Kerberos is case-sensitive. The realm name must be in uppercase (for example, EXAMPLE.COM, not example.com). The domain name in the [domain_realm] section must be in lowercase.

3. Verify that you can obtain a Kerberos ticket by running the kinit command.

   kinit username@REALM.COM

   Enter the password when prompted. If the command completes without errors, authentication succeeded.

4. Verify the ticket by running the klist command.

   klist

   The expected output is similar to the following.

   Ticket cache: FILE:/tmp/krb5cc_1000
   Default principal: username@REALM.COM
   
   Valid starting       Expires              Service principal
   01/01/2025 12:00:00  01/01/2025 22:00:00  krbtgt/REALM.COM@REALM.COM

5. Configure the discovery tool with the same case-sensitive principal that you used with kinit (for example, username@REALM.COM).

1. Ssh to Discovery tool VM

2. Place the CA certificate(s) that signed your target servers' WinRM certificates into trust store directory /etc/pki/ca-trust/source/anchors/ on the discovery tool VM. For example: sudo cp winrm-ca.pem /etc/pki/ca-trust/source/anchors/winrm-ca.pem. Note: If your target servers use certificates signed by different CAs, copy all relevant CA certificates to this directory.

3. Update the certificate trust store: sudo update-ca-trust

4. Reboot the VM

5. (Optional) To verify that certificates have been successfully imported, you can run the following command. sudo trust list —filter=ca-anchors | grep -A 5 "<certificate_name>"

Setup discovery tool

1. In a web browser access: https://ip_address:5000, where ip_address is the IP address of the discovery tool from Deploy Discovery Tool. The discovery tool uses a self-signed certificate for HTTPS connection which results in a security warning. Choose Accept the risk and continue to continue to the discovery tool console.

2. If you're accessing the discovery tool console for the first time, create a discovery tool login password. Create a password, which you will use for future logins.

   Important

   Remember this password - there is no password recovery mechanism.

To configure discovery tool to access VCenter

1. On the Discovery tool page, under Step 1. Configure discovery sources, choose Configure sources.

2. On the Configure discovery sources page, provide the vCenter URL/IP, the vCenter username and vCenter password and choose Save configuration.

   The discovery tool begins to collect vCenter information, as described in Discovered Inventory.

To configure Hyper-V access

1. On the Discovery tool page, under Step 1. Configure discovery sources, choose Configure sources.

2. On the Configure discovery sources page, provide a friendly name, the host FQDN or IP address, the authentication type (NTLM or Kerberos), the WinRM username, and the WinRM password. Choose Save configuration.

   The discovery tool begins to collect Hyper-V information, as described in Discovered inventory.

To import bare metal servers

1. Navigate to the Import servers page from the Discovery tool homepage.

2. Prepare a CSV file with the following columns: hostname_or_ip (required) and credential_name (optional).

   • The hostname_or_ip value must be a valid IPv4 address or a fully qualified domain name (FQDN).

   • The credential_name value, if provided, must match the friendly name of an OS credential that you already configured (SSH or WinRM).

3. Upload the CSV file. The tool validates all rows and rejects the file if any row is invalid.

Enable discovery tool OS Access

1. Navigate to the Set up OS access page to provide Windows and Linux credentials.

2. Choose a protocol that you want to add credentials for.

3. Provide the required credentials for the selected protocol.

4. Select Auto-connect to enable the discovery tool to try all provided credentials on discovered servers until matching credentials are found for each server.

   See Using Auto-Connect Feature With Caution for important security recommendations regarding the auto-connect feature.

5. Choose Set up and connect.

To manually update the tool

1. Download the latest discovery tool image file (OVA for VMware or VHD for Hyper-V) from the provided link.

2. (Optional) We recommend that you delete the previous discovery tool image file before you deploy the latest one.

3. Follow the steps in the Deploy the discovery tool section to deploy the updated version.