Win32operatingsystem Result Not Found Via Omi New 95%
The most common reason for "result not found" via OMI is an issue with how the collector authenticates with the target Windows server.
If networking and credentials are correct but the Win32_OperatingSystem class still returns no data, the target server's WMI repository may be corrupted.
If this fails, the issue is likely network-related or credential-based rather than a FortiSIEM GUI bug.
The user account must be part of the local Administrators Group on the target Windows machine to query WMI remotely. win32operatingsystem result not found via omi new
This is a key step for repairing a corrupted or missing cimwin32 provider.
OMI requires specific ports to be open for communication. Ensure that the Windows host's firewall allows inbound connections from your management server on , TCP/5985 , and TCP/5986 (for HTTPS) [9†L11-L13]. You can test this from your management server using Test-NetConnection in PowerShell:
Test-NetConnection <Windows_Host_IP> -Port 5985 The most common reason for "result not found"
If the network connection succeeds but the error persists, the local WMI framework on the target server may be broken or corrupted. Step 1: Diagnose Repository Integrity
On the target Windows machine, run winmgmt /verifyrepository in an elevated command prompt. If it returns "inconsistent," you may need to rebuild the repository.
curl -k -u 'domain\user:password' https://windowsserver:5986/wsman -H "Content-Type: application/soap+xml" The user account must be part of the
: Required ports for OMI/WMI communication are often blocked. Ensure TCP/5985-5986 (WinRM) are open between the collector and the host. Insufficient Permissions : The user account must be part of the Local Administrators
Troubleshooting "Win32_OperatingSystem Result Not Found via OMI"
Even if network lines remain entirely open, a lack of deep access privileges can cause the API query to return empty datasets.
One perplexing error that administrators encounter during this process is: .