SAM: WMI Monitor is not recognizing the Namespace in the Component

In version 2025.4, the component WMI monitor does not use the Name Space, and it is defaulting to ROOT\CIMV2.

Component does not recognize NameSpace input.

This issue is addressed in SAM 2026.1. Consider upgrading your environment. If you can't upgrade, use the workaround below.

As a workaround, you can replace the affected component with a PowerShell Script Monitor that performs the required WMI queries remotely.
Use the sample scripts below depending on which statement you need to replace.

Using Windows PowerShell (Execution Mode: Remote)

Script Example for: SELECT State FROM DfsrInfo

try {
$info = Get-WmiObject -Namespace "root\MicrosoftDFS" -Query "SELECT State FROM DfsrInfo" -ErrorAction Stop
}
catch {
Write-Host "statustext: ERROR connecting to DfsrInfo - $($_.Exception.Message)"
exit 1
}
if (-not $info) {
Write-Host "statustext: DfsrInfo query returned no data"
exit 2
}
$state = if ($info.PSObject.Properties['State']) { $info.State } else { "Unavailable" }
Write-Host "statustext: DFSR State = $state"
Write-Host "statistic: $state"
Exit 0

Script Example for: SELECT State FROM DfsrVolumeInfo

try {
$volumes = Get-WmiObject -Namespace "root\MicrosoftDFS" -Class "DfsrVolumeInfo" -ErrorAction Stop
}
catch {
Write-Host "statustext: ERROR connecting to DfsrVolumeInfo - $($_.Exception.Message)"
Write-Host "statistic: -1"
exit 1
}

if (-not $volumes -or $volumes.Count -eq 0) {
Write-Host "statustext: No DFSR volumes found"
Write-Host "statistic: 0"
exit 2
}

$volume = $volumes[0]
$state = $volume.State

Write-Host "statustext: DFSR volume state = $state"
Write-Host "statistic: $state"
exit 0

Notes

You can apply this workaround in two ways:

1. Create a new Application Template using a PowerShell Script Monitor.

   • Add the script to the template.

   • Assign the template to the affected node.

   • Disable the original component that is impacted by the bug.

or

2. Add a new PowerShell component directly to the existing Application.

   • Insert the script.

   • Disable the problematic component.

Disclaimer

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.