A common reason for the query returning blank results is insufficient privilege levels.
// C/C++ pseudo-code CIMInstance *inst = omi_new("root/cimv2", "Win32OperatingSystem", NULL);
[Remote Monitor / FortiSIEM] │ (WS-Man Protocol over HTTPS/HTTP) ▼ [Target Windows Server] └── [WinRM Listener] (Ports 5985/5986) └── [OMI Provider / WMI Service] └── [CIMV2 Namespace Engine] ──► [Win32_OperatingSystem]
Get-WmiObject -Class Win32OperatingSystem -Namespace root\cimv2 win32operatingsystem result not found via omi new
This error typically indicates that the OMI agent, while trying to query Windows Management Instrumentation (WMI) to retrieve operating system data ( Win32_OperatingSystem ), has failed to receive a valid response, resulting in a null or missing result. Understanding the Components
Following this workflow ensures that the target Windows host can expose the Win32_OperatingSystem properties smoothly across the OMI pipeline. To help target the precise cause, let me know:
This feature improves interoperability when using tools designed for Windows WMI (which is case-insensitive) against OMI endpoints (which are case-sensitive). It prevents silent failures in automation scripts and DSC configurations during cross-platform management. A common reason for the query returning blank
(Note: Often, the OS provider is bundled into a larger package like scx (System Center Cross Platform) rather than existing as a standalone OMI provider).
If monitoring a member server or standalone client host, verify that the account is part of the local group.
Then reboot and reinstall OMI if necessary. To help target the precise cause, let me
From the OMI client, check the target system type:
Is the target machine a or a standard member server?
Help you to pinpoint the exact broken provider.