Win32operatingsystem Result Not Found Via Omi New

The target Windows machine may be rejecting NTLM authentication. Switching to Kerberos-auth in the OMI credential settings often resolves this, especially in domain environments.

file $(which omi)

This write-up details the root cause of this specific error and provides the solution for resolving it. win32operatingsystem result not found via omi new

net start winmgmt

On the Windows machine, rebuild WMI:

If this fails, the WMI repository is corrupt. Repair with:

The error message typically indicates a communication or authentication failure between a monitoring collector (like FortiSIEM) and a target Windows host using the Open Management Infrastructure (OMI) protocol. This is not a failure of the class itself, but rather a sign that the OMI client cannot successfully query the target's WMI repository. Common Root Causes The target Windows machine may be rejecting NTLM

There is rarely a single, simple explanation for this error. It usually points to an issue on the target Windows machine that is preventing WMI from functioning correctly. The Fortinet community points to connectivity or user account permission issues. The following are the most common root causes, each of which will be covered in our troubleshooting steps.

Ensure the OMI/SCX agents are running the latest version provided by your management system. net start winmgmt On the Windows machine, rebuild

Use the official uninstaller provided by your monitoring solution (e.g., uninstall.sh for OMI or the Azure Arc agent cleanup script).