On the Windows machine running the OMI server (omi service), open /etc/opt/omi/conf/omiserver.conf and ensure:
# Allow WMI bridging (default should be true)
enableWMI = true
The OMI client library (e.g., omicli, or Python's pyomi) may be using a different CIM schema binding. Some OMI clients cache the CIM schema and, if outdated, may not recognize newer or specific classes.
If you can’t fix the OMI provider issue, retrieve the same OS information via a different CIM class known to work — or fall back to a shell command through OMI’s execute functionality:
omicli invoke root/cimv2 Win32_Process Create findstr /B /C:"OS Name""
Not elegant, but effective in a pinch.
By systematically going through these steps, you should be able to identify and potentially resolve the issue with the Win32 operating system not being found via OMI.
Win32-operatingsystem Result Not Found Via Omi
On the Windows machine running the OMI server (omi service), open /etc/opt/omi/conf/omiserver.conf and ensure:
# Allow WMI bridging (default should be true)
enableWMI = true
The OMI client library (e.g., omicli, or Python's pyomi) may be using a different CIM schema binding. Some OMI clients cache the CIM schema and, if outdated, may not recognize newer or specific classes. win32-operatingsystem result not found via omi
If you can’t fix the OMI provider issue, retrieve the same OS information via a different CIM class known to work — or fall back to a shell command through OMI’s execute functionality: On the Windows machine running the OMI server
omicli invoke root/cimv2 Win32_Process Create findstr /B /C:"OS Name""
Not elegant, but effective in a pinch.
By systematically going through these steps, you should be able to identify and potentially resolve the issue with the Win32 operating system not being found via OMI. Not elegant, but effective in a pinch