nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Bulk Assignment of Orphaned Nodes to Active Polling Engine

Siddharth Kadam

Several nodes in our SolarWinds environment are currently orphaned and associated with invalid Polling Engine IDs. Because of this mismatch, these nodes are not being polled correctly, which has led to monitoring gaps and false alerts.

We are aware of the manual method to reassign nodes one by one via the SolarWinds console, but we currently have around 120 orphaned nodes, making the manual approach time‑consuming and error‑prone.

Is there a supported or recommended way to reassign orphaned nodes and agents to an active Polling Engine in bulk?

Find more posts tagged with

pollingengine

sam

orion

orphaned objects

Comments

Lofstrand

Use "manage nodes"

On the left, group by "polling engine"
Check all the nodes you want to move, probably all on the old engine
Go to menu "more actions" and then "Change polling engine"
Choose the new polling engine and all nodes will be moved

muhammad.osama

Here are the recommended approaches, ranked from safest to most advanced:

1. The Native Bulk Edit Method (Supported)

SolarWinds actually has a bulk-reassignment feature hidden within the Manage Nodes page. This is the only "supported" method that ensures all associated polling jobs are updated correctly in the background.

Click Edit Properties.
Scroll down to the Polling section.
Click Submit.

2. The SQL/Database Method (Fastest, Use Caution)

If the web console is timing out due to the number of nodes, you can update the EngineID directly in the database.Note: Always back up your database before running manual updates.

SQLSELECT EngineID, ServerName, IP FROM Engines
SQLUPDATE NodesDataSET EngineID = XWHERE EngineID = Y
Force Refresh: After a SQL update, you usually need to restart the SolarWinds Information Service (SWIS) on the main application server to force the polling jobs to migrate to the new engine.

3. The API/PowerShell Method (Recommended for Automation)

If you want to do this via the SolarWinds API (using OrionSDK), this is considered safer than SQL because it triggers the proper internal business logic.

PowerShell

# Requires SwisSnapin or OrionSDK$targetEngineID = 1 # ID of your healthy engine$orphanedNodes = Get-SwisData $swis "SELECT Uri FROM Orion.Nodes WHERE EngineID = 99" # 99 = old engineforeach ($nodeUri in $orphanedNodes) {    Set-SwisObject $swis -Uri $nodeUri -Properties @{ EngineID = $targetEngineID }}

Critical Considerations for 2026

Agent Reassignment: If these orphaned nodes use SolarWinds Agents, reassigning the EngineID should automatically trigger the agent to attempt a reconnect to the new poller. However, ensure the new Polling Engine is reachable from the agent's network over port 17778.
Licensing: Ensure your target Polling Engine has enough "capacity" (elements) to take on the 120 new nodes. You can check this in the Polling Engines view under "Polling Load Percentage."

Siddharth Kadam

The Manage Nodes page displays only active nodes that are assigned to a polling engine.
Orphaned nodes—those that have lost their association with a polling engine—do not appear in the Manage Nodes view.

Siddharth Kadam

Thanks, it works

Quick Links

Alert HTML Content
Alert Cleared.htmlHello, I would like to share the HTML template details we have prepared so that Solarwinds alarms can become more meaningful. It can list alarm object details and connected device details separately in HTML template. Except for object and device details, you can easily add custom property information…
Cisco ASR Devices
Cisco ASR Devices.pollerCisco ASR Devices
Basic SWQL Syntax
SWQL is built on the framework of SQL and as such supports most of the standard clauses as part of a query. A very simple example query is: SELECT Caption, IPAddress, Vendor, ResponseTime FROM Orion.Nodes Dissecting this query is relatively straightforward: show some fields (Caption, IP address, Vendor, and Response Time)…
Cisco ASA SSL Tunnels
Active SSL Tunnels-ASA.UnDPThis poller *should* display the number of Active SSL VPN (Anyconnect) Tunnels currently connected to your box. However, I tried it with my 5520 running 8.0.4 and for some reason I get a OID Not Supported. Here's my post in the forum: *EDIT* This is confirmed working with at least Interm release…