Agent proxying needs to be enabled for a health service to submit discovery data about other computers.
Hi, I got an error from our management server: Agent proxying needs to be enabled for a health service to submit discovery data about other computers. Details:Health service ( 99BF733C-5161-54BE-77EE-D62D1BB1075C ) should not generate data about this managed object ( 7C08BD1F-1103-B8A8-7C13-4AEA9C654A37 ). I run this query: select * from basemanagedentitywhere basemanagedentityid = '7C08BD1F-1103-B8A8-7C13-4AEA9C654A37' The result set was empty (now row). I expected that proxing should be enabled on a management server. I used the ProxySettings tool from http://blogs.msdn.com/boris_yanushpolsky/archive/2007/08/02/enabling-proxying-for-agents.aspxand found two servers with enabled proxing as expected (the management server and a second server). What can I do? Thanks.
December 3rd, 2008 12:20pm

Hi odo, Try to run this query: select * from basemanagedentitywhere basemanagedentityid = '99BF733C-5161-54BE-77EE-D62D1BB1075C ' Is there any result?
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2008 1:41pm

Hi, yes there is an result. SERVER1 is our DC. Every value represents one column (I pasted it transposed for better reading): 99BF733C-5161-54BE-77EE-D62D1BB1075C 113AB4C891F-3359-3FB6-0704-075FBFE36710Microsoft.SystemCenter.HealthServiceERVER1.domain.comSERVER1.domain.comNULLSERVER1.domain.comB640A056-5AA7-40E8-1194-F87F164064081039762,8390339762,83774 Regards.
December 5th, 2008 2:47pm

Hello Odo, OK you used the query correctly and see that Proxying needs to be enabled on the SERVER1. Domain controllers must always have the Enable Proxy setting turned on so this is expected. Can you see what the proxy setting is on the SERVER1 computer? If it is not turned on, just check the box in the properties of the SERVER1 Agent (Administration space in the OpsMgr console) to enable that server to discover (proxy for) other computers. Good luck, John Joyner MVP-OM P.S. You can also use PowerShell to get this information, here is the cmdlet to run: (replace the GUID with your own) Get-MonitoringObject -id:'d6acc586-43d1-581d-b007-5cdd5cbd4003 ' | ft DisplayName
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2008 7:13pm

Hi, I didn't know that a dc should be act as proxy. So we have two domain controllers, do I have to enable on both proxy setting? Why do I have to enable it (for understanding)? Does this proxy service needs some resources of my dc? Thanks. Regards.
December 5th, 2008 7:32pm

Hi odo, Agent proxying needs to be enabled when health service discovers instance of some managed entity type for which management context doesnt provide information that this exact health service will also monitor this instance. For example proxying must be enabled when discovering instances of Virtual Server on cluster nodes (instance of Virtual Server will be managed by health service running on active cluster node where matching cluster resource group resides); it should be enabled for AD topology discovery etc. Failure to insert discovery data when proxying was required was always present, but with SP1 release of Operations Manager 2007 we added alert that notifies operator. This alert should help to distinguished if it is desired to insert discovery data after inspecting alert context. You can try the following steps to enable the agent proxy on Server 1: 1. In SCE console, go to Administration space. 2. Click agent managed, right click the agent and choose "properties". 3. In security tab, choose "Allow this agent to act as a proxy......."
Free Windows Admin Tool Kit Click here and download it now
December 8th, 2008 12:50pm

Hi,I enabled proxying on the both domain controllers.Thanks.odo
December 15th, 2008 3:01pm

Hi,My SCE 2007 tells me that on my Management Server , called SCE, the agent proxying should be activated. But It is not possible to activate it for the management server. Is there another way how to activate this proxy function on the management server itself?
Free Windows Admin Tool Kit Click here and download it now
August 25th, 2009 1:42pm

Hi, Take a look at this post http://blogs.technet.com/kevinholman/archive/2008/06/27/a gent-proxy-alerts-finding-the-right-machine-to-enable-agent-proxy-on-usin g-a-custom-report.aspx -- Anders BengtssonMicrosoft MVP - Operations Managerwww.contoso.se
August 25th, 2009 4:05pm

hi there: i don't think this is a hijack, but i have a question about this: using the method described above, i've been able to identify the machine that supposedly needs proxying enabled. but, it's just one of the clients on the network. just a plain old wxp client. i don't believe that i should need to enable proxying on one client out of our whole domain. does anyone have any insight on this? thx!
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2009 12:16am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics