Then I looked in event viewer in for "Operations Manager" and found this:
Event Type:    Error
Event Source:    OpsMgr Connector
Event Category:    None
Event ID:    20022
Date:        3/18/2010
Time:        7:00:47 AM
User:        N/A
Computer:    SR-SCOM
Description:
The health service {946C21D2-EA1B-389F-18C3-9B05993AD67B} running on host SRV03-09.mydom.local and serving management group Alf_SCOM with id {FAF2CEFC-EDC7-8CB9-913C-2E407DB699DD} is not heartbeating.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 

This happens for all my servers.

Any reason why the agent is not hearbeating?

There are some short videos on SLD 2.0 to get you up and running quickly

System Center Operations Manag…Dashboard part 2, Installation

ystem Center Operations Manag…ashboard part 3: Configuration

• ConfigMgr 2007 (SCCM)
• DPM 2007
• DPM 2010
• OpsMgr 2007 (SCOM)
• SCE 2007 / 2010 (Essentials) 
• SCVMM / Hyper-V
• Miscellaneous

ConfigMgr 2007 (SCCM)

• Using Powershell with Configuration Manager 2007 (Part 1)
• Using Powershell with Configuration Manager 2007: Part 2 – Manipulating Client Behavior
• How to list and query for installed hotfixes with PowerShell
• PowerShell to change ConfigMgr Client Cache size
• SCCM 2007: How to monitor inboxes in Configuration Manager 2007 using Powershell

 Top of Page

DPM 2007

• SQL Recovery Point Restore Script for SCDPM
• CLI Script: Manual detailed inventory of unknown tapes
• CLI Script: Run consistency check on invalid datasources
• CLI Script: Force mark tape as free
• CLI Script: Recover to latest point in time for a SQL DB
• CLI Script: Copy latest point in time of SQL DB to a folder
• DPM CLI: Quick reference help
• DPM CLI Scripts
• CLI: Grow your replica and shadow copy volume sizes automatically!
• CLI Script: Job object fundamentals
• CLI: Create new Recovery points on tape for all datasources in a PG
• CLI script: Create protection groups for Disk based backups
• DPM CLI> Hello World
• DPM CLI Tips 'n Tricks: Powershell Basics
• DPM CLI Tips 'n Tricks: Powershell Basics - Part II
• DPM PowerShell Script -- invoking a Consistency Check
• DPM 2007 Share Restore Recovery Point Script
• DPM 2007 Individual File Share Recovery Point Script

Top of Page

DPM 2010

• SQL Self Service Recovery using DPM 2010

Top of Page

OpsMgr 2007 (SCOM)

• Uninstall Multiple Management Packs including Relationships - PowerShell Script
• OpsMgr: Finding Grey Agents with Powershell
• Most Common Alerts Report (rule and monitor generated) with Powershell
• OpsMgr: Managing Global Settings from PowerShell
• OpsMgr Powershell: Reset monitoring state of closed alerts in ...
• A PowerShell script for resetting state of "manual reset" monitors
• Powershell: Get View display properties from UserRole
• OpsMgr: Recurring Agent Proxy Bulk Update for a Group of Computers
• Working with Active Alerts in OpsMgr 2007
• Powershell Tip: Removing Discovery Data in Operations Manager 2007 SP1
• How to create a PowerShell task for OpsMgr using the Authoring Console
• Powershell: OpsMgr Alert-to-Speech (cool idea from Gary Broadwater ...
• Automatically Starting Maintenance Mode When Servers are Rebooted
• Put any object type in maintenance mode in OpsMgr using Powershell 

Automating Agent Discovery and Failover Configuration

• How to Schedule OpsMgr Discovery and Agent Deployment without AD
• How to automate daily discovery and agent installation in OpsMgr
• OpsMgr 2007: Updating Primary and Failover Mgmt Server settings
• Powershell: Updating Proxy Agent for Multiple SNMP-enabled Devices ...

OpsMgr Groups

• Group members via PowerShell
• Create OpsMgr Groups in PowerShell from Excel File
• OpsMgr: Listing all OpsMgr groups for which a computer is a member

Series: Exploring OpsMgr Class Lineage

• Part 1 - OpsMgr 2007: Exploring Class Lineage in Powershell
• Part 2 - OpsMgr 2007 - Exploring Class Lineage in Powershell: Recursive Enumeration
• Part 3 - OpsMgr 2007 - Exploring Class Lineage in Powershell: Relationships
• Part 4 - OpsMgr 2007 - Exploring Class Lineage in Powershell: Recursive Enumeration of Classes and Relationships
• Part 5: OpsMgr 2007 and Powershell and the SDK – What MP does this class come from?

Series: How to create two-state monitors in OpsMgr with R2 PowerShell modules

• How to create a Two-State PowerShell Script Monitor using the Authoring Console (Part 1)
• How to create a Two-State PowerShell Script Monitor using the Authoring Console (Part 2)
• How to create a Two-State PowerShell Script Monitor using the Authoring Console (Part 3)
• How to create a Two-State PowerShell Script Monitor using the Authoring Console (Part 4)

Top of Page

SCE 2007 / 2010 (Essentials) 

• SCE 2007 Custom Command Shell

Top of Page

SCVMM / Hyper-V

• Create VM from Template SCVMM Powershell Script
• VMM2008 - P2V Script
• VMM2008 - Add New Host Script
• Hyper-V Host & Guest Maintenance Script
• Create VM from Template SCVMM Powershell Script

Miscellaneous

• Recursively Delete Read Only Directories, Subdirectories and Files with No Prompt in Powershell
• PowerShell: How to a remote SQL database and retrieve a data set
• Powershell Script to Reboot a List of Computers in a Text File

Cheers,

Shaun 

Do you have any info/experience on this .

Thank

Gateway Server Role Scenario

The Gateway Server role allows the Discovery Wizard in Operations Manager to discover target computers in workgroups, across one-way trusted and untrusted domains, and provides communication between the target computer and the Management Server. The security requirements of Operations Manager 2007 also bring PKI into a prominent role in many environments where it is has previously been underutilised or non-existent.

There are two primary goals for the gateway server:

1. Minimize the number of points of traffic between two secured environments, (for example, a Customer and Service Provider network)

2. Maximize the use of Kerberos based authentication when it is available, because the TCO associated with Kerberos is lower than with certificates.

Operations Manager introduces a more secure communication model than in its previous versions in that mutual authentication is now required by default between an agent and a management server, as well as between Gateway Servers and Management Servers.

Mutual authentication can be achieved via Kerberos in trusted scenarios where all machines are in the same Active Directory domain or in a domain with a two-way trust relationship. However, in cases where machines outside the trusted environment must be monitored, Kerberos authentication is not possible. In these cases, Operations Manager 2007 can utilize x.509 certificates for mutual authentication in a variety of scenarios. Certificates can be deployed to any Windows operating system that supports an Operations Manager 2007 agent.

The Gateway facilitates communication between the target agent-managed computers and a Management Server, easing management in un-trusted and distributed environments. It may be easiest to think of a Gateway as a management server that simply relays information received from agents to another management server. In real terms a gateway is effectively a management server without direct database access. When you approve a gateway, it appears as a management server in the Operations Console.

To ensure high availability, the Gateway Server on the customer site can be implemented with a secondary gateway to allow agents to failover in the event of the primary gateway becoming un-available also a gateway can be configured for failover to both a primary and secondary management server on the service provider side, allowing Gateway communication to continue in the event of a Management Server failure. The Gateway Server also does not require membership in an Active Directory domain, so it is perfect for the typical service provider scenario where quite often a customer site is separated from the Service Provider by some kind of security boundary. Alternatively, agent-managed computers can be configured to communicate directly to a management server while authenticating via certificates, this is suitable where you have a very small number of agents or where implementation of a Gateway Server is not possible.

Common Deployment Scenario for Multi Tenant Environments.

Gateway with Agent-managed Member Servers

In this scenario, monitoring of a remote, un-trusted AD domain is desired. All servers desired for management in the remote domain are members of the same AD domain as the Gateway Server. There is no trust relationship between the two domains. In this scenario, certificate authentication will be required only between the management server and gateway server, as no trust relationship exists. Agent-managed computers in the remote AD domain will be authenticated via Kerberos for communication with the Gateway Server. Thus, certificates must be secured for both the Management Server and Gateway Server in the remote domain.

Gateway with Agent-managed Workgroup Servers

In this scenario, monitoring of a remote, un-trusted AD domain is desired. Some servers desired for management by the Gateway Server are members of a workgroup. In this scenario, certificate authentication will be required not only between the management server and gateway server, but also between the Gateway Server and agent-managed computers. 

Agent-managed Workgroup Servers - Gateway in Workgroup

In this scenario, monitoring of a remote, DMZ or workgroup environment is desired. An additional requirement to minimize the number of points of communication between the isolated environment and the Management Server exists, making deployment of a Gateway Server an appropriate choice. In this scenario, certificate authentication will be required not only between the management server and gateway server, but also between the Gateway Server and agent-managed computers. 

While there is no programmed limit for the number of agents that can be managed within a single Management Group, information from live environments has established certain limits. Performance has been shown to degrade beyond 6,000 agents, so you should always plan for one Management Group for every 6,000 agents.

The official supported limit for the number of agents that can communicate to a gateway server is 1,500. 

Connected Management Groups Scenario

This deployment scenario is comprised of multiple management groups, each of which can be of the single or multiple server configurations type. This deployment scenario is exceptionally flexible and is mostly used to provide monitoring, alerting, and reporting services in complex environments.

This is extremely useful in the service provider scenario as it allows the connection to multiple instances of a Management Group that may exist on customer sites providing a "single pane of glass" for viewing critical alert data.

Connecting management groups offers these additional services:

• Consolidated monitoring and alerting for greater than 6,000 agents
• Consolidated monitoring across trust boundaries

Operations Manager 2007 Server Roles

This configuration supports all Operations Manager server roles and makes use of the Operations Manager Connector Framework to enable bidirectional communication between the connected groups and local groups.

Common Uses

This deployment scenario can be used when the service provider requirement is to link to a complete Operations Manager Management Group on a customer site to allow a consolidated view of all monitored activity and consolidated management of that data.

There is no official limit on the number of Management Groups that you can connect to in this scenario.

High Level Architecture for Mixed Multi-Tenant Environment

In the case of many large service providers quite often the environment would be a mix of both connected and non-connected management groups, therefore a tiered architecture would be suitable.

This may consist of a master Management Group (or Local Management Group) which would host a roll up of alerts from all connected management groups and second management group which would be the collection point for all data from non-connected Management Groups.

Data Warehouse collection at the Master Management Group level would consist of purely Alert and Discovery Data and this would be the primary connection point for other Management Tools or any Ticketing System, this would also provide a high-level, global data collection point for customer facing scorecarding and reporting.

Any customer owned Management Groups would connect directly to this tier via the Microsoft Connector Framework (MCF), with performance and inventory data being collected locally on their sites.

A Second Management Group would be implemented as a connection point for any non-Management Group sites which would have local Gateway Servers for relaying data from local agents, this Management Group would also be connected to the Master Management Group via the MCF. This second tier would have Data Warehouse Collection Capabilities for Performance Metrics and Inventory Data and would provide a second data collection point for customer facing scorecarding and reporting.

 The following diagram shows an example of how this architecture may look:

Connecting to other Management or Helpdesk Ticketing Systems

The Operations Manager 2007 R2 release saw the introductions of a number of free Interoperability connectors, these include HP Openview, Tivoli TEC, Remedy Helpdesk and a universal connector.

With the recent acquisition of Opalis Integration Center by Microsoft a number of other connection options have been added to the product such as Omnibus Netcool and HP Service Center.

Microsoft also has a close collaboration with EMC around the SMARTS network management toolset, which includes the purchase of some of the EMC SMARTS IP for addition to the next version of the product.  This collaboration has led to a recent release of a a bidirectional adapter package from Microsoft called the EMC Smarts Connector for Microsoft System Center Operations Manager 2007. The adapter will let Operations Manager users view Smarts topology and root-cause reports using their own interfaces. Smarts will also be able to suck in data from Operations Manager.

Operations Manager also comes with an extensive SNMP Trap collection feature allowing you to receive traps from any SNMP enabled system as well as being able to probe other systems ( via SNMP) for information.

Management Escalation

Operations Manager 2007 has a very extensive and flexible subscription based notification system which supports output to SMTP enabled mail systems, Microsoft Office or Live Communication Server (for delivery of messages to Office Communicator clients), GSM for SMS Text Messaging integration via a suitable GSM enabled device, as well as any command line supported medium.

This subscription mechanism supports a very granular and targeted alert stream, allowing you to alert down to a single object or alert over a variety of parameters (such as time raised, severity, business priority etc.).

Operations Manager also supports Alert Ageing which allows you to put a time expiry on un-answered alerts meaning that you can escalate them to higher tiers of Management or too other Operators.

Hardware Support for All Platforms

Microsoft has full support for Operations manager 2007 from most of the large Hardware Vendors such as HP, Dell, Fujitsu Siemens and IBM. Each of these vendors provide a full Operations Manager 2007 management Pack which typically integrates with the local hardware agent and contains Vendor specific knowledge in alerts generated.

Role based administration

Operations Manager 2007 can monitor many different types of applications in the enterprise and these applications can be administered by multiple teams. As the Operations Manager administrator, you can limit access to each team so they access only their monitoring data. Role-based security allows you to grant access to monitoring data, tools, and actions on a team-by-team basis.

Except for the Administrator role, you can add Active Directory security groups or individual accounts to any of these predefined roles. You can add Active Directory security groups only to the Administrator role.

Adding users or groups to a role mean that those individuals will be able to exercise the given role privileges across the scoped objects (including any inherited objects).

Operations Manager also allows you to create custom roles based on the Operator, Read-Only Operator, Author, and Advanced Operator profiles. When you create the role, you can further narrow the scope of groups, tasks, and views that the role can access. For example, you can create a role entitled "Exchange Operator" and narrow the scope to only Exchange-related groups, views, and tasks. User accounts assigned to this role will only be able to run Operator-level actions on Exchange-related objects.

Measuring and Displaying Customer Service Levels

One of the most challenging aspects of providing a managed service to a customer is being able to visualise the value of the service you are providing back to the customer in a format that can be consumed and understood by  any level of the business.

Operations Manager 2007 delivers the ability to define an IT service (or distributed application) by selecting the components that together deliver that IT service, along with their inter-relationships. For example, a web service may comprise of the web server, application pools, a database, and the servers that each are hosted on.  By monitoring a defined number of characteristics of each of those components, Operations Manager is able to determine both the health and performance of each component through 3 states:

• Healthy, indicating that the component being monitored is operating within expected parameters.
• Warning, indicating a performance or health threshold has been exceeded, and that while the component is operating, attention is required to prevent service disruption or restore performance.
• Critical, indicating that the component being monitored has entered an unhealthy state that requires immediate attention, and that the availability and performance of that component are compromised.

This feature is one of the most powerful features of Operations Manager as it gives the ability to be able to group together all of the components that make up a service and in the event of an outage very quick root cause analysis of the source of an outage of performance problem can be identified by simply clicking on a problem path button.

This is also extremely useful to the service provider as it gives him the ability provide metrics back to the customer on the core services that he is being paid to manage through Operations Manager 2007 R2's in built Service Level Reporting capability.

The Service Level Reporting capability in Operations Manager 2007 R2 (also called "service level objectives" or SLOs) leverages this same functionality maintained in the Distributed Application concept to determine both availability and performance metrics for monitored IT services. It does this by calculating the overall time that the components that comprise that IT service remain in a particular state to arrive at the following metrics:

• Availability, calculated as the time the components that comprise the service are in a healthy or warming state. Only a critical state counts against the availability metric, since even if it is in a warning state the IT service is seen as being accessible by end users, (e.g., a web service may take a long time to respond, but it does eventually deliver a web page).
• Performance, calculated as the time the components that comprise the IT services are in a healthy state. Both warning and critical states count against the performance metric, (e.g., if a database transaction is expected to complete in less than 300ms, and the actual transaction takes 2 seconds, then this will be seen as a performance impact).

Once you have defined your Distributed Applications and Service Level Objectives you can use the in-built Service Level Report to display the results or can display the data in a much more effective format using the Service Level Dashboard.

The Service Level Dashboard for Operations Manager R2 is a free download from the Microsoft Solution Accelerator team which is an application built on Windows SharePoint Services 3.0. It is designed to work with an existing Operations Manager 2007 R2 infrastructure configured to monitor business-critical applications. The dashboard evaluates an application or group over a time period that the administrator selects during setup, determines whether it met the defined service level commitment, and displays summarized data about the service levels.

In Operations Manager 2007 R2, you define your service goals. The Service Level Dashboard evaluates each SLO over the defined dashboard time period and determines if it met the goal during that period. The dashboard displays each SLO and identifies its states, based on defined service level targets.

The following diagram illustrates, at a high-level, the process flow that occurs within the Service Level Dashboard environment:

The Service Level Dashboard integrates with the Operations Manager Data Warehouse database and displays service level metrics on the Windows SharePoint Services interface. All the customized and personalized data associated with the Web Parts of the Service Level Dashboard is stored in the Windows SharePoint Services Content database.

The dashboard can summarize the current status and health of all defined SLOs against an application or group of objects. Key measures used to evaluate various aspects of the health of defined SLOs include such information as service level metrics, mean time to repair (MTTR), mean time between failures (MTBF), and service level trends.

As this Dashboard can be used in SharePoint or WSS, it can easily be imported into a public facing portal for on-line consumption by the customer.

Custom SLA Scorecarding

As the needs of the Service Provider often varies from some of the functionality that is provided from Operations Managers "out-of-the-box" availability and SLA Reporting, there is often a need to publish key data collected from Operations Manager in executive level dashboards and scorecards to give customers a "10,000" feet view of their environment so they understand the value the service provider is bringing in managing their infrastructure also key performance metrics can be presented allowing IT stakeholders within those businesses to make key decisions without the complication of having to run their own reporting infrastructure.

This extra level of reporting can easily be provided through extending Operations Managers reporting capability to utilise some of the new, native SQL 2008 reporting capabilities.

By using some of the new reporting controls now in SQL 2008, very effective, customer ready scorecards can be created which can easily be tied to an individual customer by using a combination of

Gordon McKenna - System Center Operations Manager MVP

Technical References:

Gateway Server and Certifcate-based Authorization Scenarios in Operations Manager 2007: http://www.systemcentercentral.com/Downloads/DownloadsDetails/tabid/144/IndexID/7885/Default.aspx

Tracking Service Levels with Operations Manager 2007 R2: http://download.microsoft.com/download/9/B/4/9B4829DC-55A5-46E7-9C9A-91B49EBB6320/SC_OpsMgr2007_R2-ServiceLevelMonitoring.pdf

Service Level Dashboard for System Center Operations Manager 2007: http://technet.microsoft.com/en-us/library/dd630553.aspx

I remember having the same issues a while back and this solved it.

Let me knowhow you get on,

Gordon

I am not aware of anyway to migrate these,

Sorry I do not have better news :-(

Gordon

Part 1: Create an MP that extends an existing class with a location attribute

Part 2: Write a connector using the OpsMgr SDK

Part 3: Use the location information with Live Maps to create dymanic views

Returning Resultant Set of Rules in Ops Mgr 2007

PS Monitoring:\> $sample2 | Get-Member


   TypeName: Microsoft.EnterpriseManagement.Monitoring.MonitoringPerformanceDataValue

Name                            MemberType Definition                                                       
----                            ---------- ----------                                                       
Equals                          Method     System.Boolean Equals(Object obj)                                
GetHashCode                     Method     System.Int32 GetHashCode()                                       
GetType                         Method     System.Type GetType()                                            
get_Id                          Method     System.Guid get_Id()                                             
get_ManagementGroup             Method     Microsoft.EnterpriseManagement.ManagementGroup get_ManagementGr...
get_ManagementGroupId           Method     System.Guid get_ManagementGroupId()                              
get_MonitoringPerformanceDataId Method     System.Int32 get_MonitoringPerformanceDataId()                   
get_SampleValue                 Method     System.Nullable`1[[System.Double, mscorlib, Version=2.0.0.0, Cu...
get_TimeAdded                   Method     System.DateTime get_TimeAdded()                                  
get_TimeSampled                 Method     System.DateTime get_TimeSampled()                                
Reconnect                       Method     System.Void Reconnect(ManagementGroup managementGroup)           
ToString                        Method     System.String ToString()                                         
Id                              Property   System.Guid Id {get;}                                            
ManagementGroup                 Property   Microsoft.EnterpriseManagement.ManagementGroup ManagementGroup ...
ManagementGroupId               Property   System.Guid ManagementGroupId {get;}                             
MonitoringPerformanceDataId     Property   System.Int32 MonitoringPerformanceDataId {get;}                  
SampleValue                     Property   System.Nullable`1[[System.Double, mscorlib, Version=2.0.0.0, Cu...
TimeAdded                       Property   System.DateTime TimeAdded {get;}                                 
TimeSampled                     Property   System.DateTime TimeSampled {get;}                               

 

I wonder if there is a way to do a reverse lookup using the MonitoringPerformanceDataId somehow...?

Any ideas?  Obviously I could compare the values that I'm getting in Powershell versus what I'm actually seeing in the SCOM performance view console to match them up.. but that wouldn't be any fun.  Especially with 800+ servers and these ID's are probably different for each.  :(

>$sample2 = get-performanceCounter -criteria: "MonitoringObjectPath='userv0234.us.domain.com'" | get-performanceCounterValue -startTime $startTime -endTime $endTime
PS Monitoring:\userv1172.us.domain.com
>$sample2


MonitoringPerformanceDataId : 2059862
SampleValue                 : 0.000325000000884756
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : a7564821-5956-4349-a6ca-78052b3268cc
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059876
SampleValue                 : 165647.609375
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : 53387f9e-8e4d-44b2-b798-18e0b930015b
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059861
SampleValue                 : 1135.158203125
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : 430ccd2b-e927-46e1-b555-1a1f3d8cab1a
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059842
SampleValue                 : 0
TimeSampled                 : 3/17/2010 10:31:43 AM
TimeAdded                   : 3/17/2010 10:32:25 AM
Id                          : 30749af3-7053-4bac-aafe-0a5db8662fc5
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059853
SampleValue                 : 0.6544468998909
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : 7d6c549a-6f74-4100-aac8-82c2e7aa5e15
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059869
SampleValue                 : 0.0269736349582672
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : c466c184-d8bf-404f-8df1-b2265ffe0eea
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059866
SampleValue                 : 34229.23046875
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : c5729010-dfe2-461b-85e5-f18b5adbb2c5
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059874
SampleValue                 : 44924.04296875
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : 11273cd4-f637-4769-a9c0-257c8f14bfb4
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059857
SampleValue                 : 14.4679508209229
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : 26d31a6a-ad73-4b33-bbca-5b2fe9787bbe
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059852
SampleValue                 : 8087
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : ee41437d-7ef3-4364-a5f9-a10960a9898e
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059860
SampleValue                 : 1.81308495998383
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : 2e12e3a2-f890-4a91-9eb1-faecdd1b7a19
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059867
SampleValue                 : 0.0934924110770226
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : 30f2e220-896d-4b56-8fd9-ed4a6f65f139
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059854
SampleValue                 : 16879.376953125
TimeSampled                 : 3/17/2010 10:29:10 AM
TimeAdded                   : 3/17/2010 10:29:41 AM
Id                          : 729374f0-5842-4cd6-95ff-65d5c3950d4a
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055

MonitoringPerformanceDataId : 2059865
SampleValue                 : 10723.9521484375
TimeSampled                 : 3/17/2010 10:29:11 AM
TimeAdded                   : 3/17/2010 10:34:41 AM
Id                          : f6dac739-2cdd-418a-ae9a-9b0d704a9b41
ManagementGroup             : US-Domain
ManagementGroupId           : ff7da74a-b70c-ddd0-58b9-ee0e42393055



PS Monitoring:\userv1172.us.domain.com
>

So the question is how do I know which "MonitoringPerformanceDataId" corresponds to which Performance Counter?

I know that ID # 2059852 corresponds to "Memory/Available MBytes" since I could pull that one based on the "criteria" mentioned before.  But no clue about the rest of these.

Can someone help me dissect these objects via Powershell?

Thanks!

Please find a script below. Hopefully it's self documenting enough but if you've got any other questions please let me know!

Cheers

_________________________________________________________

 use OperationsManagerDW

I'd like to add that your starting point is not the way to go in my opinion. You don't monitor for the sake of monitoring.

Why would you wan't to monitor services of which you didn't know the existence of and can't say whether they are important or not?

You should ask yourself what kind of status/monitoring information you're missing right now. You could make an inventory of services that are currently active, but don't just monitor every service you find.