Child objects not UNdiscovering

Hello,

Below is a diagram depicting the [non-version specific] discovery mechanism associated with a handful of classes included in the SQL Server Management Pack.

In our environment, we control the deployment of application-level Management Packs by:

1. Creating a class-based override disabling each discovery targeting library classes such asWindows Computer; and

2. Creating a group containing a subset of Windows Computer objects to be targeted by the MP;

Note that the group membership is manually managed.

3. Creating a group-based override, targeting the group defined in #2 above, [re-]enabling each discovery targeting library classes such asWindows Computer.

The problem we are experiencing is that when an SQL installation is removed from a server, though theSQL Server Installation Seed object is undiscovered, the child objects are not. I would have expected to see the discovery also “undiscover” any child objects (ex.: SQL Server DB Engine) associated with recently purged targets (ex.:SQL Server Installation Seed).

Though I haven’t tested this, I strongly suspect that this behaviour would still exist despite the controlled MP deployment technique described above.

Any thoughts on what might be going on here are more than welcome.

Larry