Default language.

Enabling and configuring agentless discovery


License Required

To enable and configure Discovery in Remedyforce, you require one of the following licenses:

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

You can either enable  Discovery or integrate with BMC Client Management. Proceed with this section if you have decided to enable Discovery in your organization.

Enabling and configuring Discovery in  is a multiphase process. The following figure provides an overview of the procedures that you must perform to enable and configure Discovery in your organization.

discovery_process.gif

 

For more information, refer the following topics:

Procedure 1: Enable Discovery in your organization

discovery_process1.gif

Ensure that you have disabled the BMC Client Management integration under Integrations > BMC Client Management Integration Settings page else you will not see the Discovery Setup & Configuration option.

  1. Click the Remedyforce Administration tab.
  2. On the Home tab, from the Configure CMDB 2.0 tile click Discovery Setup & Configuration.
  3. Select the Enable Remedyforce Discovery check box.
  4. Click Save save_icon.gif.

Back to top

Procedure 2: Request Remedyforce Discovery Server

discovery_process2.gif

The Remedyforce Discovery Server is required to establish communication between a scanner and Remedyforce.

  1. To ensure that you receive all email notification, navigate to the required path:
    • For Salesforce Classic, go to Setup > Administer > Email Administration > Deliverability.
    • For Salesforce Lightning, go to Setup > Administration > Email > Deliverability.
  2. On the Discovery Setup & Configuration page, click the highlighted link to create a remote site.
    The  BMC_Remedyforce_Discovery_Prov_Server remote site is created.
    Disco_proc_2.png
  1. To enable secured communication with the server, set up a password in the Enter Password and Confirm Password fields.
    Your username is the Salesforce organization ID of your Salesforce organization that is already displayed on the page.
    If you want to change your password, click Change Password. If you have forgotten your password, click the Reset Password link and an email is sent to your registered email address.
  1. To request for the Remedyforce Discovery Server, click the Request Discovery Server button.

    Important

    After you click the Request Discovery Server button, BMC recommends that you do not move away from the page until your request is processing.

    The Remedyforce Discovery Server is unique for your Salesforce organization. When the server is created for your organization, the screen refreshes and the details to install scanners are displayed on the page. An email message is also sent to your registered email address with the server URL and download URLs for scanner installation.

    image2020-6-11_1-46-45.png
    If your request for the Remedyforce Discovery Server fails, request again after some time. 

    Note

    When the Remedyforce Discovery Server is created for you, a scheduled job (Remedyforce - BCM Processor (datetime)) runs in your Salesforce organization to keep your server alive. Ensure that you do not delete this job. 

  2. To enable communication with the Discovery Server, create second remote site setting by clicking the link on the page.
    The license information is not provided on the page until you create this remote site setting.
    Once you have configured the remote links, you must not delete these links. Also, note that the Remote Site URL will not change, though the port number in the URL can change. Refer the following image.

    image_remote_sites.png

  3. Open the ports on your network firewall in outbound way to enable communication with the Discovery Server, BMC Client Management Console, and scanner.

The ports that you must open are displayed on the page. You require the following ports:

    • Integration port—To download the scanner installer that is required to communicate with Discovery Server from .
    • High Priority port—To communicate with the Discovery Server for transferring data (in all licenses) and launching BMC Client Management Console (in the premium licenses).
    • Low Priority port—To establish connection with the Discovery Server.

These are TCP ports. These ports handle HTTPS connections and internal custom protocols to communicate with the Discovery Server. These ports must be opened for outbound connections on all devices that are running an agent (scanners for Base license; relays and scanners for Premium licenses) that directly communicate with the Discovery Server.

Note

  • To enable discovery and scan, ensure that the protocols are enabled and the default ports of these protocols are also opened on the devices to be discovered.
  • Also note that you might have to enable communication with the Discovery server in case your organization's network is under firewall by unblocking the Discovery server IP address. The Discovery server is on the public network and you can get its IP address by using the alias name in the ping request. To find the alias name of the Discovery server in your organization, refer the blurred part in the image provided in Step 4.

Back to top

Procedure 3: Install scanners

discovery_process3.gif

After you identify a device to be used as a scanner, use the URLs to install scanners that are available on the Scanner Roll-out tab. URLs for the Windows (32 and 64 bit) and Linux (32 and 64 bit) operating systems are provided. After installation, these devices are displayed in the Scanner Details list on the Scan Configurations tab. After installation, the "BMC Client Management Agent" service runs on the scanner device.

image2020-6-11_1-57-21.png

You can run one executable file on multiple devices that have the same configuration. The maximum number of installers that you can install depends on your Remedyforce Discovery license. For more information, see Supported-discovery-licenses-and-features.

Note

If you exceed the limit of maximum number of installers, the scanner is not displayed in the  Scanner Details  list even if the installation is successful.


Operating system requirements for a scanner

For operating system requirements, see Software requirements

To install scanners

  1. On the scanner device, in a web browser, open the URL to the scanner installer file that is provided on the Scanner Roll-out  tab on the  Remedyforce Administration > Configure CMDB 2.0 > Discovery Setup & Configuration page.
    image2020-6-11_1-57-51.png
  2. Enter your Salesforce organization ID as user name and your Remedyforce Discovery Server password to access the installer.
    The installer is downloaded on your device. If you have forgotten your Discovery Server password, click Reset Password link on the page. An email is sent to your registered email address.
  3. Double-click the installer and run the installation.
  4. After the installation is complete, on the Remedyforce Administration > Configure CMDB 2.0 > Discovery Setup & Configuration  page, click Refresh and the device is displayed in Scanner List on the Scan Configurations tab.
    You might notice a delay in getting the installed scanner in Scanner List.
    image2020-6-11_2-1-54.png
  5. To ensure that a scanner is able to communicate with the Discovery Server, open the port 1610 in your firewall on the scanner. 

    Note that, if you no longer want to use a device as a scanner, you can uninstall the scanner.

    Tip

    Under the Scan Configurations tab, once you click the Refresh button, a request is initiated to fetch the updated execution status of the scanner list. This status is fetched from the BCM server to be synced at the Remedyforce end. But since the page gets auto refreshed every three minutes, the synced status is displayed on the UI in its next refresh cycle (which may take around three to six minutes).

Procedure 4: Configure scans

discovery_process4.gif

After installing scanners, configure the following for each scanner:

  • Protocols that a scanner will use to access and discover devices on your network. 
  • IP ranges in which the scanner will discover devices. You can also specify the IP ranges that must be excluded from discovery.
  • Schedule for scanners to discover. For example, say you want to discover devices every Monday, 9:00 A.M.

Before you begin

Gather the following information to configure scans:

  • Type of devices that you want to discover.
  • The protocols that you want to configure to communicate with these devices.
    • Windows remotely (via WMI, SMB)
    • Unix, Linux, or Mac OS
    • Printers, routers, and switches (via SNMP)
    • Hypervisors of type ESX, ESXi (via SOAP)
    • Hypervisors of type Hyper-V (via WMI)
  • Administrative credentials to access devices on your network.
  • List of IP ranges or addresses of devices that you want to discover and do not want to discover.
  • Schedule to discover devices.

To configure scans

  1. On the Discovery & Configuration page, click the Scan Configurations tab.
  2. From the Scanner Details list, select one of the available scanner for which you want to configure a scan.
  3. In the Scan Configurations section, select the check box for the protocols that you want to use to access and scan devices on your network.
    For example, you want to discover Windows computer systems by using WMI, select the check box for Windows remotely (via WMI, SMB, etc.).
  4. In the Credentials for section, click RBA_Add.png.
  5. In the Add user credentials window, enter the administrative user name and password to access devices by using this protocol, and click Save.
    image2020-6-16_10-4-15.png
    You can enter multiple credentials to access a device. Scanner accesses a device using one credential at a time beginning from top and moves on until success.
    The user name must be in one of the following formats: 
    • if you are on a domain: <domain name>/<user name>
    • if you are not on a domain: <user name>
  6. In the Target List section, click RBA_Add.png.
  7. In the Add Target List window, enter the device names that you want to discover and the IP addresses or device names of the devices that you do not want to discover.
    image2020-6-16_10-4-54.png
    The format of the device name can be any or combination of the following:
    • Long or short network name (such as, scotty or scotty.organization_name.com)
    • IP addresses (such as, 159.125.5.10)
    • Comma-separated list of names or IP addresses or IP address ranges (such as, scotty, 10.125.5.10, 192.168.4.34-192.168.4.45)
    • Classless inter-domain routing (CIDR) notation (such as, 192.9.205.22/18 or 2001:db8:85a3::8a2e:370:152/896)

      Note

      The address x.x.x.255 is a broadcast IP address and it cannot be scanned. Therefore, do not enter this IP address. 

      Do not press Enter while entering the target list members.

  8. In the Scan Schedule section, configure the time when scanner must discover devices in your network.
    You can configure scan to run immediately or run at specified intervals. 
    image2020-6-12_9-15-14.png

    To stop scanning, select Do not scan. If a scan is being executed, successive scans will stop after completing the current running scan. 

    Note

    Time is saved in the time zone of the logged on user. When the scanner receives the scan configuration, this time is converted to the time zone of the scanner and the scan is performed at the converted time.

    To view details of the scan progress and its current status, click View Details in the Scan Details column of the Scanner Details section. For more information, see Verifying-scan-details.

  9. Click Save.

    Note

    If you have Remedyforce Client Management - Premium or Premium Plus license, you can create multiple configurations for a scanner in the BMC Client Management Console. To access the BMC Client Management Console, navigate to the Remedyforce CMDB  tab and click client_management_console_icon.gif. In the BMC Client Management Authentication dialog box, enter your BMC Client Management credentials. The BMC Client Management Authentication dialog box is shown only once. For information about creating multiple configurations, see The referenced document [xwiki:More-Products.RemedyForce.BMC-Helix-Remedyforce.remforce202501._inclusionsLibrary_remforce._remforce_NW_LinksLibrary.WebHome] was not found.  in the  BMC Client Management  documentation. To configure scans in BMC Client Management Console, the scan capability must be enabled for your BMC Client Management user. 

    If you create or update a scan configuration from BMC Client Management Console, you can update such configurations from BMC Client Management only.

Back to top

Procedure 5: Configure the import settings

discovery_process5.gif

You can import the discovered devices as configuration items (CIs) or assets to Remedyforce CMDB. You can import discovered device details to the following CMDB class types:

  • Computer System
  • LAN Endpoint
  • Operating System
  • Processor

While importing, the following relationships are created among the discovered devices:

  • Computer System–LAN Endpoint
  • Computer System–Operating System
  • Computer System–Processor

Existing records in your CMDB are retained as is.

To import discovered device details to Remedyforce CMDB

Note

This built-in import method is applicable only when you enable Remedyforce Discovery as given in Procedure 1: Enable Discovery in your organization. You must not use the Pentaho package for this integration as this path does not support it. The Pentaho packages associated with BMC Client Management are applicable only in the older integration method.

For more information about the older integration method, see Importing-data-from-BMC-Client-Management-by-accessing-the-database.

  1. On the Discovery & Configuration page, click the Import Configurations tab. 
    While importing instances of the Computer System class, you can map the Primary Client field. For more information, see Mapping the Primary Client field.
  2. Select the class types.
    The Computer System class is selected by default and you cannot clear its selection. This class stores devices such as desktops, laptops, and servers. When you click the down arrow with a class name, the field mapping table is displayed. Source fields belong to the Remedyforce Discovery Server. For certain field values, the if-else function is used. For example, the value of Is Virtual field of the Base Element object is "No" if the VIRTUALSYSTEMTYPE field value of the source is "notvirtual". For a complete list of field mappings, see Field mappings between Remedyforce and Remedyforce Discovery.

    image2020-6-12_9-17-54.png
     
  3. In the Job Schedule section, specify the schedule to import discovered device details, and click the Start button.
    For example, to import discovered device details once in two days, specify 48 in the Hours field. When you specify import schedule, BMC recommends you to consider the scan schedule. For example, say your scanners are configured to scan every Monday. You might want to import discovered devices after every 7 days starting a Tuesday. In this case, enter 168 in the Hours field.
  4. Click Save.

    Note

    • The Last successful import at field shows the time when the records were last imported (inserted or updated). The field keeps showing the same date until new records are imported by the running job.
    • If you want to generate a report on imported records, use the Assembly ID  field. The value of the Assembly ID field of discovered and imported devices is prefixed with " AC:CS ".

    For the imported records, the Source field is set to Remedyforce Discovery. You can use the Source field to generate reports. The same can be done even when you enable and configure reconciliation. 

Back to top

Mapping the Primary Client field

While importing instances of the Computer System class through Remedyforce Discovery, you can populate the Primary Client field by including the primary client mapping for certain instances based on primary capabilities.

Notes

  • The Integration User Info field is provided for mapping the Primary Client field values. This field is visible to both fresh install users on Remedyforce 20.20.01 and users upgrading to 20.20.01. Note that in case there is an existing field that can be used for Primary Client mapping, you must store the field's API name in the IntegrationUserInfo custom setting.  
  • To populate the primary client (Salesforce user), the primary user must be mapped to a user name as discovered by Remedyforce Discovery.

To map the Primary Client field

The following table describes the primary client mapping process. 

Step

Description

Step 1: (Prerequisite) Populating the User object

Before importing the instances of the Computer System class from Remedyforce Discovery, perform the following steps in Remedyforce:

  1. Go to Setup > Administer > Manage Users > Users.
    (For Salesforce Lightning, go to Setup > Administration > Users > Users).
  2. Click Edit for the user to be populated.
  3. Enter details in the Integration User Info field (for example, domain\username or username)
  4. Click Save.

    Note: You can either manually enter details in the Integration User Info field or import them using the Data Loader. However, if you have upgraded from earlier versions to  20.20.01, refer to the following information.

To map the primary client for existing instances in CMDB
  1. Click the Discovery Mapping tab.
    As per selected option, the Create New View or Edit form is displayed.
  2. From the Select Fields to Display section, add the Last Import and CMDB Class fields.
  3. Click the Go! tab.
  4. From the list view, search for Discovery Mapping records belonging to BMC_ComputerSystem CMDB class.
    (You can use the following query to search for Discovery Mapping records.

    SELECT BMCServiceDesk__LastImport__c FROM BMCServiceDesk__DiscoveryMapping__c WHERE BMCServiceDesk__FKCMDBClass__c = '** Id of BMC_ComputerSystem class **')
  5. Edit those records by clearing the values for Last Import field.
  6. Click Save.

Step 2: Importing configuration

After populating the User object, perform the Remedyforce Discovery import job from Remedyforce Administration > Configure CMDB 2.0 > Discovery Setup & Configuration > Import Configurations > BMC_ComputerSystem.

image2020-6-12_9-20-42.png

For field mapping details, see Field mappings between Remedyforce and Remedyforce Discovery.

Step 3: Including the Primary Client field mapping

(Optional)

You can include primary client mapping for the required instances of the Computer System class based on primary capabilities. Provide a semicolon separated list of primary capabilities that need to be included for the mapping (for example: WorkStation;Desktop;Laptop).
Note: The primary client values such as WorkStation;Desktop;Laptop are provided by default. Ensure that you enter the primary capabilities in English only.

image2020-6-12_9-22-57.png

Step 4: Populating the Primary Client field

Once you import the configurations on Remedyforce CMDB , the primary user or last logged in user are populated for the discovered devices.

In absence of the primary user, the Primary Client field is populated with the last logged in user. For any device, the PrimaryUserLogin field takes precedence over the LastLoggedInUser field.

Note: Ensure that you do not use any type of encryption on the Integration User Info field while mapping the Primary Client field.

Step 5: Viewing the report

A report is generated for the Computer System class indicating the instances for which the primary client is not populated, the user name for which the primary client is not populated, and so on.

To view the report, navigate to Reports > Remedyforce Reports > Missing Client in Discovered Instances.

Field mappings between Remedyforce and Remedyforce Discovery 

The following table lists the field mappings between Remedyforce and Remedyforce Discovery.

Class

Target field in Base Element

Source field in Remedyforce Discovery

BMC_ComputerSystem

 

Assembly ID

"AC:CS:-" + DEVICEID

 

Asset #

ASSETTAG

 

Description

if ( DESCRIPTION == " ) { OPERATINGSYTEMNAME } else { DESCRIPTION=OPERATINGSYSTEMNAME

 

Domain

DOMAIN

 

Host Name

HOSTNAME

 

Instance Name

DEVICENAME

 

Is Virtual

if( VIRTUALSYSTEMTYPE == 'notvirtual' ) { No } else { Yes }

 

LastScanDate

LASTUPDATE

 

Manufacturer Name

MANUFACTURERNAME

 

Model

MODELNAME

 

Primary Capability

DEVICETYPE

 

Primary Client

if(PRIMARYUSERLOGIN == ''){LASTLOGGEDINUSER}else{PRIMARYUSERLOGIN} 

 

Serial #

SERIALNUMBER

 

Short Description

if( SHORTDESCRIPTION == " ) { OPERATINGSYSTEMNAME } else {SHORTDESCRIPTION+OPERATINGSYSTEMNAME }

 

Token Id

TOKENID

 

Total Physical Memory

PHYSICALMEMORY

 

Unique CI Source ID

"AC:CS:-" + DEVICEID

 

Virtual System Type

VIRTUALSYSTEMTYPE

BMC_LANEndpoint

 

Address

IPADDRESS

 

Assembly ID

"AC:CS:-" + DEVICEID

 

Description

DESCRIPTION

 

Instance Name

If( NAME != " ) { NAME + "AC:LEP:-" + MACADDRESS } else { "AC:LEP:-" + MACADDRESS }

 

MAC Address

MACADDRESS

 

Short Description

SHORTDESCRIPTION

 

System Name

DEVICENAME

 

Token Id

NETWORKINTERFACEID

 

Unique CI Source ID

"AC:LEP:-" + MACADDRESS

BMC_OperatingSystem

 

Assembly ID

"AC:CS:-" + DEVICEID

 

Build Number

BUILDNUMBER

 

Description

if(OSNAME != '' && VERSIONNUMBER != 0){OSNAME+ VERSIONNUMBER}else if(OSNAME == '' && VersionNumber != 0){VERSIONNUMBER}else if(OSNAME != '' && VERSIONNUMBER == 0){OSNAME}

 

Instance Name

if ( OSNAME != " ) { OSNAME+ "AC:OS:-"+INVENTORYID } else { "AC:OS:-"+INVENTORYID }

 

Service Pack

SERVICEPACK

 

Short Description

if( SHORTDESCRIPTION == " ) { OSLANGUAGE } else { SHORTDESCRIPTION+OSLANGUAGE }

 

System Name

DEVICENAME

 

Token Id

INVENTORYID

 

Unique CI Source ID

"AC:OS:-" + INVENTORYID

 

Version Number 

VERSONNUMBER

BMC_Processor

 

Assembly ID

"AC:CS:-" + DEVICEID

 

Description

DESCRIPTION

 

Instance Name

NAME + "AC:PROC:"+ INVENTORYID

 

Manufacturer Name

MANUFACTURERNAME

 

Maximum Clock Speed

MAXCLOCKSPEED

 

Number of Logical Processors

NUMBEROFLOGICALPROCESSORS

 

Processor Family

PROCESSORFAMILY

 

Short Description

SHORTDESCRIPTION

 

System Name

DEVICENAME

 

Token Id

INVENTORYID

 

Unique CI Source ID

"AC:PROC:-" + INVENTORYID

Back to top

Related topics

How-discovery-works

Managing-discovered-devices

Troubleshooting-Remedyforce-CMDB-2-0-issues

Verifying-scan-details

Uninstalling-scannersSoftware requirements

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*