Choosing a Discovery Strategy

Different network environments require different discovery strategies. This page helps you choose the right approach based on your network topology, security requirements, and device types.

Standard Networks

For standard network hardware plus PC discovery on a single-segment network:

1. Use the application server as the Collection Server (the default configuration)
2. Use the default menu options to run discovery (Discover a Location or Discover a Computer/IP Range)
3. Optionally configure the discovery scripts to include PCAnalyser, WMI, or Remote Registry for additional data collection

This covers the majority of installations with a single site and straightforward network topology.

Remote and Mobile Users

Choose logon script discovery when:

• Desktop machines have different local administrator passwords that prevent a single Credential Pack from working
• Remote laptop users (e.g., salespeople) only connect to the network occasionally
• Firewalls or NAT prevent the Collection Server from initiating connections to target machines

With logon scripts, the PCAnalyser agent runs each time a user logs on, sending data back to the Collection Server share. No remote administrative access is needed.

Multiple Network Segments

When separate networks exist that are not visible to each other:

1. Install a Collection Server on each network segment
2. Connect each Collection Server to the application server either:
   • Through a web services login (if network connectivity exists between the servers)
   • By manually copying discovery files from the Collection Server back to the application server (for air-gapped networks)

Unix, Linux, and Mac Discovery

For non-Windows operating systems, choose SSH technology:

• The discovery engine connects via SSH and runs commands to collect hardware and software data
• If root access is needed for full discovery, configure credential escalation (su or sudo)

Root/Sudo Access Configuration

Two methods are available for privilege escalation, both requiring two Credential Packs -- one for SSH login and one for root:

Note: If the root Credential Pack uses the username sudo, the system uses sudo instead of su, responding to each sudo prompt automatically.

XDSL Configuration for Root Access

The discovery script must include this line in its settings section for privilege escalation to work:

SWITCHUSERCREDENTIALPACK=*ROOT

And the corresponding Credential Pack must exist with the correct naming convention.

Network Devices (SNMP)

For switches, routers, firewalls, and other network devices, configure SNMP discovery with:

• The appropriate SNMP version (v1, v2, or v3)
• A Credential Pack containing the community string or SNMP v3 credentials
• The IP range Technology field set to "Network Devices"

See SNMP Discovery for detailed configuration.

Strategy Summary

Tips

• You can combine multiple strategies in a single installation -- for example, agentless WMI for servers, logon scripts for desktops, and SNMP for network devices
• Start simple and add complexity as needed -- the default configuration handles most environments
• Document your discovery strategy so other team members can understand and maintain it

Related Articles

• Discovery Architecture Overview — the components that make up the discovery engine
• Bandwidth Requirements — network impact considerations
• Credential Packs — managing authentication for different strategies
• Logon Script Discovery — setting up logon scripts
• SNMP Discovery — configuring SNMP for network devices