Windows Pattern Discovery may discover MID server host itself instead of target server if the first WMI query fails in the pattern


Description

Observed issue:
Windows Pattern Discovery may discover MID server host itself instead of target server if the first WMI query fails in the pattern. The target's CI will be updated with attribute values of the MID Server host. The issue might happen intermittently depending on the WMI query performance in the environment.

The issue may appear as:
In Pattern log a step "Get hostname and domain from registry" fails to query target with error "The RPC server is unavailable."

Then in the following steps the Windows queries would run against the MID server host itself. e.g. "Get data from Win32_ComputerSystem" would retrieve the name as the MID server host name.

In a successful Discovery the query result would be consistent.

Steps to Reproduce

  1. Run an affected discovery schedule.

In a Lab environment, one way to reproduce is to add a delay to the stderr processor (via a custom jar) so that the credential test succeeds even though the credential is invalid.

Workaround

This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

As a workaround, temporarily import and commit the attached Update Set for New York or Paris releases.

A limitation of the workaround is that MID server cannot discover its own host, but other MID servers can discover it.


Related Problem: PRB1436701