Note

 

This documentation supports the 20.16.01 version of Remedyforce.

To view the latest documentation, select the latest version from the Product version menu.

How discovery works

License Required

This section is valid for the following licenses:

  • BMC Remedyforce Base
  • BMC Remedyforce Client Management - Premium
  • BMC Remedyforce Client Management - Premium Plus

The initial process to discover devices in your network is the same across all licenses. To initially discover devices, you do not need to install an agent on all your network devices.

BMC Remedyforce Base license provides agentless discovery solution that discovers operating system, hardware configurations, and software inventories in your IT environment. You can manage discovered devices by upgrading your Base discovery license, installing agents on discovered devices, and performing direct actions (such as, remote control or view registry) and operational rules on them.

The following topics are provided:

The following video (2:53) provides an overview to Remedyforce Discovery.

 https://youtu.be/WGHLGDNdOcI

Discovery components

BMC Remedyforce discovery requires the following components:

ComponentDescription
Remedyforce Discovery ServerThis server enables communication among scanners, BMC Remedyforce, and discovered devices. After discovery, the operating system, hardware configuration, and software inventory details of discovered devices are stored on the server.
Scanners

A scanner is a Windows or Linux device in your network on which an agent is running. A scanner executes scans on individual devices or groups of devices, called target list on which agent might not be running. It accesses the devices via different protocols to retrieve various device information.

How devices are discovered

The following figure shows how the discovery components work together to discover devices in your network:

How a scanner discovers a device

To scan a device, scanner performs the following actions:

  1. Splits the target list members into smaller units.
  2. Uses the Network Mapper (Nmap) (depending on the scan configuration) to perform the following actions:
    • Discover host
    • Scan port
    • Detect service and OS
  3. After detecting the open ports (or the filtered ports) that are running services and the underlying protocols, the supplied credentials for each protocol are tested. In this way, the scanner detects the OS and performs the following scans:

    Scan toProtocol used
    Verify test credentialsSMB, WMI, SSH, SNMP
    Detect WMI user nameWMI, SMB
    Detect Mac addressWMI, SNMP, SSH
    Detect device typeWMI
    Detect virtual devicesVMware vSphere, Hyper-V

  4. After the credentials are tested for each known open port, more information about OS is fetched by using the SSH, WMI, SMB, or SNMP protocol.
  5. After the device is detected, software inventory is obtained by using the SSH (Linux, UNIX) or SMB or WMI (Windows) protocol and hardware inventory is obtained by using the SSH or WMI protocol.
  6. After fetching software and hardware details, the scanner writes the scan log and device inventory details to the Remedyforce Discovery Server by using the SNMP protocol.

Related topics

Supported discovery licenses and features

Enabling and configuring agentless discovery

Remedyforce Discovery

Was this page helpful? Yes No Submitting... Thank you

Comments