Here’s an issue we ran into the other day that you might want to be aware of. If a Cluster has orphaned object entries in ClusterHive registry key, the System Center Operations Manager agent may not discover some or all Cluster resources. This can occur with System Center Operations Manager 2007 (OpsMgr 2007) or System Center 2012 Operations Manager (OpsMgr 2012).
IF you take a TracingGuidsNative.log verbose OM ETL Trace (see
) you will see evidence of this via this string in the trace:
Some of the Virtual server critical (or key) properties is (are) NULL.
To resolve this issue we simply need to delete these orphaned resources and/or groups. First, use the Failover Cluster PowerShell commands
to get the list of Resources and Groups. Then, using the output, check for Resources/Groups that appear as Offline and verify if these can be seen in the Failover Cluster Console. Verify with the Cluster administrator whether these are still valid, then assuming they are not and you’ve identified which ones that are orphaned, delete them using these commands from an elevated CMD Prompt (Run As Administrator):
For orphaned resources:
Cluster RES "
For orphaned groups:
Cluster GROUP "
Once this is done the missing cluster resources should now be discovered.
Mihai Sarbulescu | Support Escalation Engineer | Microsoft GBS Management and Security Division