System Center Operations Manager by Jonathan Hambrook

May 10, 2007

SCOM doesn’t pick up the Cluster Servers virtual devices

Filed under: Issues, Microsoft, SCOM 2007 — opsmgr @ 8:07 pm

Each physical node has to have “Agent Proxy” enabled (in the administration tab -> Agent managed)In case this was not set, restart the agent on each cluster node. The discovery reruns. Check now that each virtual node comes in under “agentless” managed. (in the discovered inventory it will show as “not monitored” which is ok)Now check under Windows Server (state view). Each virtual server has to be discovered. Check the properties, it has to say “Is Virtual Node” true. Now the SQL 2005 should work as well. Check the SQL state views (this may take a moment if the Virtual node was not discovered previously – again you can restart the agent on the cluster node where the SQL is currently active)

Here is a Step-by-step guide on exactly what to do.

  1. Open System Center Operations Manager Operator Console.
  2. Open the Administration view, and select Agent Managed under Device Management.
  3. Right-Click on the Cluster Nodes and select Properties.
  4. In the security tab tick the box that says Allow this agent to act as a proxy and discover managed objects on other computers.
  5. Click OK.
  6. On the Cluster Nodes restart the OpsMgr Health Service. (The Discovery will re-run)
  7. Open the Administration view, and select Agentless Managed under Device Management.
  8. You should see all the Cluster Virtual Servers.
  9. Open the Monitoring view, and select Discovered Inventory. It will show “not monitored” this is expected.
  10. Select Windows Server State under Microsoft Windows Server. (You should see the Cluster Object listed with their IP address).
  11. Right-Click the Cluster Virtual Servers select Properties.
  12. Check that the line saying “Is Virtual Node” is True (The SQL 2005 MP should work now)
  13. Select Database State under Microsoft SQL Server\Databases. (This may take a moment if the Virtual Servers were not previously discovered. You can re-start the OpsMgr Health Service where SQL is currently active to rescan).

Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Blog at

%d bloggers like this: