Difference between revisions of "Discovery Job"

From Hornbill
Jump to navigation Jump to search
m (Rickyf moved page Discover Job to Discovery Job: Incorrect page name)
(One intermediate revision by the same user not shown)
Line 4: Line 4:
 
|style="width:73%"|
 
|style="width:73%"|
 
==Introduction==
 
==Introduction==
A discovery is run on a designated SIS. The account given within the Admin Credentials will then perform a Discovery based on the method selected. Once a machine is found, the machine will be pinged and then the credentials are further used (using WMI (DCOM/WinRM)) to confirm access to the machine and obtain extra information (e.g. hardware, operating system, installed programs; using EspSisDiscovery)<br><br><br><br><br>
+
A Discovery is executed from a designated SIS server using Admin Credentials provided via the Hornbill KeySafe, using one of the various methods provided. Once all the devices have been discovered, dependant on configuration, a ping request will also be sent to each device.  The Admin Credentials are further used for access to each devices Inventory (e.g. hardware, operating system, installed programs) using WMI via DCOM or WinRM.  On successful completion, the device details will be stored within the ITOM Inventory and can be identified as managed and the Inventory viewed.
 
|style="width:5%"|
 
|style="width:5%"|
 
|
 
|

Revision as of 01:33, 27 March 2020

Home > ITOM > Create New Job > Discovery Job Index

Introduction

A Discovery is executed from a designated SIS server using Admin Credentials provided via the Hornbill KeySafe, using one of the various methods provided. Once all the devices have been discovered, dependant on configuration, a ping request will also be sent to each device. The Admin Credentials are further used for access to each devices Inventory (e.g. hardware, operating system, installed programs) using WMI via DCOM or WinRM. On successful completion, the device details will be stored within the ITOM Inventory and can be identified as managed and the Inventory viewed.

Related Articles

Discovery Job Properties

ITOM Add Discovery Job
  • Name
Name given to identify this Discovery Job
  • Site Target [Group / Server ]
whether the job needs to run on a SIS Group or on a single SIS/Managed CI
  • Protocol
The Discovery process once a computer has been identified as a Windows device, Windows Management Instrumentation (WMI) is used to retrieve Windows Information that is used to populate the Inventory. The discovery Job will always be executed directly from the SIS server and thus needs to remotely connect with any computers that it discovers to retrieve their details. There are two methods supported, that can be utilised:
  • WinRm
Provides secure and firewall-friendly communications, in order to access WMI. This feature is supported on Windows 2008R2 and later, Windows 7 and later and later.
  • DCOM
Communication relies on Remote Procedure Calls and can be tricky to configure over firewalls.
  • Discovery Mode
The Discover Mode dictates the method that identifies devices on the Network. Each Mode will have specific settings; these will be visible in the Discover Mode Settings. It is only possible to have a single mode per Job use of multiple modes, will require the creation of multiple Jobs.
  • Ping Check Settings
  • Ping check Discovered
[Yes / No] Check that the discovered machine is pinged - if ICMP is disabled or firewalled, then select "No"
  • Timeout
  • Hop Count

Job Details

Once the job has been created details will be displayed showing information relating to the job including the status of the job. Monitoring, Console and Debug Logging are provided for monitoring the progress and to aid with troubleshooting failures.

  • Summary
Shows the current status of the job and its name along with who created it and when
  • Discovery Options
Displays details of the options used by the discovery process, this will differ depending on the discovery mode that is being used
  • Target Information
Provides details of the SIS server that will facilitate the job, target machine and the security keys used
  • Execution Details
The execution details show when the job was started and completed along with any result code

Creating a Job

  1. Select the Create New button
  2. Select Discover Job
  3. Enter Name to identify the Job
  4. Select an SIS server:
    This can be a single Server or a Group
  5. Select the required Protocol
  6. Select the required Discovery Mode
  7. Enter the relevant Discovery Mode Settings
  8. Click Create button

Monitor

The Monitor frame provides information relating to the execution of the job; the details shown will be dependant on the method of discovery used.

JobMonitorADDiscovery.png

The above example shows that the discovery has started and has initiated two processes, Standalone (EspSiSExec.exe) and a Payload (ESPSisDiscovery.exe), on the SIS server.

All console output from the process is output, and confirmation of successful completion or failure will be output.

Console Output

The Console Output is accessible once the job has been completed and will contain only the output produced by the payload, including any error messages.

JobConsoleADDiscovery.png

Debug Log

In cases where the Discovery may have failed or completed incorrectly, the Debug log can be used to review any errors and other technical information.

JobDebugLogDiscovery.png

The Log provides three sections:

  • Full
Full debug log information
  • Standard
Information log entries
  • Problem
Warning and Error, entries that may identify portential problems
Information
The sections output will depend on the job, and thus some sections may not be available