OpsMgr R2 by Example: the Configuration Manager SP 2 MP

The Configuration Manager management pack adds support for monitoring Configuration Manager 2007 SP 2 in a 64-bit environment with Operations Manager 2007 R2 or Operations Manager 2007 SP 1 with hotfix (KB971541) installed. This enables the Configuration Manager 2007 SP 2 management pack to work with either the 32-bit or the 64-bit Operations Manager 2007 agent.

How to Install the Configuration Manager MP

  1. Download the Configuration Manager (ConfigMgr) management pack from the management pack catalog. The Configuration Manager 2007 Management Pack Guide is available on the same URL as the download and is labeled “CM07_OM07_MPGuide.doc”
  2. Review the Management Pack Guide – cover to cover. This document spells out some important pieces of information you will need to know.
  3. Import the Configuration Manager MP (using either the Operations console or PowerShell).
  4. Deploy the OpsMgr agent to all ConfigMgr servers.
  5. Enable Agent Proxy configuration on all ConfigMgr primary site servers. This is in the Administration node, under Administration -> Device Management -> Agent Managed. Right-click each primary site server, select Properties, click the Security tab, then check the box labeled “Allow this agent to act as a proxy and discover managed objects on other computers.”
  6. Create a ConfigurationManager_Overrides management pack to contain any overrides required for the MP.

How to Configure the Configuration Manager MP

After installing the Configuration Manager management pack, there is additional configuration and tuning to adjust management pack settings to your particular environment. Here is a list of configuration tasks for the Configuration Manager management pack:

Create groups needed for overriding targets with common requirements in your environment

As with other management packs, the groups needed for management pack tuning depend on the specifics of your deployment and the support model for your organization. As an example, a group of logical disks on Configuration Manager distribution point servers may require a lower threshold for disk space monitoring.

Configure Wake On LAN (WOL) performance monitoring rules

If WOL is in use in your Configuration Manager environment, you should enable monitoring of this feature. Several management pack rules, including performance measuring counters and rules monitoring the WOL feature, are disabled by default. To use the data collected by these rules, you must enable them by using overrides. WOL rules disabled by default in the Configuration Manager 2007 management pack include:

  • ConfigMgr 2007 Perf Threshold: Site Server Inbox WOLCMGR.box Backlog > 20 over 1 hour
  • ConfigMgr 2007 Perf Threshold: Site Server Inbox WOLCMGR.box\data Backlog > 100 over 1 hour
  • ConfigMgr 2007 Perf Threshold: SMS Wake On LAN Communication Manager Total Number of Packets Failed > 100 over 15 minutes
  • ConfigMgr 2007 Perf Threshold: SMS Wake On LAN Communication Manager Total Number of Requests Pending > 10,000 over 3 hours

Create custom Inbox monitoring rules

Most of the performance rules monitoring inbox backlogs have default thresholds of 10,000 messages for 3 hours. The threshold is not exposed as an overridable parameter in these monitors, meaning you must disable the monitor and create a replacement recurring threshold unit monitor with threshold, interval, and repeat count settings appropriate to the environment being monitored. This step is necessary only if the default thresholds are not acceptable for your environment. You can make this determination based on the normal levels in your specific environment, collecting and viewing data from inbox performance counters to better understand the performance baseline.

Configure sender connectivity monitoring

If the sender cannot connect to its parent site, status messages do not flow up the Configuration Manager hierarchy and the management pack does not generate an alert on those status messages. For these rules to work, create the %SMS_INSTALL_DIR_PATH% environment variable on your site server with the installation path previously specified for your site installation.

Configure Configuration Manager integration with Operations Manager

You can use the Configuration Manager console to configure how Configuration Manager responds during software distribution activities. These settings are not enabled by default.

  • Enable maintenance mode for Configuration Manager software distribution – When enabled, this allows Configuration Manager to enact the maintenance mode for the Operations Manager agent during software deployment operations.
  • Enable Operations Manager 2007 alerts if a Configuration Manager 2007 program fails to run – If enabled, this allows event logging resulting in alerts being raised in Operations Manager 2007 if a program fails to run.

Define the SMS environment variable to support log-based rules

A number of rules in the ConfigMgr management pack read Configuration Manager-based log files (sender.log, distmgr.log, and policypv.log) to check for errors. To monitor these logs, you must specify the location of the Configuration Manager installation folder by creating the %SMS_INSTALL_DIR_PATH% system environment variable on a site server. This enables the MOM/OpsMgr agent running under Local System or a local administrator user context to have access to the log files in the %SMS_INSTALL_DIR_PATH%\Logs folder.

Note that the %SMS_INSTALL_DIR_PATH% variable is not present on ConfigMgr systems by default. For the Operations Manager Health Agent to use this system environment variable, you may need to restart the Configuration Manager site server.

TIP: Steps for configuring system environment variables will vary by operating system. For detailed instructions on setting system environment variables on Windows 2008, refer to the system environment variable web page at http://technet.microsoft.com/en-us/library/cc772047.aspx.

Define Configuration Manager Admin UI variable to support console tasks

If the Configuration Manager 2007 console is collocated with an installation of the Operations Manager 2007 Operations console, the OpsMgr console will be able to launch the following Configuration Manager 2007 UI components, using the following console tasks presented in the Actions pane of the Operations console.

  • Resource Explorer
  • Configuration Manager console
  • Service Manager
  • Status Message

Define the SYSTEM Environment variable SMS_ADMIN_UI_PATH as the path to the folder containing the Configuration Manager 2007 console. A SMS_ADMIN_UI_PATH system environment variable is created to launch these applications. This environment variable points to the folder containing the Configuration Manager console, <ConfigMgrInstallationPath>\AdminUI\bin\i386 by default.

Note: The SMS_ADMIN_UI_PATH variable should be present on any system where the Configuration Manager console is installed. However, for the Operations Manager Health Agent to use this system environment variable, you may need to restart the system after completing the Configuration Manager console installation.

Enable general health monitoring

When enabled, general health monitoring for ConfigMgr servers is implemented through four unit monitors, all of which generate alerts when a health metric on a Configuration Manager server is above a certain threshold over a period of time. Here are the metrics checked by the unit monitors that implement general health monitoring:

  • Processor Time at 95% over 3 hours
  • Smsexec
  • Ccmexec
  • Total
  • Paging File Usage at 98% over 3 hours

General health monitoring in the Configuration Manager 2007 management pack is disabled by default. If desired, use overrides to enable these unit monitors:

  • ConfigMgr 2007 Perf Threshold – Paging File %Usage > 98% over 3 hours
  • ConfigMgr 2007 Perf Threshold – % Processor time(ccmexec) > 95% over 3 hours
  • ConfigMgr 2007 Perf Threshold – % Processor time(smsexec) > 95% over 3 hours
  • ConfigMgr 2007 Perf Threshold – % Processor time(_Total) > 95% over 3 hours

Disable unused performance and non-critical event collection rules

As mentioned in the previous discussion of the Active Directory management pack (http://tinyurl.com/ActiveDirectoryMP-ByExample), disable any non-critical collection rules in the Configuration Manager management pack to free up database space, bandwidth, and processor cycles

Tuning / Alerts to look for in the Configuration Manager MP

The rules and monitors generating false (or otherwise non-actionable) alerts will vary from one environment to another. For the alert rules mentioned here, the issues do not appear immediately after importing the management pack, rather over time during normal product use.

Alert: ConfigMgr 2007 Status: Distribution Manager failed to process a package.

Issue: The alert generated by this rule indicates that the Distribution Manager failed to copy a package from its source folder its destination folder on a distribution point. This is usually indicative of permissions on the folder, which can be resolved by granting permissions to the share for the server attempting to copy.

Resolution: Disabled due to false alerts which were generated from the management pack.

Alert: ConfigMgr 2007 Status: Distribution Manager does not have enough free disk space to copy a package.

Issue: The alert generated by this rule indicates that the Distribution Manager failed to copy a package from its source folder to its destination folder on a distribution point. This may indicate a true space issue, but can also be triggered by permissions on the folder, which you can resolve by granting permissions to the share for the server attempting to copy.

Resolution: Disabled due to false alerts which were generated from the management pack.

Thanks to Pete Zerger for his contribution to this posting.

Advertisements
This entry was posted in Tuning and Configuration. Bookmark the permalink.

One Response to OpsMgr R2 by Example: the Configuration Manager SP 2 MP

  1. Unknown says:

    Thanks for this, it\’s a big help! Can you tell me if there\’s any additional configurations required to monitor DCM? We have created a test CI which checks for a folder. DCM is monitoring this CI correctly and generates an alert when that folder is changed. But, the SCCM management pack is not picking up these alerts. 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