Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Introducing the MID Server

Log in to subscribe to topics and get notified when content changes.

Introducing the MID Server

The MID Server facilitates communication and movement of data between the ServiceNow platform and external applications, data sources, and services.

The Management, Instrumentation, and Discovery (MID) Server is a Java application that runs as a Windows service or UNIX daemon. The MID Server performs the following tasks:
  • Communicates securely with the ServiceNow instance to determine what Discovery probes to run.
  • Runs Discovery probes on the local network to gather data on network devices
  • Sends Discovery probe results back to the ServiceNow instance for processing
Note: MID Server communications are initiated inside the enterprise's firewall and therefore do not require any special firewall rules or VPNs.
The MID Server is used by the following applications:
  • Discovery
  • Orchestration
  • Import Sets
  • Altiris
  • Microsoft SMS/SCCM
  • Avocent LANDesk
  • HP OpenView Operations
  • Microsoft System Center Operations Manager (SCOM)
  • Borland Starteam Integration
  • Microsoft MIIS
  • Service Assurance

MID Server Records that can not be altered

The following records can not be modified or deleted.

Table 1. MID Server records that can not be altered
Table Record
Public Page [sys_public] InstanceInfo
Scripted Web Service [sys_web_service]
  • InstanceInfo
  • GetMIDInfo
  • MIDAssignedPackages
  • MIDFieldForFileProvider
  • MIDFileSyncSnapshot
  • MIDServerCheck
  • MIDServerFileProvider