The WMI service will recreate the repository automatically.
If WinRM listeners are missing or configured with ListeningOn = null , you have several options:
Because it is a core WMI class, virtually every management tool that uses WMI or OMI will query Win32_OperatingSystem as part of its discovery process. If this query fails, the tool cannot reliably determine what operating system it is communicating with.
If connectivity and WinRM are working but the OMI query still returns no results, the WMI subsystem may be damaged. win32operatingsystem result not found via omi new
: Test the connection manually from your monitoring node's core CLI (the collector or supervisor shell) using the integrated omic compilation binaries:
If they return an error or no data, proceed to WMI repair steps.
Instead of waiting on the monitoring platform GUI to refresh, run a raw OMI command line verification manually from the collector. Replace the arguments below with your infrastructure details: The WMI service will recreate the repository automatically
What are you running the OMI command from?
Start-Service WinRM Set-Service WinRM -StartupType Automatic
—often specifically noted as "NEW" in logs—it usually indicates a breakdown in communication between an Open Management Infrastructure (OMI) collector (like FortiSIEM or SCOM) and the target Windows machine. If connectivity and WinRM are working but the
Ensure you are running the latest version of OMI and the psrp-host if you are using PowerShell Remoting over OMI. 📋 Quick Comparison: OMI vs. Traditional WMI OMI (Open Management Infrastructure) WMI (Windows Management Instrumentation) Primary OS Linux / Unix Protocol WS-Management DCOM / RPC Namespace root/omi (default) root/cimv2 (default) Footprint Lightweight / High Performance Heavy / Feature Rich To help you get this fixed quickly, could you tell me:
Ensure the account used for monitoring has and Remote Enable permissions. 4. Restart OMI/SCOM Services