JAMA00

SCOM 2007 R2

Setting agent proxying

Posted by MarcKlaver on January 21, 2010

Several management pack (if not all) require you to change the security settings for the agent to allow the agent to act as a proxy:

proxysetting

We are using a slightly modified version of the Operations Manager Support Team blog script, which will enable this setting, based on a class name. We run this script on a daily basis.

But then the question is: How do I know which class I can use.

When an agent does not have the proxy setting enabled (but should) an alert is generated on the management server and looks like this:

image

 Note: We have lowered the severity to warning instead of the default critical.

In the “Alert Description” you can find which management pack wants the proxy setting enabled (Microsoft Windows DFSReplication is this example). When you export this management pack to xml, you can retrieve the required class.

For our production environment we have now enabled agent proxying for these classes:

#——————————————————————————-
# Citrix servers for zone data collection.
#——————————————————————————-
Citrix.PresentationServer.ServerRole

#——————————————————————————-
# Cluster nodes.
#——————————————————————————-
Microsoft.Windows.Cluster.Node
Microsoft.Windows.Cluster.Service

#——————————————————————————-
# DFSReplication service
#——————————————————————————-
Microsoft.Windows.DfsReplication.Service

#——————————————————————————-
# DNS Server 2003
#——————————————————————————-
Microsoft.Windows.DNSServer.2003.Server

#——————————————————————————-
# DNS Server 2008
#——————————————————————————-
Microsoft.Windows.DNSServer.2008.Server

#——————————————————————————-
# Exchange 2003 Servers
#——————————————————————————-
Microsoft.Exchange.ServerRole.2003

#——————————————————————————-
# Exchange 2007 discovery helper.
#——————————————————————————-
Microsoft.Exchange2007.Component.DiscoveryHelper

#——————————————————————————-
# ISA server 2006
#——————————————————————————-
Microsoft.ISAServer.2006.Firewall.ServerRole

#——————————————————————————-
# NLB windows 2008.
#——————————————————————————-
Microsoft.Windows.NetworkLoadBalancing.2008.ServerRole

#——————————————————————————-
# SMS 2003
#——————————————————————————-
Microsoft.SMS.2003.Microsoft_SMS_2003_Providers_Installation
Microsoft.SMS.2003.Microsoft_SMS_2003_Site_Database_Servers_Installation

#——————————————————————————-
# System Center Configuration Manager 2007
#——————————————————————————-
Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Providers_Installation
Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Primary_Site_Servers_Installation
Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Database_Servers_Installation

Advertisements

6 Responses to “Setting agent proxying”

  1. MarcKlaver said

    Added SSCM 2007 and SMS 2003 classes

  2. Marty said

    Great info, thanks for sharing. What are the reasons that you don’t just enable it for all agents? Are they technical reasons or more security related?

    • MarcKlaver said

      The same reason why this settings is disabled by default: security.
      But then again if so many agents need this setting, what security will it provide? So you could opt, for just enabling it for all agents.

  3. […] now we have set the Agent proxy for an agent only when required and we used a script to do this. See this link for more information. But now Microsoft has come up with something new in the Exchange 2010 management pack. It will not […]

  4. Dominique said

    Great thanks

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s

 
%d bloggers like this: