For an
MSP Account in Site24x7, every
Customer Account has a unique
Device Key. Every On-Premise Poller in a
Customer Account is mapped to that unique Device Key and can only be mapped to one account at a time. i.e. it cannot be added at the MSP level and should be associated at customer level only. To move On-Premise Poller from one account to a new account, follow these steps with the Device Key of the account to which the On-Premise Poller has to be moved.
Reconfiguration steps:
1. Stop the Site24x7 On-Premise Poller process.
Goto services.msc -> stop the service name 'SITE24X7_ONPREMISEMONITOR'
2. Go to
C:\Program Files (x86)\Site24x7OnPremisePoller\conf
Edit the file 'install.txt' where you can find the below keys. Change the values as [ ]
-------------------
S24X7KEY=[new site24x7 device key]
PROXY=[false/true - depends on if proxy needed]
PROXY_HOST=
PROXY_PORT=
PROXY_USER=
PROXY_PASS=
SERVERMONITOR=false
--------------------
If the PROXY=true, then give appropriate values for PROXY_HOST, PROXY_PORT, PROXY_USER(username proxy credentials), PROXY_PASS(password proxy credentials)
3. Edit the file 'serveragent.config' under /conf/ folder. Delete all the keys except the below:
-----------------------
MONAGENTID=SITE24X7
AGENTUID=SITE24X7
NETWORKID=UPDATEDSITE24X7
CUSTOMERID=[new site24x7 device key]
-----------------------
Note: For MONAGENTID, AGENTUID the value SITE24X7 should be modified.
4. Delete '.eum' file available in the Site24x7 On-Premise Poller home folder.
C:\Program Files (x86)\Site24x7OnPremisePoller\.eum
5. Start the Site24x7 On-Premise Poller process.
Go to services.msc -> Start the service 'SITE24X7_ONPREMISEMONITOR'
Reconfiguration steps:
Stop the Site24x7 On-Premise Poller process: Go to /opt/Site24x7OnPremisePoller -> sudo sh StopServer.sh
Go to
/opt/Site24x7OnPremisePoller/conf/
Edit the file 'install.txt' where you can find the below keys. Change the values as [ ]
-------------------
S24X7KEY=[new site24x7 device key]
PROXY=[false/true - depends on if proxy needed]
PROXY_HOST=
PROXY_PORT=
PROXY_USER=
PROXY_PASS=
SERVERMONITOR=false
--------------------
If the PROXY=true, then give appropriate values for PROXY_HOST, PROXY_PORT, PROXY_USER(username proxy credentials), PROXY_PASS(password proxy credentials)
Edit the file 'serveragent.config' under /conf/ folder. Delete all the keys except the below:
-----------------------
MONAGENTID=SITE24X7
AGENTUID=SITE24X7
NETWORKID=UPDATEDSITE24X7
CUSTOMERID=[new site24x7 device key]
-----------------------
Note: For MONAGENTID, AGENTUID the value SITE24X7 should be modified.
Delete '.eum' file available in the Site24x7 On-Premise Poller home folder.
/opt/Site24x7OnPremisePoller/.eum
Start the Site24x7 On-Premise Poller process.
Go to /opt/Site24x7OnPremisePoller -> sudo sh StartServer.sh &
Related Articles
Synthetic browser module prerequisite and troubleshooting guide for On-Premise Pollers
Introduction This document provides a structured troubleshooting guide for resolving issues encountered during the download process of On-Premise Poller for Synthetic (Browser) Module. It covers possible statuses, check-up steps, remedies, and ...
Monitors that require On-Premise Pollers in Site24x7
Certain monitor types in Site24x7 require the use of On-Premise Pollers for data collection, especially when monitoring internal, firewall-restricted, or private resources. Depending on the type of monitoring, additional modules like the Network ...
Resolving huge disk space issues with the On-Premise Poller and Network Module
Often huge disk space results from the heap dump files in the NetworkPlus/bin directory of the On-Premise Poller. What are HPROF files? HPROF files are used to store Java virtual machine (JVM) memory dumps. When a JVM runs out of memory (OOM), it ...
Exclude the selective SSH algorithms in On-Premise Poller during SFTP Transfer monitoring
By excluding SSH algorithms, you can restrict Site24x7 SSH Client from using the excluded algorithm while connecting to the SSH server during SFTP Transfer monitoring. Follow the steps mentioned below for SSH algorithm exclusion in On-Premise Poller ...
What to do if I create a new Site24x7 account by mistake even though my organization has an existing account?
When your organization already holds an existing account in Site24x7 and you create a new one by mistake, you can follow these steps: Terminate your Site24x7 account. Terminate your newly created organization. Request your admin to add you as a user ...