Prepare the network for MID Servers to connect with the instance and access the
download site. The network must be prepared before installing or configuring the MID Server.
If computers or devices have additional security measures, that security may interfere with
MID Servers on those systems.
The MID Server host computer
must have access to the ServiceNow download site at
install.service-now.com to upgrade automatically. If you have a
self-hosted ServiceNow environment that blocks access to the download site, you must
import the MID Server installer package into your MID Server hosts manually. For
instructions, see KB0760123 in the Self-Hosted knowledge base.
Firewalls and proxy configurations may block calls to the OCSP
Entrust server, which prevents the MID Server from working. You may need to change your
firewall permissions so the OCSP traffic to go through properly. For more information and
resolutions, see the HI Knowledge Base article [KB0813636].The host machine must have these network privileges:
- Firewall access: Configure any firewalls between the MID Server and the
target devices to allow a connection. If your network uses a DMZ, and if
your network security protocols limit port access from within the network to
the DMZ, you might have to deploy a MID Server to a machine within the DMZ
to probe the devices there.
- Network access: Configure target devices to allow the MID Server probe to
connect. If network security prevents you from configuring new machines that
can connect to the targets, install the MID Server on an existing machine
with connection privileges.
- Network account: Install the MID Server with the proper account, either
local or domain administrator.
Additionally, for the MID Server to access your
ServiceNow instance, satisfy these prerequisites:
- Network access to the ServiceNow instance: Configure
the network that the MID Server uses to allow traffic over TCP port
443.
- A MID user: Create a ServiceNow user record for the
MID Server to use. This user record must have the mid_server and
import_admin roles.
Note: Verify that the baseline public page
InstanceInfo is active for the MID Server to connect
to the instance.