MID Server release notes ServiceNow® MID Server enhancements and updates in the Istanbul release. Istanbul upgrade information For details on the following upgrade tasks, see MID Server upgrade to the Istanbul release. To ensure that your MID Servers can upgrade successfully, run a series of manual tests for free disk space, access to the download server, and file permissions on the MID Server host. Important: After all MID Servers have been upgraded to Geneva or higher, complete the post-upgrade steps listed in the Workaround section of KB0597396. This release introduces features such as application assignment and changes the way various applications select MID Servers. For information on how the upgrade handles defined capabilities, Discovery schedules, IP ranges you have configured, and default MID Servers for Orchestration, see the reference above. In Istanbul, the MID Server can run SSH commands using either the J2SSH client or the proprietary ServiceNow® SNCSSH client. When you upgrade from Dublin or earlier, the MID Server property that controls the SSH client selection is not active in your upgraded instance, and the MID Server will use the J2SSH client by default. To enable the SNCSSH client, you must add the mid.property.ssh.use_snc MID Server property and set it to true. Instances upgraded from Eureka or later have the SNCSSH client enabled by default, and no configuration is required. For details, see MID Server properties. New in the Istanbul release MID Server pause The MID Server can be temporarily paused to prevent it from polling the ECC Queue for work and from sending Discovery results back to the instance. MID Server upgrade The MID Server is put into Upgrading status while an upgrade is being performed. This status is similar to the Pause state. If an upgrade from one major version to another fails, the MID Server is put into Upgrade Failed status. MID Server version and user compatibility The MID Server list view and the MID Server form provide indicators to show you if the version of the MID Server is compatible with the instance. The indicators also show you if the MID Server user is configured correctly. Privileged commands The dzdo privileged command is supported. You can add new privileged commands to the Privileged Command [privileged_command] table and configure the MID Server to use them in a predefined order. You can create a special configuration for the pbrun privileged command that allows it to run as a profile. Guided setup A guided setup system helps you download a MID Server and configure it to work with your instance, using a series of easy-to-follow panels. To get started, navigate to ITOM Guided Setup > MID Server. Credentials debug A new section of the ECC queue payload is available to help troubleshoot issues with credentials: <credentials_debug>. Changed in this release MID Server selection criteria: In addition to IP ranges and capabilities, MID Servers can specify an additional selection criterion: supported applications. The supported application refers to the application that is allowed to use the MID Server, such as Orchestration or Service Analytics. Each application uses this supported application criterion differently. You can also specify initial selection criteria on a MID Server when you validate it. MID Server status: These types of status are new: Upgrading, Upgrade Failed, Paused, Validating, Validation failed.