How to map Site24x7's On-Premise Poller to multiple MSP customer accounts?

How to move Site24x7 On-Premise Poller from one customer account to another?

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.

Follow the below steps for Windows 32 & 64-bit On-Premise Pollers
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'

Follow the below steps for Linux 32 & 64-bit On-Premise Pollers

Reconfiguration steps:
  1. Stop the Site24x7 On-Premise Poller process: Go to /opt/Site24x7OnPremisePoller -> sudo sh StopServer.sh                                                                                                                                                                                                 
  2. 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)                 
  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.
    /opt/Site24x7OnPremisePoller/.eum                                                                                                                                                                                                                                                  
  5. Start the Site24x7 On-Premise Poller process.
    Go to /opt/Site24x7OnPremisePoller -> sudo sh StartServer.sh &

    • Related Articles

    • 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 ...

    • Compare our various methodologies for Website Monitoring

      Get to know Site24x7 monitors better and choose the one that best fits your monitoring needs. Compare the functionality of the following monitors: Website Monitoring Webpage Speed (Browser) Web Transaction Monitoring Web Transaction (Browser) SSL/TLS ...

    • Troubleshooting false positive alerts in monitoring

      Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...

    • Exclude Site24x7 monitoring traffic from Google Analytics

      You can exclude traffic from the Site24x7 Web Transaction (Browser) monitor and Webpage Speed (Browser) traffic from Google Analytics in two ways. To exclude traffic for the Web Defacement monitor, you can follow the first method. 1. Creating a ...

    • Validating sender email using DKIM authentication

      What is DKIM? DomainKeys Identified Mail (DKIM) is an advanced authentication method used widely by email service providers to verify the email from the point of its origin by validating the email sender. It allows the email senders to authenticate ...