CPU metrics are not polled for Windows 2008 and older WMI nodes in SolarWinds Platform 2025.2

This is a known issue where Windows Server 2008 and earlier nodes polled via WMI or Agent incorrectly receive the poller N.Cpu.WMI.WindowsPct after upgrading to SolarWinds Platform 2025.2. The correct CPU poller for these nodes should be N.Cpu.WMI.Windows or N.Cpu.WMI.Windows2008R2.

Upgrade 2024.4 → 2025.2 Overview

This issue is addressed in SolarWinds Platform 2026.1. Consider upgrading your environment.

Workaround:

To restore CPU polling functionality for affected nodes, manually update the poller type in the SolarWinds database from N.Cpu.WMI.WindowsPct to N.Cpu.WMI.Windows for the affected nodes. 

NOTE:

• Before making any changes kindly make sure that you have any of the applicable following a recent backup of the database, a snapshot of the VM, or a restore point of the physical server.
• Kindly work with your DBA for any database-related concerns.

Method 1: Using Database Manager GUI

1. RDP to the Main SolarWinds Platform Server.
2. Stop the SolarWinds services via the SolarWinds Platform Service Manager.
3. Open the Database Manager as an administrator from the SolarWinds Platform folder of the start menu.
4. Select Add Orion Server and expand the SolarWindsOrion database.
5. Scroll down to the Pollers table and double click.
6. Click on Execute Query on the right side.
7. Click on Enable table editing.
8. Find entries where PollerType = N.Cpu.WMI.WindowsPct and rename them to N.Cpu.WMI.Windows.  

9. Press Enter to save the change, and select Execute query again to ensure the change was committed to the database.
10. Start the SolarWinds service via the SolarWinds Platform Service Manager.
11. Verify CPU data is now polling correctly.

Method 2: Using SQL Query

1. RDP to the Main SolarWinds Platform Server.
2. Stop the SolarWinds services via the SolarWinds Platform Service Manager.
3. Open the Database Manager as an administrator from the SolarWinds Platform folder of the start menu.
4. Select Add Orion Server, right-click on the SolarWindsOrion Database and select New query.
5. Paste the following SQL Query and select Execute query to update the Pollers table for the NetobjectIDs you need to. In the example they are (3419 , 734)

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation

Update Pollers set PollerType ='N.Cpu.WMI.Windows'
where PollerType='N.Cpu.WMI.WindowsPct' and Netobjectid in ( 3419, 734)

NOTE: If you need to add nodes, make sure to separate the IDs by a comma.

​​​​​​​

6. Start the SolarWinds service via the SolarWinds Platform Service Manager.
7. Confirm CPU polling resumes for affected nodes.

Additional Recommendations

• Verify WMI connectivity and permissions on the affected nodes using wbemtest.
• Ensure DNS forward and reverse lookups are functioning correctly for the nodes.
• Check firewall and port settings to allow WMI/RPC communication.
• Monitor logs for any further WMI-related errors.