From the ServiceNow Wiki on Discovery
The ServiceNow Discovery application finds computers and other devices connected to an enterprise's network. When Discovery finds a computer or device, it explores the device's configuration, provisioning, and current status and updates the CMDB accordingly.
On computer systems, Discovery also identifies the software that is running and any TCP connections between computer systems. Discovery creates all the relationships between computer systems (such as an application on one server that uses a database on another server).
#1 step in a ServiceNow Discovery implementation is gaining the credentials to run discovery on your network. Discovery applications are invasive and powerful, they do scan and obtain information all about your company infrastructure. This requires a lot of rights and access.
There is large ServiceNow Wiki article on this subject: Discovery Credentials I suggest reading that article and being very familiar with it before asking security for credentials. Going into those meetings without the proper information and stakeholder backing, will cause "difficulty" in obtaining the proper rights.
Security expects you know what you are doing in order to turn over that level of access. I suggest being prepared for those discussions.
Setting up Initial Discovery
I do not recommend just "turning on" ServiceNow Discovery when you get the credentials. Plan out what you want to discovery and test small range sets.
Some Setup Tasks I recommend
- Buy Discovery
- Activate Discovery Plugin
- Setup Credentials
- Setup Port Probes
- Deploy Midservers to access network
- Setup Discovery Schedule and Range Sets
- Try small range set for testing
Understanding the Discovery Process
Understanding the discovery lifecycle is important to understanding how it works and what to do if it doesn't or if you want to change it.
Port Scan Phase
- Discovery Schedule or Discover Now Runs
- Shazzam (Port Probes) Run. Checks for open ports for configured probes. If no ports are open for configured probes, discovery stops.
- Depending on what ports were open on Port Scan Phase, Probes will run. For example: WMI. If Windows WMI port was open, WMI Probe, Windows - Classify will run
- Sensor will return results. If there are bad credentials for for the Probe, discovery fails for this CI.
- CI is given a class and classified.
- If CI is Classified, Identify probes runs
- It is determined to update or insert a new CI
- All remaining probes run and sensors return results and update CI, related lists, and relationships.
Running a CMDB unchecked is not a good idea. If you are using ServiceNow Discovery, you should run reports to determine if the CMDB is accurate. Are you discovering the anticipated number of CIs? Many factors can decide whether you are discovering too much or too little.
I suggest setting periodic meetings to check CMDB data for accuracy and eliminate duplicates. One idea is to generate a monthly incident to make sure maintenance is completed.
Here is an article about how to build duplicate record reports: Duplicate Record Scripts
Here are some examples of other reports you can build (Some are included in the base system)
- Blank IP
- CIs Not Discovered
- Duplicate CI by IP Address
- Duplicate CI by Serial Number
- Not Classified
- Not Responding
- Connection Errors