A mid-sized enterprise was using Azure Arc + OMI to collect inventory from 2,000 Windows Server 2019 VMs. The monitoring dashboard suddenly showed Win32OperatingSystem result not found via omi new for a subset of 150 machines.
Investigation revealed:
Resolution steps:
The error was eliminated within 48 hours. win32operatingsystem result not found via omi new
The issue seems to be related to accessing or discovering the Win32_OperatingSystem class through OMI, possibly in a context where OMI is used for system management or monitoring.
omi query 'root/cimv2' "SELECT * FROM Win32_OperatingSystem"
If this returns empty, check the OMI log (/var/log/omiserver.log on Linux OMI client, or Event Viewer on Windows).
Get-WmiObject Win32_OperatingSystem
If this fails, the WMI repository may need repair. A mid-sized enterprise was using Azure Arc +
On Windows, OMI uses a bridge to translate OMI calls to WMI. If the OMI server’s WMI bridge provider is not properly registered or the WMI repository is corrupted, queries fail.
In the world of enterprise IT automation and cross-platform system management, OMI (Open Management Infrastructure) has become a critical component. As Microsoft’s open-source implementation of the DMTF CIM/WBEM standards, OMI allows administrators to manage Windows, Linux, and Unix systems from a single console. However, when querying Windows hosts using OMI—particularly via methods like omi new or leveraging Python’s pyomi—a frustrating error often appears:
"win32operatingsystem result not found via omi new" Resolution steps:
This error indicates that an OMI client (or a script using OMI) cannot retrieve information from the Win32_OperatingSystem class on a targeted Windows machine. This article provides a deep dive into why this error occurs, how to systematically diagnose it, and step-by-step solutions to resolve it permanently.
If the error persists despite all fixes, consider these alternatives:
omi query -u user -p pass 'root/cimv2' "SELECT * FROM Win32_OperatingSystem"