Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

MID Server release notes

MID Server release notes

MID Server product enhancements and updates in the Geneva release.

Geneva upgrade information

  • 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. For details, see Test the MID Server before an upgrade.
  • MID Servers that exist prior to upgrading to Geneva are automatically validated to avoid interrupting automation tasks that such servers may be performing.
    Important: After all MID Servers have been upgraded to Geneva or higher, complete the post-upgrade steps listed in the Workaround section of KB0597396.
  • In Geneva, 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 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.

Activation information

The MID Server application is downloadable from the ServiceNow service instance. The MID Server is upgraded automatically when you upgrade the instance. However, you can configure the version number to control MID Server upgrades. The MID Server is configured to check with the ServiceNow instance hourly to determine whether it needs to upgrade. This configurable behavior allows the MID Server to upgrade automatically when the instance upgrades.

New in the Geneva release

MID Server installer An installer allows for a clean and simple MID Server deployment on any supported operating system.
MID Server validation New MID Servers must be validated before they are permitted to access automation credentials or execute any outbound ECC probes. MID Servers that exist prior to upgrading to Geneva are automatically validated.
Enhanced logging framework A MID Server configuration parameter called mid.log.level provides four logging levels: DEBUG, INFO, WARN, and ERROR.
Windows Remote Management (WinRM) protocol A MID Server parameter,, allows you to select WinRM for device classification of Windows hosts.
CyberArk credential storage The MID Server now provides external credential storage through an integration with CyberArk.
Sudo alternatives For systems that cannot use sudo commands, you can configure the hosts in the network to use either the pbrun or pfexec privileged command.
JRE version 1.8 MID Server now installs with JRE 1.8 by default and installs that version on all upgraded MID Servers. Both the 32 bit and 64 bit MID Server use JRE 1.8.

Changed in the Geneva release

  • Configuring Unix shells for SSH: The mid.ssh.shells_supported MID Server parameter now enables users to edit the list and add any compatible bourne-shells.
  • MID Server ECC query interval: The query_backoff MID Server configuration parameter was removed and is not available to new or upgraded instances.
  • MID Server poll time: The polling interval in the mid.poll,time MID Server configuration parameter was changed from 15 seconds to 5 seconds.
  • Deprecated SCCM plugins: The following Microsoft SCCM plugins were deprecated:
    • Integration - Microsoft SCCM
    • Integration - Microsoft SCCM 2012
    • Integration - Microsoft SMS / SCCM 2.0

    These plugins will continue to function normally for instances upgraded to Geneva in which they are already activated.