Updated OpsMgr 2007 R2 Management Pack
The System Center Team has released an update to the OpsMgr 2007 R2 Management Pack to resolve issues with Management Pack workflow detection, and to resolve issues around Agent process utilization.
From the download details:
“Feature Summary
The Operations Manager 2007 R2 Management Packs includes the following features:
- Local and Remote Monitoring of an Agent’s Health
- Operations Manager agents monitor themselves for events and performance indicators that signal an issue with the agent’s health.
- Management servers also maintain an external perspective of an agent’s health via the Health Service Watcher.
- The ‘Agent Health State’ view provides a side-by-side dashboard of both perspectives on the agent.
- Optional, Automatic Agent Remediation Capabilities
- If the Health Service Watcher determines that an agent is unhealthy, a series of diagnostics and recoveries can be enabled to further diagnose the problem and event take actions to attempt to fix the problem (e.g. Ping the server to see if it is completely offline, start a stopped agent, trigger a reinstall, etc.). Refer to the management pack guide for more details.
- Agents are monitoring their own process to ensure that memory utilization is not sustained at unacceptable levels. If this condition is detected then the agent will automatically restart itself to force the freeing up of memory.
- Detection of Problems and Misconfigurations with Run As Accounts and Profiles
- Checks are run on a regular basis to detect if any of the management group’s “Windows” type Run As Accounts have credentials which are about to expire. Alerts will be raised, and where possible this will be done in advance of the credentials expiring to avoid outages.
- Alerts will be raised if any errors are encountered during the distribution of Run As Accounts.
- Monitoring of problems with Running Workflows in Management Packs
- Numerous rules are provided to detect if workflows within management packs are failing. Examples of workflows include discoveries, rules, monitors, etc. Failures can range from bad configurations on the workflows themselves, script failures, permissions problems, etc.”