Ensure that RPC/WMI ports (TCP 135 and the dynamic range 49152-65535) are open between the collector and the target.
Many users report that NTLM authentication frequently fails with OMI. Configuring your credentials to use Kerberos-auth instead can often resolve the "Result not found" error immediately.
On the target Windows machine, go to Security > Windows Firewall > Change Settings and ensure the Windows Management Instrumentation (WMI) exception is enabled. 3. Repair a Corrupted WMI Repository
If the OMI client cannot reach the WMI/CIM service, it will return an empty result or a timeout error.
The most common reason for "result not found" via OMI is an issue with how the collector authenticates with the target Windows server.
Ensure that RPC/WMI ports (TCP 135 and the dynamic range 49152-65535) are open between the collector and the target.
Many users report that NTLM authentication frequently fails with OMI. Configuring your credentials to use Kerberos-auth instead can often resolve the "Result not found" error immediately.
On the target Windows machine, go to Security > Windows Firewall > Change Settings and ensure the Windows Management Instrumentation (WMI) exception is enabled. 3. Repair a Corrupted WMI Repository win32operatingsystem result not found via omi new
If the OMI client cannot reach the WMI/CIM service, it will return an empty result or a timeout error.
The most common reason for "result not found" via OMI is an issue with how the collector authenticates with the target Windows server. Ensure that RPC/WMI ports (TCP 135 and the
Unlock unlimited access to all WTR content