The remote collector is available as a self hosted managed virtual appliance. It can be installed on various hypervisors (list the supported ones), or it can be hosted in various clouds (as listed). Most customers will want the on-prem ones first and cloud second.

Note: Available only for new signups after the 31 March, 2026 release. If you signed up earlier, refer to the existing ITAM documentation.

Remote Collectors (RC) perform agentless discovery across network segments. It is available as a pre-configured image for cloud marketplaces, including AWS, Azure, and Google Cloud. 

TABLE OF CONTENTS

• Install Remote Collector
  • How to install and configure a Remote Collector

How to install and configure a Remote Collector

To begin discovering assets, you must deploy at least one remote collector within your target network segments. Follow these steps to install and configure a Remote Collector:

Step 1: Access Remote Collector

1. Navigate to Admin > Asset Management > Discovery Hub.

2. Select Remote Collectors and agents > External tools > click Download in the Remote Collector section.
   

Once the RC is downloaded and configured you can extend your discovery by hosting RC on a hypervisor of your choice.

Step 2: Add a Remote Collector group and connect to Remote Collector

1. Go to Admin >  Asset Management > Discovery Hub > Remote Controllers and agents > Remote Collector Groups tab > click Add new.

2. Enter the name for the group.

3. Enable the Windows Discovery Services toggle if you plan to allow this remote collector group to discover windows devices in addition to network and cloud based systems.

4. Optional, enable Proxy Settings and enter proxy details and click Save.
   

5. Go to the Remote Collectors tab and click Add new. 

6. Select the Remote Collector group that you created earlier and click Generate to create an OTP code .
   Note: Select a collector group or create a new one before generating OTP code.
   

7. Copy the token for later use. This token includes the security key needed to communicate with your instance.
   
   Note: Enter this token in your Remote Collector or WDS console to complete registration. Token will expire in 30 minutes.

8. Host the RC on a hypervisor of your choice. Ensure to follow the system requirements. 
   

9. Log in to the RC using SSH. Use the default credentials: client <IP address of RC>, Password- device42

10. In the Remote Collector Setup, the hostname must be your instance. You can change the name later if required.  

11. Paste the token to securely bind the collector to your instance and click Register. See how to copy a token in Step:2.
    

Step 3: Change user password

1. Choose option (p) to enter the Change Password (user client) menu.

2. Enter and verify the new password.

3. Click Save.

Caution: Do not put an RC into production without changing the default password.

Step 4: Configure the NTP Settings

1. Choose option (n) to enter the NTP Client Settings menu.

2. Select Daily sync is chosen.

3. Select to Reboot sync to enable an admin to reboot the RC within the cloud interface, which can help resolve unusual RC behavior.

4. Click Manual Sync if you want to perform a manual sync now, else click Save.
   

Step 5: Optional, specify hostname

1. Choose option (s) to enter the Server Settings menu.

2. Enter a hostname.

3. Click Save.
   
   

Step 6: Configure the Network Interface

This is only needed if your RC has multiple networks assigned, otherwise the first one is picked. 

1. Choose option (u) to enter the Network, Connectivity and Utilities menu.

2. Choose option (n) to enter the Network Interfaces menu.
   
   

3. Select the default interface (highlighted in white) and press Enter.
   

4. If using a Static IP, deselect Use DHCP and enter the IP Address, Subnet, Gateway, and DNS server(s). If using IPv6, specify the IPv6 Address and Gateway. It is recommended to have a static IP for RC.

5. Click Save, then Exit.
   

Once the Remote Collector is configured the state will show as Connected.