---
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


---

# Configure a default MID Server for Service Mapping for upgraded deployments

# Configure a default MID Server for
Service Mapping for upgraded
deployments {#ariaid-title1}

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

In deployments upgraded to Istanbul or earlier, Service Mapping uses the default MID
Server when it cannot find a MID Server with the matching IP range. Configuring a default
MID Server improves the discovery process.

## Before you begin

Role required: service_mapping_admin

Perform this procedure only for deployments upgraded to
Istanbul or earlier. For fresh installs, perform [Configure a default MID Server for each application](https://www.servicenow.com/docs/access?context=t_SpecifyMIDServerApplications&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

Ensure that you know the name of the MID Server you want to configure as
the default MID Server for Service Mapping.

## About this task

In upgraded deployments, Service Mapping selects a MID Server using a legacy algorithm:

* Service Mapping chooses the MID Server whose application criteria is set to ServiceMapping or to ALL.
* By default, Service Mapping selects the MID Server whose IP range matches the IP in the discovery request.
* If Service Mapping cannot find a MID Server with the matching IP range and matching application, it assigns the discovery request to the default MID Server.
* If there is no default MID Server and none of the MID Servers have IP ranges configured for them, Service Mapping uses a random MID Server.
* If there is no default MID Server and no IP range matches the IP in the discovery request, Service Mapping cannot start the discovery process.
{#config-default-mid-for-sm__ul_hfy_fns_xw}

## Procedure

1. Navigate to System Properties by entering <kbd class="ph userinput">sys_properties.list</kbd> in the navigation filter.
2. Click New.
3. Configure values for the new property as follows:  
   {#config-default-mid-for-sm__table_gc3_qsf_vv__entry__2}

   | Property | Description |
   |-|-|
   | Name | Enter <kbd class="ph userinput">mid.server.sm_default</kbd>. |
   | Description | Enter a free text description of the use of this MID Server. |
   | Type | Select string. |
   | Value | Enter the name of the MID Server you want to configure as the default for Service Mapping. |
   [ ]

   {#config-default-mid-for-sm__table_gc3_qsf_vv}
4. Click Update.
**Related concepts**   

* [MID Server configuration for Service Mapping](https://servicenow-prod.fluidtopics.net/zWlPCWfb7dE865TT7wtHHA "Configure Service Mapping and MID Servers to work together.")