Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Install NCM APE (Additional Polling Engine) on a different drive

Install NCM APE (Additional Polling Engine) on a different drive

Table of contents

Updated August 23rd, 2017

Overview

This article provides brief information on the effects of installing the NCM Additional Polling Engine (APE) on a different drive letter (not the same as on the main NCM PPE server installation directory). 

Environment

NCM version 7.4.1 or later

Detail

When you install NCM APE on a different drive letter that does not correspond with the drive letter where you install the Main NCM server. This will cause an issue where the Syslog and Trap viewer setting for RTNForwarder.exe will only use one drive letter globally.

 

SolarWinds recommends installing the APE on the same drive letter on the Main NCM server and APE server. However. if you have already installed the APE on a different drive letter and the NCM main server, do the following:

 

Create separate alert action RTNForwarder.exe for each poller and set correct path and create new rule for each drive letter.

 

For example, SyslogRule actions will looks as follow:

 

    1st Action

C:\Program Files (x86)\SolarWinds\Orion\SolarWinds.NCM.RTNForwarder.exe ${IP_Address},RealtimeNotification,${DateTime},${Message}

 

    2nd Action

E:\Program Files (x86)\SolarWinds\Orion\SolarWinds.NCM.RTNForwarder.exe ${IP_Address},RealtimeNotification,${DateTime},${Message}

 

 

 

 

 

Last modified

Tags

Classifications

Public