Win32operatingsystem Result Not — Found Via Omi New

You are running an OMI client query against a Linux server (the OMI agent). You expect the query to return system information analogous to the Windows Win32_OperatingSystem class.

The Command:

omiendpoint /namespace:"root/cimv2" /className:Win32_OperatingSystem
# Or via the Python/Scripting API

The Observed Result: The query executes, but returns no instances or a generic "Not Found" error, despite the OMI service running correctly.

From the OMI client, check the target system type: win32operatingsystem result not found via omi new

uname -a   # If Linux

or

scxadmin -status  # If using SCOM agent

If the target is not Windows, do not query Win32_OperatingSystem. Use Linux-specific classes like OMI_OperatingSystem or CIM_OperatingSystem.

In Azure Arc-enabled servers, Microsoft uses a locked-down OMI agent. For security reasons, certain high-impact WMI classes (including Win32OperatingSystem) may be filtered or require explicit allow-listing in the Arc guest configuration policies. You are running an OMI client query against

Symptoms: The error appears only on Arc-managed servers, not on standalone Windows boxes.

Solution: Review the Azure Policy assignments for "Guest Configuration" and ensure root\cimv2 and Win32OperatingSystem are not excluded.

To avoid "win32operatingsystem result not found via omi new" in the future, follow these golden rules when setting up OMI on a Windows fleet: The Observed Result: The query executes, but returns

Enable-NetFirewallRule -DisplayGroup "Windows Management Instrumentation (WMI)"

Then test from the client:

omi new root/cimv2 Win32_OperatingSystem

Win32_OperatingSystem is a core WMI (Windows Management Instrumentation) class that provides detailed information about the installed operating system, including version, last boot time, serial number, total memory, and more. Any management tool that gathers OS inventory typically queries this class.