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) > Change the polling engine on a node in NPM

Change the polling engine on a node in NPM

Table of contents
Created by John Salvani, last modified by Alvin Gutierrez on Jul 31, 2018

Views: 4,378 Votes: 5 Revisions: 11


Steps to change or transfer nodes to another polling engine. 


NPM version 10.6 and later


Follow the steps below if there is more than one polling engine because if there is only one polling engine in the database then the option will not appear. 


  1. Click Settings and then Manage Nodes
  2. Select the node(s) you want to transfer by selecting the checkbox and then click More Action > Change Polling Engine.
  3. Select the new polling engine from the list the pops out. 
  4. Finish by clicking Change Polling Engine.


If this procedure doesn't work in your current NPM version, follow the steps below:

  1. On your Orion Web console, go to Settings > Manage Nodes.
  2. Click the boxes of the nodes you want to transfer.
  3. Click Edit Properties. 
  4. Under Polling section, click Change Polling Engine and select the new engine you want to assign to the node. 
  5. Click Submit. 






Last modified