Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Rebuild/migrate Orion poller configurations

Rebuild/migrate Orion poller configurations

Table of contents

Updated November 30th, 2016


This article provides information on rebuilding and migrating your Orion Poller configurations. 


You may refer to the  SolarWinds Migration Guide document for additional information regarding SQL and NPM Migration.

The guide includes the following documents with prep lists and checklists, including steps for the poller migration:


Review Best Practices for Managing the Orion Platform Database for information on SQL best practices and performance tuning.
The whole Orion Database, including all data polled and settings reside in the database. 
But there are a few folders that may have customizations and should be backed up.


All NPM versions


  1. Reconfigure Syslogs\Traps\Netflow to be sent to the correct Orion Poller (optional)

    If you are migrating Orion Poller to a new IP address:

    • reconfigure your Syslog messages on the nodes to move to the new Orion server
    • reconfigure your Traps messages on the nodes to move to the new Orion server, and
    • reconfigure your Netflow messages on your nodes to forward to the new Orion server.
  2. Licensing (required)

    Refer to the Deactivating and Activating Orion Product Licenses during Migration article for the procedure.

  3. Move Nodes to a new EngineID (Must be done if a new engineID has been created in the Engines table.)

    The ability to move monitored nodes between polling engines is now a feature of Web Node Management (NPM v10.2 onwards).

    Do the following steps to change the polling engines:

    1. Log in to the web console as a user with node management rights.
    2. Click Home.
    3. In the All Nodes resource on the Orion Summary Home view, click Manage Nodes.
    4. Check all the nodes that needs to be changed, and then click More Action > Change Polling Engine.

    If you are migrating a new poller, but keeping the name or IP, after the migration it is likely that it is still recognized as if it is the same server.
    This can be seen in Orion Website > Settings > Polling Engines.
    Or, open Orion DB Manager or SQL Management Studio and run the following: 

    SELECT TOP 1000* FROM [dbo].[Engines]

    If the engineID is the same, no action is needed. For some reasons, the migration picked it up as a NEW Poller.
    Then a new engineID record will be created and you will have to follow the node migration process to migrate the nodes from the old to the new poller's engineID.

  4. Deleting Old Polling Engines (optional)

    Refer to the screenshot below on how delete old polling engines via web console:

    Refer to the SolarWinds Migration Guide on how to delete old polling engines via database manager. 

  5. Reports (optional)

    Web-based Report Scheduler

    • Report scheduling is now featured in the web console.
    • Email, print or save reports on a scheduled basis.
    • Send reports using SSL with Office365. 
  6. Migrating NCM to a new server environment.

    Refer to the Migrating NCM v7.2 to a New Server Environment for more information or the SolarWinds Migration Guide.

    You can upgrade to NCM 7.2 first before the migration. NCM 7.3.x merges NCM and NPM database into 1 DB and simplifies the migration process.

  7. Migrating Netflow v4 FSDB to talk to a new SQL Server Database

    The SolarWinds Migration Guide and the NetFlow Traffic Analyzer Administration Guide provide migration information. The guide includes:

  8. FSDN Configurator on FSDB database server and NTA Application server.
    Here you can choose:


Last modified