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

The 32-bit On-Premise Poller is no longer supported in Site24x7 version 6.5 and above.

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. 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 and 64-bit On-Premise Pollers

Reconfiguration steps:

    1. Stop the Site24x7 On-Premise Poller process.
       Go to services.msc -> stop the service name 'Site24x7 On-Premise Poller'

    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 is needed]
PROXY_HOST= [User Proxy Host]
PROXY_PORT= [User Proxy Port]
PROXY_USER= [User Proxy User]
PROXY_PASS= [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]

MONAGENTID and AGENTUID are dynamic values. These will auto-update after successful poller registration..

      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 and 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= [User Proxy Host]
PROXY_PORT= [User Proxy Port]
PROXY_USER= [User Proxy User]
PROXY_PASS= [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]

MONAGENTID and AGENTUID are dynamic values. These will auto-update after successful poller registration. 

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

• Moving a device from one On-Premise Poller to another

  You can always change the On-Premise Poller that monitors your device when your needs demand. This feature also helps to balance the load on an existing On-Premise Poller by moving some monitors to another On-Premise Poller. Log in to your Site24x7 ...

• Why is my On-Premise Poller not getting registered?

  Please find below the possible reasons for your On-Premise Poller not being registered: The most common cause is when your machine (where the agent is installed) might not be connected to the internet. Check if there are any connectivity issues with ...

• Changes to the On-Premise Poller when the account is migrated to a different data center

  When an account is migrated to another data center, the Device Key of the account also changes. Because of this, the Device Key needs to be updated in the On-Premise Poller config file to ensure uninterrupted monitoring. You can find the new Device ...

• Upgrading On-Premise Poller to the latest version

  Go to Admin > On-Premise Poller in the Site24x7 web client Click on the name of the On-Premise Poller In the dashboard that opens up, click upgrade to the latest version Confirm it in the pop-up The latest version of the On-Premise Poller will be ...

• When I restart/activate/upgrade the On-Premise Poller, why is it not showing data immediately

  The following may be one of the following reasons for data not showing up after restarting/activating/upgrading the On-Premise Poller: In cases where there is a large number of monitors pointed to the On-Premise Poller, data collection for all these ...