Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
How a mid server is selected for Orchestration activities - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • How a mid server is selected for Orchestration activities
KB0693456

How a mid server is selected for Orchestration activities


2452 Views Last updated : Sep 27, 2022 public Copy Permalink
KB Summary by Now Assist

Issue

This explains the Orchestration mid server selection procedure.

Procedure

Orchestration mid server selection happens based on multiple factors like application, IP ranges, capabilities, operational state, validated or not. Below are the steps to determine mid server selection for orchestration activities. At each stage, mid servers that won't satisfy the condition would be filtered out. At the end, a random mid server or a default mid server would be selected.

  1. Validated Mid Servers (Is it a valid MID) --> This process start with all the mid servers that are validated.
  2. Orchestration application (Under MID applications section) --> This list would be further filter down based on "Orchestration" application or ALL application under MID Server supported applications section.
  3. IP Ranges --> Then IP ranges be checked to for this destination IP.
  4. Capability --> Based on the orchestration activity capability ( SSH, PowerShell, WMI, etc..), all the mid servers would be filtered further.
  5. At this stage, there may be multiple mid servers or none. If we have multiple, this list would be further filtered based on the below priority order.
    • Up, Degraded, down. Each priority order (above) be checked for all the mid servers. If any priority order finds a mid server, further priority order check would be skipped.
    • To this mid server list, default mid server would also be added to check the operation status. As soon as we find mid servers, a random mid server will be selected for further activities.
    • If no mid server is identified, orchestration uses the default mid server.

 

 

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.