---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Set up Discovery without Guided Setup

# Set up Discovery without Guided Setup {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

If you are not using Guided Setup, you must perform several configuration steps
manually to activate the application, set up the MID Server, and then set up
Discovery.

## Before you begin

* Grant Discovery role: Verify that users who are expected to configure and execute Discovery in your network have the discovery_admin role. This role grants access to the tables in the Discovery application.
* Designate a computer to host the MID Server.
* Gather the login credentials that the MID server must use to access the devices it is expected to discover.
* Determine which IP addresses Discovery must scan. In a highly complex network, group IP ranges into a range sets, which are reusable for different schedules. Discovery does not scan anything outside of these ranges.
{#t_ConfigureDiscovery__ul_dfs_n5m_wbb}Role required: discovery_admin

## About this task

## Procedure

1. Install one or more MID Servers on physical or virtual servers that meet the [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) and configure them to communicate with the appropriate ServiceNow instance.  
   Install at least two MID Servers at first and assign them to different schedules and IP ranges to help complete discoveries quicker. Starting with the Istanbul release, you must make sure that the MID Server is assigned the Discovery application or the ALL application.
2. Ensure MID Server connectivity by navigating to DiscoveryMID Servers.  
   If the MID Servers are configured properly, they appear in the list of MID Servers.
3. If a MID Server does not appear as a choice in the instance, perform the following checks:  
   * Ensure that the URL in the Configuration Parameters related list provided is correct.
   * If the MID Server is installed on Windows, make sure the ServiceNow MID Server service is configured properly with the correct logon credentials and is running.
   * Check the MID Server log for errors.
     * On the instance, navigate to DiscoveryMID Servers\[MID Server\]Logs.
     * On the MID Server host, navigate to the agent\\logs\\agent0.log0 directory.
     {#t_ConfigureDiscovery__ul_ulg_qtw_wp}
   * If Basic Authentication is enabled, a user name and password must be provided.
   * The MID Server might not have outbound access on port 443 (SSL) or a proxy server might be preventing TCP communication to the instance.
   * Make sure that no firewalls are blocking communication between the MID Server and the instance.
   {#t_ConfigureDiscovery__ul_ekf_mtw_wp}
4. [Set the
   credentials](https://www.servicenow.com/docs/access?context=t_CreateCredential&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) on the instance for all the computers, printers, and network gear in your environment.  
   Credentials for Windows devices (using the WMI protocol) are provided by the logon configured for the MID Server service on the Windows server host. Credentials for UNIX, vCenter, and SNMP must be configured on the instance. Discovery automatically determines which credentials work for a particular computer or device.
5. Define and run [Discovery
   schedules](https://servicenow-prod.fluidtopics.net/CIQEq9XeYjrEAd3sKWHEVg "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.").  
   The Discovery Schedule
   is the control point for running discoveries. The schedule controls when Discovery runs,
   defines the MID Server to use, the type of Discovery that should
   run, and the IP addresses to query. Create as many schedules as necessary,
   using different types of discoveries, and configure them to run at any time.
   Let Discovery run on
   its configured schedule or manually execute Discovery at any time.
   You can set up a single schedule for the entire network or separate
   schedules for each location or VLAN. If you do not know the IP address to
   scan in your network, run a Network Discovery first to
   discover the IP networks. Once discovered, you can convert these networks
   into IP address range sets that you use in a Discovery
   Schedule.  
   Note:  
   For advanced discoveries, such as those requiring load balancing or scanning across multiple domains, use Discovery [behaviors](https://servicenow-prod.fluidtopics.net/aa~GVD6Ga6IiFNS8fQpOjA "Discovery behaviors determine the probes that Shazzam launches, and from which MID Servers these probes are launched.").
6. Validate the Discovery results.  
   Open the ECC queue and analyze the XML payload, then check the [Discovery log](https://servicenow-prod.fluidtopics.net/ao5OrQtRxbDaPsjhkL2QeA#r_DiscoveryLog "The system collects logs to reflect the activity that takes place during a horizontal discovery based on both patterns and probes. Use the logs to fine-tune or troubleshoot the discovery process."). For more information, refer to the section for validating results in [Schedule a horizontal discovery](https://servicenow-prod.fluidtopics.net/CIQEq9XeYjrEAd3sKWHEVg "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.").

*[\>]: and then