Omi New: Win32operatingsystem Result Not Found Via

The error "failed (Win32_OperatingSystem results not found via OMI)" typically occurs when a monitoring tool, such as FortiSIEM, fails to retrieve system metadata from a Windows host using the Open Management Infrastructure (OMI) protocol. This is often due to authentication mismatches, network blocks, or local permission issues rather than the class itself being missing. Common Causes & Fixes

The most common reason for "result not found" via OMI is an issue with how the collector authenticates with the target Windows server. win32operatingsystem result not found via omi new

or

When you run a command like omi new root/cimv2 Win32_OperatingSystem, you are asking the OMI client to connect to a remote Windows machine’s OMI server (which wraps WMI) and instantiate an object representing the OS. Indicates the issue might be with how the

3.4 Verify OMI authentication

omi query -u user -p pass 'root/cimv2' "SELECT * FROM Win32_OperatingSystem"

Indicates the issue might be with how the specific monitoring agent is processing the metadata. PowerShell commands such as FortiSIEM

Before troubleshooting the Linux/OMI side, confirm WMI is working on the Windows machine itself.