Troubleshooting "Win32OperatingSystem Result Not Found via OMI New"
If your original script used omi new , rewrite it to use omi enumerate or, better yet, use the CIM_OperatingSystem class (the cross-platform standard): win32operatingsystem result not found via omi new
: Try switching from NTLM to Kerberos authentication. Users often find that NTLM fails to return results even when credentials are correct. Run a salvaging command: winmgmt /salvagerepository Use code
The issue is likely with permissions, firewall, or the OMI provider itself. 2. Repair/Rebuild the WMI Repository If local WMI queries fail, you must repair the repository. Stop the WMI service: net stop winmgmt Use code with caution. Run a salvaging command: winmgmt /salvagerepository Use code with caution. If that fails, run a reset: winmgmt /resetrepository Use code with caution. Restart the server and check WMI functionality again. 3. Check Permissions and Namespace Security The polling account must have remote access to WMI. Run wmimgmt.msc . Right-click WMI Control (Local) -> Properties . Navigate to the Security tab. Expand Root , select CIMV2 , and click Security . Authentication Protocol Issues
"Win32_OperatingSystem results not found via OMI" typically indicates a communication or permission failure between a monitoring collector (like FortiSIEM) and a Windows host using the Open Management Infrastructure (OMI) protocol. This prevents the collector from retrieving essential OS data via the standard Win32_OperatingSystem WMI class. Core Causes & Fixes 1. Authentication Protocol Issues