After upgrading to SolarWinds Observability Self-Hosted 2026.2.2, I found that some new native polling capabilities were not showing as applicable to existing nodes. In my case, the new Switch Stack poller showed Not a Match even though the devices were correctly identified.
A normal Network Rediscovery did not resolve the issue. Since I did not want to make any changes to the existing monitored elements, the devices were simply skipped during the import. Manually running List Resources → Submit caused SolarWinds to reevaluate the node, and the Switch Stack poller became applicable. I wanted a way to do this in bulk without manually changing the existing interface/port monitoring selections on each device.
The PowerShell script below automates the List Resources → Submit process through SWIS, preserving the resource selections returned by SolarWinds. Although developed for the Juniper Switch Stack issue, the process is not Juniper-specific and may be useful after upgrades that introduce new native polling capabilities.
Note: This is more than a normal rediscovery. The script submits the resources that SolarWinds automatically selects during List Resources, so newly available resources may be enabled. The script only causes newly supported native pollers to become applicable; it does not assign or enable those pollers. They must still be assigned separately from the Manage Pollers page. Poller assignment could be added to the script, but I intentionally left it separate to keep the community version safer to test and adapt. Test against representative nodes first and use -WhatIf to verify your target population before running it in bulk.
Invoke-SolarWindsListResourcesRefresh.ps1
