Win32operatingsystem Result Not Found Via Omi New ((new)) -

OMI communication depends on several specific legacy and modern management protocols. Ensure your network firewalls allow traffic from your Collector or Supervisor to the target Windows host over these ports: RPC Endpoint Mapper UDP/137: NetBIOS Name Service TCP/5985: WinRM HTTP TCP/5986: WinRM HTTPS 2. Verify User Group Memberships

If you only need OS name and version, Win32_ComputerSystem also provides SystemType and Manufacturer , but not OS version. For OS version, Win32_OperatingSystem is irreplaceable.

Follow this multi-step workflow to isolate where the handshakes and queries are failing.

| Cause | Description | |-------|-------------| | | Win32_OperatingSystem is case-sensitive in some contexts. | | OMI namespace mismatch | Default namespace is root/cimv2 ; other namespaces may not contain this class. | | Insufficient permissions | OMI user lacks WMI read access. | | Corrupted WMI repository | WMI class enumeration fails. | | OMI server not running | OMI service ( omiserver ) down or not installed on target. | | Firewall blocking DCOM/WinRM | OMI uses WinRM (HTTP/HTTPS) by default; blocked ports cause empty results. | | 64-bit vs 32-bit redirection | OMI might be running in 32-bit mode and cannot access 64-bit WMI classes. | win32operatingsystem result not found via omi new

If it reports inconsistency, run:

Manually test the connection using the omic tool from your FortiSIEM node:

If this returns empty, check the OMI log ( /var/log/omiserver.log on Linux OMI client, or Event Viewer on Windows). OMI communication depends on several specific legacy and

If your network and accounts are fine but the manual test still fails, the WMI data inside Windows itself might be corrupted.

This specific failure prevents remote platforms from gathering basic system details like the hostname, operating system version, and patch levels. Resolving it requires diagnosing permissions, network layers, and the underlying Windows Management Instrumentation (WMI) subsystem. Understanding the Architecture: OMI vs. WMI

winmgmt /salvagerepository

If this fails, the issue is likely network-related or credential-based rather than a FortiSIEM GUI bug.

ping <TARGET_IP_OR_HOSTNAME>

The error indicates that an OMI (Open Management Infrastructure) query attempting to retrieve Win32_OperatingSystem class information from a Windows system returned no results. This typically occurs when: For OS version, Win32_OperatingSystem is irreplaceable

The error was eliminated within 48 hours.