Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM NetPath - Not all agents show when assigning a probe to a service

NPM NetPath - Not all agents show when assigning a probe to a service

Updated October 28, 2016

Overview

This article provides brief information when assigning a probe to a service, not all agents are listed in the drop-down menu.

Environment

NPM 12.0 and later

Cause 

Only agents with currently assigned probes or agents that previously had probes assigned appear in the drop-down.

 

Resolution

In order to add new probes to a NetPath service (even if agent is deployed) do the folowing:

  1. Select NetPath Service where you want to add the probe.
  2. Click on Create New Probe.
  3. Enter the details for the Probe (hostname, ip address, username and password).
  4. Click Create.

Now you should be able to assign the probe to the NetPath Service.

 

 

 

 

 

 

Last modified

Tags

Classifications

Public