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

Autodiscovery automates the collection of asset data across your infrastructure. To maintain system stability, it is essential to provide dedicated resources to the discovery appliance and use optimized scan settings. This article covers the hardware specifications, network requirements, and credential safety protocols necessary for a successful deployment.

System resource requirements

For the appliance to perform efficiently, ensure the host environment meets the following resource specifications.

Ensure there is a dedicated resource pool for the virtual machine to prevent resource contention issues with other guests on the same host.

Network and scan configuration

Identify the IP discovery scope or ranges of interest before starting a job. If your environment does not use IPv6, select the Ignore IPv6 option when configuring discovery jobs to improve processing speed.

Remote collectors

WinRM Windows discovery can be executed from a Remote Collector. If you have segmented networks, deploy remote collectors to those specific segments and select them during the job configuration to reduce cross-segment traffic.

Exclusions and optimization

You can limit the scope and volume of discovered data to reduce noise and overhead. This shortens the overall discovery time.

• Service port exclusions: To exclude known service port ranges, go to Tools > Settings > Global Settings > Win/nix Exclusions. Add your desired exclusions to the autodiscovery application.
  
  

• IP and MAC exclusions: To ignore specific devices across all jobs, create an exclusion under Tools > Settings > Global Settings > Win/nix Exclusions. 
  Note: These devices are still discovered, but their details are dropped during ingestion.

Manage permissions and ports

Proper credential management and port availability are critical for successful data collection. To ensure secure and effective scanning, follow these:

• Create a dedicated discovery account: Do not set up an autodiscovery scan using critical production account credentials. Create a separate, dedicated account to use only for discovery.
  Note: Account lockout could result in an otherwise avoidable outage depending on your permissions and configured password policies. You are responsible for any such behavior.
  
  

• Assign platform permissions: Ensure the discovery account has the necessary rights for your specific operating systems.

  • For Windows and WMI namespace, refer to the Windows and HyperV Discovery page.

  • For Linux and Sudo usage, refer to the Linux and Unix Server Discovery page.
    
    

• Configure communication ports: Verify that the required ports are open between the appliance and target assets. For a complete list of communication requirements, see the Discovery Port Configurations documentation. 

If you have questions regarding specific privilege level requirements for WMI Namespaces or *nix commands, contact the support team.