---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Validate the MID Server

# Validate the MID Server {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

You must manually validate the MID Server after it is installed to enable it to execute automation tasks. You can invalidate a MID Server you suspect has been compromised to prevent it from accessing automation credentials in the instance or executing outbound ECC probes.{#t_ValidateAMIDServer__ph_ValidationIntro}

## Vorbereitungen

Role required: agent_admin, admin  

|-|
|   |
[ ]

{#t_ValidateAMIDServer__table_nds_2s4_nhb}

Make sure that the [MID Server
version](https://servicenow-prod.fluidtopics.net/YkkO5zZK3HdVs48NzJuenQ "The Management, Instrumentation, and Discovery (MID) Server is a Java application that runs as a Windows service or UNIX daemon on a server in your local network. The ServiceNow MID Server enables communication and the movement of data between a ServiceNow instance and external applications, data sources, and services.") is compatible with the instance.

## Warum und wann dieser Vorgang ausgeführt wird

Validation restricts access to automation credentials to trusted MID servers only.  
When you validate a MID Server, you specify the capabilities it can use, the applications that use it, and the IP ranges it is allowed to explore. You will be prompted to set the initial selection criteria when you validate MID Servers that do not already have capabilities, applications, or IP ranges already configured. You do not have to set the initial selection criteria to actually validate the MID Server. See [MID Server selection](https://servicenow-prod.fluidtopics.net/mrx4cQ9hAtMgiweuFR2raw "You can configure MID Server selection by application, IP address ranges, network capability, or behavior. Specific MID Servers can be assigned to particular tasks, or the MID Server can be selected automatically. MID Servers can use domain separation to limit the scope of discoveries and event management.") for more information on capabilities, applications, and IP ranges.  
Hinweis:  
When you upgrade, MID Servers that are already configured in your instance are automatically validated. This prevents the interruption of automation tasks that MID Servers might be performing. See [MID Server upgrades](https://servicenow-prod.fluidtopics.net/FHThP3zPMJs8jJC1nxVqog "Upgrade MID Servers manually, or automatically through the instance. MID Server automatic upgrade is triggered when the instance upgrades and the MID Server no longer has the same version. The new MID Server package is downloaded from install.service-now.com, replaces the old one, and the MID Server starts with the new version.") for more information.

## Prozedur

1. Navigate to AllMID ServerServers. {#t_ValidateAMIDServer__s_Step2}
{#t_ValidateAMIDServer__s_Step2}
2. Open the new MID Server you created from the list of MID Servers. {#t_ValidateAMIDServer__s_Step3}
{#t_ValidateAMIDServer__s_Step3}
3. Under Related Links click Validate.  
   The Set Initial Selection Criteria window appears if there are no records in the Supported Applications, IP Ranges, or Capabilities related lists. {#t_ValidateAMIDServer__cmd_Step4}
4. On the Set Initial Selection Criteria window, use the switches to enable or disable selection criteria for this MID Server:  
   * Allow ALL capabilities: Allow all capabilities for Orchestration and Event Management to use this MID Server.  
     Hinweis:  
     Service Mapping and Event Management alert aggregation and RCA, which used capabilities in previous releases, rely on the application for MID Server selection.
   * Allow ALL applications: Allow all applications that use MID Servers to use this MID Server.
   * Allow ALL IP ranges: Make all IP ranges valid for this MID Server, meaning that it can target any IP address.

   {#t_ValidateAMIDServer__ul_psl_4hp_tw}  
   Abbildung : 1. Setting initial selection criteria

   If you click Cancel, the validation continues but none
   of the capabilities, applications, or IP ranges are added.
5. Click OK.  
   The Validated field on the dashboard is set to
   Validating, and then set to
   Yes after the validation completes.
6. To invalidate a MID Server, open the record for the MID Server you suspect has a security issue.
7. Under Related Links, click Invalidate.  
   Invalidating a MID Server forces it to clear its memory and restart. The MID Server generates a new keypair on restart.

## Nächste Maßnahme

[Test
network connectivity](https://servicenow-prod.fluidtopics.net/p3M_8Z__2OtghiL5qiflyw "Confirm that the MID Server host is able to communicate with the instance. Resolve any issues with the network connectivity such as conflicts with firewalls, access control lists, and routing errors. Successful communication is necessary for automatic upgrades.") to ensure that the MID Server can upgrade
automatically.
**Zugehörige Tasks**   

* [Rekey a MID Server](https://servicenow-prod.fluidtopics.net/pL97YclPNbf5hsjR6JhaEA "Rekey a MID Server to generate a new private key. Private keys are used to decrypt automation credentials, so that MID Servers can transmit information securely. Key pairs are initially generated when a MID Server is validated, and MID Servers should be rekeyed periodically to meet security requirements.")