Win32operatingsystem Result Not Found Via Omi New -

Example for RHEL/CentOS:

The error typically indicates a communication or permission failure between a monitoring collector (like FortiSIEM ) and a target Windows host. It often means that while the initial connection was made, the Open Management Infrastructure (OMI) service could not retrieve the required system information through WMI. Common Causes & Fixes FortiSIEM AIO - Collector questions and WMI/OMI issues win32operatingsystem result not found via omi new

: Ensure the following ports are open on the Windows host's firewall: TCP/135 : RPC Endpoint Mapper. TCP/5985 (HTTP) or 5986 (HTTPS): WinRM/OMI communication. UDP/137 : NetBIOS Name Service. Advanced Troubleshooting Example for RHEL/CentOS: The error typically indicates a

If you are using the stack (common in System Center scenarios), you typically need the omi-provider or specifically the OMI OS Provider . TCP/5985 (HTTP) or 5986 (HTTPS): WinRM/OMI communication

If this fails with the same error, move to checking host-side permissions. 2. Check WMI Namespace Security Ensure the account has remote access: wmimgmt.msc on the target Windows server. Right-click WMI Control (Local) Properties and select and ensure your monitoring user has Execute Methods Enable Account Remote Enable 3. Verify & Repair the WMI Repository