Set debug logging to see exactly what fails:
Win32_OperatingSystem lives in root\cimv2 . If your OMI client doesn’t specify the namespace, you’ll see no results. win32-operatingsystem result not found via omi
If this command succeeds, the issue lies within the application's configuration; if it fails, it confirms a network or permission block. or check specific WinRM configurations FortiSIEM AIO - Collector questions and WMI/OMI issues Set debug logging to see exactly what fails:
: Many users find that OMI fails with NTLM authentication. If possible, configure your collector or tool to use Kerberos-auth instead of NTLM. if it fails