Upon upgrading to Service Pack 1 for SC Operations Manager 2007, I began receiving the following alert:
Alert: Agent proxying needs to be enabled for a health service to submit discovery data about other computers.
Source: scom1.
Path: scom1.
Last modified by: System
Last modified time: 3/6/2008 2:32:21 PM
Alert description: Details:Health service ( 93A0E708-5148-5975-BD36-373E8E5A1610 ) should not generate data about this managed object ( F227C8F1-E50E-F847-9378-45EB7135B901 ).
The problem with this Alert (which appears to be new in SP1), is that your RMS is reported as the source server, when in fact there is another Agent throwing the error (in our case, Agent Proxying is already enabled on our RMS). I found the following blog post from Marius Sutara at Microsoft that explaining that performing the following SQL query on your OperationsManager database will show you which managed Agent is throwing the error:
SELECT * FROM BaseManagedEntity WHERE BaseManagedEntityId = '<GUID>' <- Where <GUID> is the "managed object" GUID reported in the OpsMgr alert (the second GUID listed)
In our case this returned a single row, and I was able to determine the problem Agent by looking at the Path field.