Already a NinjaOne customer? Log in to view more guides and the latest updates.

NinjaOne NMS: Network Discovery

Topic

This article describes how to use the Network Discovery utility to detect and manage networked devices in your organization.

Environment

NinjaOne Network Management System (NMS)

Description

This utility replaces the legacy Network Management System (NMS) download and installer. You can perform network discovery directly from the NinjaOne platform. Network Discovery scans your IP ranges for active devices, profiles them using Simple Network Management Protocol (SNMP) and other protocols, and adds them to NinjaOne for ongoing monitoring and management. You can run discovery on demand or on a scheduled basis, making it suitable for both initial network onboarding and continuous inventory maintenance. Before deploying the NMS delegate, ensure your environment meets the system requirements described in the linked article below.

Refer to our NinjaOne NMS System Requirements article before installing the NMS delegate.

Want to learn more about NinjaOne NMS? Check out our video library.

Index

Select a topic to continue:

NMS Delegate Architecture

Refer to Figure 1 for an overview of the NinjaOne NMS architecture, and note the following points:

  • To use NinjaOne's network management suite, deploy the NinjaOne NMS Delegate separately for every customer whose SNMP-capable devices you want to monitor.
  • The NMS Delegate is a separate installation from the NinjaOne monitoring agent, but you can install both agents in parallel. The NMS Delegate performs network discovery (manually) and adds the associated devices to NinjaOne.
ninjaone_nms_architecture_v6.png
Figure 1: The Network Discovery data flow (click to enlarge)

Configuring Network Discovery

  1. In the NinjaOne platform, click the + icon, then select Add device.
  2. Click Network Discovery.
NMS_Discovery_NewAddDevice.png
Figure 2: Add Device → Network Discovery (click to enlarge)
  1. The Network Discovery window will open. Configure the network and location parameters for discoverable devices and add any credentials they may require.
IPPreview_NetworkDiscoveryWindow.png
Figure 3: The Network Discovery window (click to enlarge)
  1. In the Network Discovery window, configure the following settings:
SettingDescription
OrganizationSelect the organization to which the network belongs.
LocationSpecify the physical location for discovery. If an organization has only one location, this field should automatically populate.
NMS Delegate

Select the device to use as the network probe.

  • The drop-down menu shows installed delegates, or a list of NinjaOne agents on which the delegate can run. The NMS Delegate only supports Microsoft Windows devices.
  • If you choose a NinjaOne agent that does not have the NMS Delegate installed, it will install before the network discovery job runs.
  • If you are selecting multiple network interface cards (NICs) on the network probe device, their combined IP range cannot exceed 4,094 addresses (/20). Otherwise, NinjaOne will block the discovery job and prompt you to reduce your NIC selection.

Refer to NinjaOne NMS: System Requirements for NMS-supported Windows operating system versions.

Preview NMS Delegate IPsDisplay a table from which you can confirm the probe's local IP addresses and subnets, copy or send an individual network range to the IP Targets window, or select multiple rows using the checkboxes and push them to all IP targets at once. This option only appears if you select an NMS Delegate.
IP targets

Enter comma-separated IP addresses, IP address ranges, and subnets for your discovery range. For example:

  • 192.168.1.1, 192.168.1.2, 192.168.1.3
  • 172.20.1.1 - 172.20.1.50
  • 10.1.1.0/20

Combined IP address range selections cannot exceed 4,094 addresses (/20). Otherwise, NinjaOne will block the discovery job and prompt you to reduce your IP address range.

  1. In the Credentials (optional) section, enter any credentials used by the devices you are discovering. Refer to NinjaOne NMS: Network Discovery Credentials for more information.

Running and Saving Network Discovery

After configuring Network Discovery, you can click Run discovery to perform the discovery immediately, or click Save and close to save the network discovery job.

Running a Network Discovery Job

After you click Run discovery, NinjaOne will search for eligible devices on your network. During the network discovery job, NinjaOne will create a service named Ninja NMS Manager Service and a corresponding process named nmsmanager.exe, which will promote the device to become the NMS delegate. If you close this window while the job is running, NinjaOne will display an alert.

In FedRAMP deployments, NinjaOne encrypts the NMS delegate database. If the encryption keys are lost or invalidated, the delegate may need to recreate its local database.
  • Click Close and continue to close the Network Discovery window and keep the job running.
  • Click View job history to open the Job history tab. Refer to the Viewing Network Discovery Job History section of this article for more information.

Saving and Scheduling a Network Job

Saving network discovery jobs enables you to re-run specific job configurations as needed, or on a custom schedule.

  1. Set up your network discovery job as described in the Configuring Network Discovery section of this article. When finished, click Save and close. The Save network discovery window will open.
  2. Activate the Enable discovery job toggle, then use the drop-down menus to enter a job name and configure an optional job schedule. You can schedule network jobs to run on an hourly, daily, weekly, or monthly basis.

Network Discovery Job Schedule Settings

Enter the following settings when scheduling a network job. When finished, click Apply. The job appears on the Saved jobs tab.

SettingDescription
RecurrenceSet the time interval between jobs.
Start dateSet the date on which the sequence of scheduled jobs begins.
Days of the week (weekly only)Choose the days on which the job runs.
Day of the month (monthly only)Choose the day of the month on which the job runs.
Time and Time ZoneSelect the time of day and the appropriate time zone to perform the first job.
End

Select one of the following options to end the job:

  • Never: Run the job according to the schedule with no end date
  • Yes: End on a specific date
  • Occurrence: End after a specific number of runs

Viewing Saved Network Discovery Jobs

The Saved jobs tab allows you to view all jobs that you have saved after running.

  1. In NinjaOne, navigate to AdministrationDevicesDiscovery and click the Saved jobs tab. This tab will display a list of saved jobs, which you can filter by data column.
Pagination_SavedJobs.png
Figure 4: Administration → Devices → Discovery → Saved jobs (click to enlarge)

Viewing Network Scan Details

Click a saved network job to open the Network scan details window. The window displays the following:

CategoryDescription
Job settingsView the job name and status.
Network scan settings

View the following network scan details:

  • Type
  • Organization
  • Location
  • Network probe
  • IP targets
  • Credentials
  • Job type
  • Create date
Credentials

List the following found credentials by type:

  • Windows
  • 1st SNMP
  • 2nd SNMP
  • Telnet
  • SSH
Advanced settings

View the following information:

  • Internet Control Message Protocol (ICMP) timeout (in milliseconds)
  • ICMP packet time to live (TTL)

Editing Saved Jobs

  1. Place your cursor over a job, then click the actions menu when it appears, and choose one of the following options from the drop-down menu:
    • Edit: Change the job's scheduling parameters.
    • Clone: Create a duplicate of the job.
    • Enable or Disable: Activate or deactivate a job.
    • Delete: Remove the job from the Saved jobs list.

Viewing Network Discovery Job History

The Job history tab shows all executions of each network discovery job for the past 90 days.

In NinjaOne, navigate to AdministrationDevicesDiscovery and click the Job history tab. NinjaOne will display a table that lists all previously run network discovery jobs, which you can filter by data column.

Pagination_JobHistoryPage.png
Figure 5: Administration → Devices → Discovery → Job history (click to enlarge)

Re-running Historical Network Jobs

You can re-run any job instance from the Job history tab.

  1. In the Job history tab, place your cursor over a job, then click the actions menu when it appears and choose Run from the drop-down menu.

Saving Historical Network Jobs

You can add any job instance from the Job history tab to your Saved jobs list.

  1. In the Job history tab, place your cursor over a job, then click the actions menu when it appears and choose Save.
  2. The Save network discovery job window will open. Configure the following settings:
SettingDescription
Job nameGive the network job a descriptive name.
ScheduleSet an optional run schedule for the job. Refer to the Saving and Scheduling a Network Job section of this article for more information.
OrganizationSelect the organization to which the network belongs.
LocationSpecify the physical location for discovery. If an organization has only one location, this field should automatically populate.
Network probeThis drop-down menu contains all Microsoft Windows devices currently online that have the NinjaOne agent installed. Refer to NinjaOne NMS: System Requirements for NMS-supported Windows operating system versions.
IP targets

Enter comma-separated IP addresses, IP ranges, and subnets for your discovery range. For example:

  • 192.168.1.1, 192.168.1.2, 192.168.1.3
  • 192.168.1.1 - 192.168.1.50
  • 192.16.17.30/20
Credentials (optional)Refer to NinjaOne NMS: Network Discovery Credentials for more information.

Viewing Job Instances From the Job History Tab

You can view details of specific job run dates and save previously run jobs to your Saved jobs list for future reference.

Viewing Job History Details and Scan Results

Click a saved network job to open the Network scan details window. From the Job history tab, a window will open containing two tabs:

  • General: This tab displays the same information as the Network scan details window when accessed from the Saved jobs page.
  • Scan results: Clicking this tab displays the results of the network scan for each historical execution of the network job. The window displays a list of each historical job instance, with the following data columns:
    • IP address
    • DNS information
    • Ping time
    • Ports
    • Credentials used
NMSDiscovery_JobHistoryScan.png
Figure 6: Job history → Network scan details → Scan results (click to enlarge)

Claiming Ownership of a Network Discovery Job

If the user who created the network discovery job has been deactivated, you can become the new owner of that job by opening the Network scan details window on the Job history tab and clicking the Claim ownership button.

NMS_Discovery_ClaimOwnership.png
Figure 7: Job history → Network scan details → Scan results → Claim ownership (click to enlarge)

Applying Ping Conditions Through Advanced Settings

Ping conditions are optional, but they let you fine-tune how NinjaOne NMS checks device availability, tailoring the process to your specific network and devices. To apply ping conditions for network discovery:

  1. Click Advanced settings.
NetworkDiscovery_NotNMS_AdvancedSettings.png
Figure 8: Network Discovery window → Advanced settings (click to enlarge)
  1. If your device is not local (for example, on a virtual private network (VPN)), consider increasing the Ping timeout (ms) and Ping packet TTL settings.
add_NMS network discovery_advanced settings_modal.png
Figure 9: Advanced settings (click to enlarge)

Advanced Settings Explained

Refer to this table for an explanation of each advanced setting.

SettingDescription
Ping timeout (ms)Specify how long, in milliseconds, to wait for a reply. The initial packet is sent, waits for a reply, and gives up at a preset timeout.
Ping packet TTLSet the Time to Live (TTL) at a specified threshold.
Pings per nodeSpecify the number of pings sent to each host to test if the host successfully responds to each.
Delay between pings (ms)Specify the number of milliseconds that pass between each ping.

For any device not previously used as a network probe, NinjaOne creates a new service that promotes the device to become the NMS delegate. The service is named Ninja NMS Manager Service, and the corresponding process name is nmsmanager.exe.

Adding Discovered Devices to Your Organization

After the network discovery job finishes, you can convert discovered devices to NinjaOne devices, which can be either managed (for example, NinjaOne Mobile Device Management (MDM), Agent, and NMS) or unmanaged.

In NinjaOne, navigate to Dashboard(Your Organization)DevicesDiscovered. NinjaOne will display the Discovered devices table.

NetworkDiscovery_DiscoveredDevs.png
Figure 10: Dashboard → Organization → Devices → Discovered (click to enlarge)

Viewing Device Deployment Status

Before converting devices, review the Deployment status column in the Discovered devices table. This column shows each device's readiness to receive the NinjaOne agent. NinjaOne assigns the following possible statuses to each device:

StatusDescription
Agent already installedThe NinjaOne agent is already installed and running on this device. No deployment action is required.
DeployableThe device meets all prerequisites for agent deployment. NinjaOne can attempt to install the agent on this device.
Not applicable

NinjaOne cannot deploy to this device at this time. Select the status icon to see the specific reason. Common reasons include:

  • One or more required ports are not open on the device.
  • The deployment credential did not authenticate successfully.
  • The device is a network device and does not support agent installation.
  • The device runs an operating system NinjaOne does not currently support for deployment.
DeploymentStatus_Table.png
Figure 11: Discovered devices → Deployment status (click to enlarge)

Converting a Device

Only devices with a Deployable status are available for selection.
NinjaOne attempts to match discovered devices using several methods, such as serial numbers and MAC addresses. If it identifies a match, NinjaOne dims the duplicate entry and links the record to the primary device.

From the Discovered devices screen, select the checkbox next to each device you want to convert, then click Add. Select one of the following conversion options:

OptionWhen to use
Convert NMS deviceUse this option for devices responding on the network that you want to bring into NMS management.
Convert unmanaged deviceUse this option to add devices to your inventory without NinjaOne management. This option requires NinjaOne IT Asset Management (ITAM) to be activated in your instance.
NetworkDiscovery_AddDevices2.png
Figure 12: Discovered devices options (click to enlarge)

Assigning Device Roles to Discovered Devices

Device roles determine which NinjaOne policy governs the device. You must assign a role to each device if NinjaOne did not assess its role during discovery. Refer to NinjaOne Endpoint Management: Device Roles for more information.

  1. In NinjaOne, navigate to Dashboard(Your Organization)DevicesDiscovered, then click the device name.
  2. In the device's dashboard, navigate to GeneralSettingsDevice informationEdit.
NMS_Discovery_EditDeviceSettings.png
Figure 13: General → Settings → Device information → Edit (click to enlarge)
  1. In the Edit device information window, use the Device role drop-down menu to select a new role, then click Update.
NMS_Discovery_EditDeviceRole.png
Figure 14: The Device role drop-down menu (click to enlarge)

Additional Resources

Refer to NinjaOne NMS: Device Dashboard Navigation and Management for more information about viewing and configuring NMS devices.

FAQ

Next Steps