Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
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 Aileen de Lara_ret on Oct 04, 2016

Views: 358 Votes: 5 Revisions: 10

Overview

Steps to change or transfer nodes to another polling engine. 

Environment

NPM version 10.6 and later

Steps

Follow the steps below if there is more than one polling engine because if there is only one polling egnine 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
19:49, 3 Oct 2016

Tags

Classifications

Public