I have a SCOM 2007 Exchange 2003 question that I cant find an answer to. I see in multiple walkthroughs that Allow this agent to act as a proxy and discover managed objects on other computers SCOM 2007 setting HAS to be enabled on all Exchange 2003 managed agents but I dont see anywhere WHY this is required. Not the help files, not the google, not the experts-exchange&Im about to go to Barnes and Noble and buy a book on SCOM but before I did that, I thought Id ask the 'Experts'.
Enable Agent Proxy configuration on all Exchange Servers identified from the groups. This is in the Administration node under Administration -> Device Management -> Agent Managed. Right-click on each domain controller, select Properties, then the Security tab, and check the box to Allow this agent to act as a proxy and discover managed objects on other computers. This has to be done for EVERY EXCHANGE SERVER, even if the server is added after your initial configuration of OpsMgr.
And in this article, it associates this setting to enabling Exchange Topology Discovery:
Enable Agent Proxy configuration on all managed Exchange servers. In the Administration pane, under Administration, Device Management, Agent Managed, right-click on each Exchange server, select Properties, then the Security tab (Figure 1), and check the box Allow this agent to act as a proxy and discover managed objects on other computers. This step will also make exchange cluster instances to appear in the Agentless Managed section.
Im looking at this because I have an environment that has disabled all Mail Flow SCOM 2007 monitoring of their exchange 2003 servers because of the deluge of meaningless notifications they were receiving and this little setting is NOT currently applied to their exchange server SCOM agent settings. So before I just toggle it on to see if it has some connection with the mail flow notification deluge, Im looking for some reason for the setting in the first place&